[whatwg] html5 + ogg
silviapfeiffer1 at gmail.com
Sun Dec 30 08:41:13 PST 2007
The spec is not finalised and the a/v baseline codec question is one
of the open questions.
As exerience from the W3C video workshop shows, all involved parties
want to find a solution for a baseline codec that can actually be
mandated. I am confident that the new year will see us solve this
problem with a royalty-fee codec that is acceptable to everybody,
however, it will take time and a lot of discussions. Flamewars won't
help (not that this thread is one, but we have had a few threads that
were pretty close to a flamewar).
I am expecting progress from technical and legal discussions, possibly
in small expert groups. This is a hard problem, but people are working
On Dec 29, 2007 8:19 PM, Henry Mason <hmason at mac.com> wrote:
> On Dec 29, 2007, at 12:01 PM, Philip Parker wrote:
> > The removal of ogg as a baseline for audio/video implementation
> > strikes me as ridiculous. Theres nothing stopping other formats from
> > being used after all
> If the specification included the Ogg baseline and few web browsers
> actually supported it, what use would the specification be? Simply
> specifying it won't actually make it widely implemented.
> There's also nothing stopping you from using Ogg in the things you
> develop right now, so how does the removal change what you choose to do?
> > As things stand with how easily large corporations can
> > obstruct/corrupt the process for their own goals, I might as well just
> > stick to xhtml1 and avoid rich media elements where possible in any
> > site I may end up developing until - and indeed if sense prevails.
> I guess by "rich media elements" you also mean JPEG, GIF, PNG, SVG,
> and Flash? None of those are included as baselines in the XHTML1
> specification either.
More information about the whatwg