Comments on: Announcing OEmbed - An Open Standard for Embedded Content http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/ leahculver.com Sat, 22 Nov 2008 00:34:46 +0000 http://wordpress.org/?v=2.3.2 By: dns http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1125 dns Wed, 11 Jun 2008 07:53:31 +0000 http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1125 [...] Pownce an OpenDNS, this early spec has already been adopted up by Viddler, Qik, Revision3 and Hulu.http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/Howstuffworks &quotHow Domain Name Servers Work&quotDomain name servers, or DNS, are an incredibly [...] […] Pownce an OpenDNS, this early spec has already been adopted up by Viddler, Qik, Revision3 and Hulu.http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/Howstuffworks &quotHow Domain Name Servers Work&quotDomain name servers, or DNS, are an incredibly […]

]]> By: Andrew Mager http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1124 Andrew Mager Wed, 11 Jun 2008 00:13:38 +0000 http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1124 Don't forget about Plurk! Hey, I was gonna write about OEmbed at the same time :( Don’t forget about Plurk!

Hey, I was gonna write about OEmbed at the same time :(

]]> By: robert http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1123 robert Tue, 10 Jun 2008 19:18:00 +0000 http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1123 Does oembed output standards compliant code, or code that will work across all the old browsers instead? I figure I know the answer, but figured I would ask anyways. Also a port of this to say a wordpress plug in, could be infinitely useful as well. Other than that, great job, I am surprised you guys had to come up with this and it wasn't available in the first place. Does oembed output standards compliant code, or code that will work across all the old browsers instead? I figure I know the answer, but figured I would ask anyways.

Also a port of this to say a wordpress plug in, could be infinitely useful as well.

Other than that, great job, I am surprised you guys had to come up with this and it wasn’t available in the first place.

]]> By: Review: oEmbed 1.0 » I’m JBF http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1121 Review: oEmbed 1.0 » I’m JBF Sun, 08 Jun 2008 18:07:32 +0000 http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1121 [...] 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. [...] […] 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. […]

]]> By: thejbf http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1120 thejbf Sun, 08 Jun 2008 10:09:50 +0000 http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1120 Finally data is getting out of pages! I'm so sure that in a short time, major media providers like youtube will go for this marvelous concept! Finally data is getting out of pages! I’m so sure that in a short time, major media providers like youtube will go for this marvelous concept!

]]> By: Michael R. Bernstein http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1117 Michael R. Bernstein Mon, 02 Jun 2008 18:42:37 +0000 http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1117 Standardizing the format and the endpoint schema for information about embeddable content is a great idea and will obviously save a lot of duplicated effort. But there is no provision here for autodiscovery, so this does not actually accomplish the stated goal of eliminating manually picking and choosing which services to support. Standardizing the format and the endpoint schema for information about embeddable content is a great idea and will obviously save a lot of duplicated effort. But there is no provision here for autodiscovery, so this does not actually accomplish the stated goal of eliminating manually picking and choosing which services to support.

]]> By: Dean Landolt http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1116 Dean Landolt Mon, 02 Jun 2008 18:19:16 +0000 http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1116 Beautiful. I can envision this being useful for all kinds of rich objects, not just media. Most objects have at least a few natural metaphors for how they would be represented when embedding -- this would allow the object's owner to provide a skeleton for that metaphor. Especially if some kind of autodiscovery a la rss be were in the offing? I'm not much of a security weenie, but perhaps autodiscovering foreign code to embed may be a bit too risky. Perhaps a whitelist providers could register domains with as part of the autodiscovery spec would alleviate some of the problems. Still, elegant spec. Brilliant. Beautiful. I can envision this being useful for all kinds of rich objects, not just media. Most objects have at least a few natural metaphors for how they would be represented when embedding — this would allow the object’s owner to provide a skeleton for that metaphor. Especially if some kind of autodiscovery a la rss be were in the offing?

I’m not much of a security weenie, but perhaps autodiscovering foreign code to embed may be a bit too risky. Perhaps a whitelist providers could register domains with as part of the autodiscovery spec would alleviate some of the problems.

Still, elegant spec. Brilliant.

]]> By: Wil Tan (MojiPage) http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1114 Wil Tan (MojiPage) Fri, 30 May 2008 20:53:17 +0000 http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1114 @adam, there are too many link tags. XRDS-Simple http://xrds-simple.net/ was created for this so we should use it. Leah, I'd be curious to know if you have discussed using a template in addition to the currently-defined per-instance mechanism. For the most part, the chunk of HTML used for embedding a particular URL scheme (such as Youtube) won't change much, so it could be a waste of resources to do that for every call. Of course, there are still plenty of use-cases for having per-instance call so as to allow providers to control it at a finer-granularity. There are definitely interesting applications of this in the "mobile web" arena. @adam, there are too many link tags. XRDS-Simple http://xrds-simple.net/ was created for this so we should use it.

Leah, I’d be curious to know if you have discussed using a template in addition to the currently-defined per-instance mechanism. For the most part, the chunk of HTML used for embedding a particular URL scheme (such as Youtube) won’t change much, so it could be a waste of resources to do that for every call.

Of course, there are still plenty of use-cases for having per-instance call so as to allow providers to control it at a finer-granularity.

There are definitely interesting applications of this in the “mobile web” arena.

]]> By: Matt Froese http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1113 Matt Froese Fri, 30 May 2008 18:55:35 +0000 http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1113 Excellent idea. I am happy to see many sites on board already. Is it really necessary to pass a full url to the oembed request. Seems somewhat redudant to request something from Flickr by sending it a Flickr URL! Excellent idea. I am happy to see many sites on board already.

Is it really necessary to pass a full url to the oembed request. Seems somewhat redudant to request something from Flickr by sending it a Flickr URL!

]]> By: Adam Nemeth http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1112 Adam Nemeth Fri, 30 May 2008 08:17:10 +0000 http://leahculver.com/2008/05/29/announcing-oembed-an-open-standard-for-embedded-content/#comment-1112 Whoah, thinking / working on such solutions for ages! :) Another thing: maybe a http header extension or catalog would be needed, so it could be auto-detected if some site supports oembed or such. Like RSS auto-discovery: link type="alternative" type="oembed/json"... something like such.. maybe provided by regexps.. relative to the element url (s/flickr.com\//photo\//.*/flickr.com\/oembed?\1 ?), maybe provided in the root page, like favicon (even better, maybe forcing the provider to always use the same scheme, eg. it should be www.domainname.com/oembed always...) All this stuff is for consumers to auto-discover new oembed providers. Whoah, thinking / working on such solutions for ages! :)

Another thing: maybe a http header extension or catalog would be needed, so it could be auto-detected if some site supports oembed or such. Like RSS auto-discovery:

link type=”alternative” type=”oembed/json”…

something like such.. maybe provided by regexps.. relative to the element url (s/flickr.com\//photo\//.*/flickr.com\/oembed?\1 ?), maybe provided in the root page, like favicon (even better, maybe forcing the provider to always use the same scheme, eg. it should be http://www.domainname.com/oembed always…)

All this stuff is for consumers to auto-discover new oembed providers.

]]>