RFC: Extend Oembed adding optional amp_html parameter

[patrick-mcdougle]

In the same way that oembed responses contain html parameters containing the valid HTML for consumers to drop into their pages, what if the oembed spec was extended to allow amp_html parameters containing the valid Google AMP markup for the provider's embed (if supported)? I would certainly be willing to draft this extension to the spec if the community would be supportive of this change.