|
|
|
|
|
by macrael
5883 days ago
|
|
I never said that the spec should not specify a video codec, I was just trying to set the record straight. In fact, I didn't claim anything about the spec at all, I just summarized some of Hixie's points. If you aren't satisfied with what I wrote, I recommend reading Hixie's words. Please let me know if I misrepresented him. And, I disagree that not having it in the spec is the equivalent of having it in the spec. The problem is that the spec is useless when, as Hixie puts it, it becomes fiction. Mandating either Theora or H.264 in the spec would have been useless because either Firefox/Opera would be violating the spec or Safari/IE would be. So the only option left to them was to leave it out of the spec, something that Hixie was not happy about but seems like the right thing to do. If a codec comes along that all the vendors can agree to implement, then it is likely that will go into the spec, but until then it will remain blank. |
|
I disagree that just by forcing the spec to be changed from requiring Theora that Apple and Microsoft now get off the hook for their actions.
You said, repeating an often made claim, The spec does not specify a codec for use on the video tag, just as it doesn't for the img tag. Which is factually correct now, after Apple refused to implement the spec as it was and Hixie edited the spec to reflect reality. Hixie claims he will add a codec back, once one is found suitable, which means both royalty-free and implemented by the big players.
You appear to have done it by accident, but you'll find comments elsewhere in the thread that make the argument that he has no right to specify any codec in HTML5, whether Theora or a future royalty-free codec, and make the parallel to the img tag not specifying an image format. This is clearly not Hixie's position, and I don't think it generally holds any water.