You received this message because you are subscribed to the Google Groups "OEmbed" group.
To post to this group, send email to oem...@googlegroups.com.
To unsubscribe from this group, send email to oembed+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/oembed?hl=en.
Sounds like a good idea, probably slightly more complicated to
implement than the current discovery mechanism but could definitely be
more efficient, especially for hosts with a lot of embeddable content.
How often does the XRD need to be re-checked though, in case the URI
Coming from use of OpenSearch (http://www.opensearch.org/), I assumed
a site wide discovery document for OEmbed. After rereading section 4,
I see that I assumed wrong. The discovery of the OEmbed gives the URL
for the embeddable item's specific OEmbed result.
In my use case, in theory this kind of works as I am using OpenSearch
(or in some cases provider specific APIs for search) to narrow down my
results for the user to match to the user's search term before needing
to make the actual OEmbed request.
However it still adds an request to the user's selected item's detail
page to discover the OEmbed URL.
Not very efficient. I would prefer the OpenSearch style of site wide
description document telling me what the OEmbed service's base URL is.
I.e. if I make a request to any page of a given site I would like to
find in the head:
* a link to the OpenSearch description document
* a link to the OEmbed description document
After parsing those documents, I would like to in turn use them as
configuration parameters for listing that site as a media provider
that I can query against and get back OpenSearch results. After the
user selects a result, then I can request from the service the
result's OEmbed response.