tags » Have you ever imagined how much it would be useful to map an URL on media content providers to detailed information in XML or JSON about the media’s itself?
The problem with today’s world can be summarized into a few sentences. Media that we’re uploading to media share services like Youtube and Flickr, is usually used on different mediums like our blogs or on other social platforms. So adding these kinds of rich media with jumble embed codes to everywhere is a lot nervous. What would happen if these providers give you an opportunity to fetch some essential information about the media with its permalink?
Leah Culver announced that OEmbed comes with an idea to distribute machine readable data for embed elements from photo, video and rich content providers. So as you provide the media’s permalink, it returns you its title, description, embed code and etc.
Below there is an example of getting some information from Flickr about this photo. There is a sample scenario below ask provider more about the picture via oEmbed.
As you see above, Flickr returned us the details about the picture. So, you can easily develop more complex applications which combine multimedia elements from different sources by providing only links.
At the moment, Flickr, Viddler, Qik, Pownce, Revision3 and Hulu is giving support to OEmbed. Please visit the official page for the specifications and the API back points.
JBF provides some new generation energy to the web. She is working on interesting stuff like increasing efficiency in data on the web and making content more machine readable. (
Made on a