> I might be off track, but here are some of my musings:

> 1) An official callback parameter would be nice.

> 2) The three most used media types on the web are: image, video and
> audio.
> There are two main ways to display them in a browser: 1) portions of
> HTML or Javascript (very particular to the provider); 2) Source files.
> Images, ever since Mosaic, have always been embedded as source, and
> since all browsers support it, no one felt the need for a workaround
> like HTML, Flash, etc. There are however formats such as SVG that are
> purely XML and can be inlined in the browser.
> Videos and audios have only recently been embedded as source with the
> introduction of HTML5. Before that, we had the famous Flash players
> and obfuscated sources.
> This is the current way to deal with different formats:
> http://tmp.qiknr.com/files/media_scenario.png (correct me if this is
> in someway wrong and keep in mind that the <video> and <audio> tags in
> HTML5 allow fallbacks).

> So the question is: how do you specify something that incorporates all
> of these variables? Any ideas?

> On Apr 29, 10:01 am, Sean Creeley <sean.cree...@gmail.com> wrote:
>> Embedly would love to participate in this. It will give us the ability
>> to add an `audio` type that has been missing for ages.

>> Let me know what your proposed next steps would be.

>> Thanks for proposing this!

>> Sean

>> Co-Founder at Embedly

>> On Thu, Apr 28, 2011 at 8:31 PM, Samin Shams <saminsh...@gmail.com> wrote:
>> > oEmbed v1 was written in what, 2008?
>> > I'm I the only one who feels that maybe the authors should start thinking of
>> > a version 2 of the specification, taking in all the suggestions given in
>> > this group in the past 3 years?

>> > I mean, seeing that the web is now moving into html5 and open standards for
>> > media files, maybe a new specification could be written taking that into
>> > account. It feels like the authors have given up on keeping this an active
>> > community and I'm sure companies like Embed.ly and many consumers such as
>> > myself are still very interested in making this a tool as fitting to the web
>> > as possible.

>> > Who's with me?

>> > --
>> > You received this message because you are subscribed to the Google Groups
>> > "OEmbed" group.
>> > To post to this group, send email to oembed@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > oembed+unsubscribe@googlegroups.com.
>> > For more options, visit this group at
>> >http://groups.google.com/group/oembed?hl=en.

> --
> You received this message because you are subscribed to the Google Groups "OEmbed" group.
> To post to this group, send email to oembed@googlegroups.com.
> To unsubscribe from this group, send email to oembed+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/oembed?hl=en.