[gojomo]

How does SXG "set dynamite to" http-server-centricity? Aren't all resources still named via HTTP endpoints, thus also bringing in overhead of the domain-system & TLS-Certificate assumptions? It seems to enable path-indifference, not independence from HTTP-server assumptions.

How does certificate transparency resolve a dependence on short-lived certificates that makes perfect sense for Google's applications, but not necessary others? Will these unspec'd additions like "additional user encryption", "user subdomains", etc be easy to define & standardize – even if they don't meet Google's very-specific motivations that this power things like AMP?

Iv'e only skimmed the ADX materials so far, but that's enough to see it's not a "standalone completely isolated alternate world" – reusing many standards deployed elsewhere (which another commenter has pointed out are often older than SXG), and devising conventions that even an SXG-centric solution would... still need to devise.