Any AMP page can be HTML5 compliant. AMP doesn't require that the page pass an HTML5 validator, but is entirely compatible with HTML5.

JavaScript and Web Components are part of the HTML5 standard. This is simply the Extensible Web (https://www.w3.org/community/nextweb/2013/06/11/the-extensib...)

My profile discloses that I work on AMP.

Since you work on AMP, can you please disclose why Google results call the AMP carousel “Top Stories,” when indeed it’s not the top stories, but the top _AMP_ stories? Please create a ticket that instructs engineers to immediately change this nomenclature to either “Top AMP Stories” or start allowing non-Amp pages to appear in this carousel. This is misleading to users of Google.

Presumably, the people who work on the AMP spec are different from the people who work on Google search (or for that matter, Bing search, Yandex search, or any other search engine that consumes AMP). I doubt he has any control over how search results are ranked or presented.

That's the main problem with AMP. For any issue that AMP is the cause of the AMP team goes: "not our problem, ask the people who implement a specific feature".

Plausible deniability and all that.

Do you have any examples? Also, in what way is search ranking a problem of the AMP team?

> Any AMP page can be HTML5 compliant.

They are not compliant by default.

> This is simply the Extensible Web

That gets exclusive preferential treatment by Google.

It's not "just HTML".