So if I’m reading the oEmbed spec correctly, it should be possible to pre-render #oEmbed metadata for a #staticSite as long as I…
- Pre-render both XML and JSON formats
- Pre-render the discovery links in the page head
- Have the server map endpoint+parameter URLs to the files
- Only provide “link” type responses
Photo, video, and rich responses are all required to specify a width and height, and those are required to fit within the requested maxheight and maxwidth, so those responses would have to be dynamic.
It’s not clear whether [3] is necessary if I have [2].
Link responses aren’t that much more useful than including the title element in the original file.
Photo responses would be good for, well, photos, and rich responses would let me design the embedded preview for an article. Which would be nice.
But most of this is pretty much covered by #OpenGraph and similar #metadata schemes that are just in the file — no messing around with API endpoints or mapping and the rest. So I’m not sure it would be worth the effort except maaaaybe being able to get WordPress sites to embed a preview when someone pastes a plain URL. (Assuming it will look for the discovery link in the first place, that is.)