Cool, this makes more sense than my idea then!
So the owner of the ENS name would need to host a GraphQL endpoint (possibly on the same gateway server). And also deploy their own subgraph if they want/need to actually use TheGraph for it (though I don’t see why they would need to).
I see that Resolver still needs to be defined in this spec. Domain is explicitly defined here, but not Resolver.
Also, I see a subdomains field, but it’d be useful to have subdomainCount too like the subgraph has (for pagination purposes).
Yeah it’s probably a good idea to make it a URI, so you can use a direct data: URI if you need to. Theoretically it could be any other scheme too, like a gateway server.