- From: <bugzilla@jessica.w3.org>
- Date: Sun, 12 Oct 2014 14:15:22 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27025 --- Comment #2 from Thue Janus Kristensen <thuejk@gmail.com> --- > "codecs" as used as a MIME type parameter is already well established in the MPEG and DASH communities I agree that many people are often using the two meanings interchangably. Even though they are really two different things. I just keep seeing endless confusion whenever people are talking about and conflating the two. While professionals can probably understand the difference, it is unnecessarily confusing for people who do not a priori have a complete understanding. > this isn't the first such mismatch, and won't be the last How about trying to be precise, and get as few semantic mismatches as possible. HTML5 is still a draft; it can still be fixed. Browsers can still unofficially support the codecs=... version for compatibility, if the draft switches to format=... . > In any case, the definition of MIME type parameters and their usage is outside the scope of the HTML5 specification. HTML5 is just a consumer of these parameters. At the very least, the HTML5 specification should use unambiguous and precise language when talking about codecs versus video/audio coding formats. It currently doesn't. And explain why the codecs=... parameter isn't really a list of codecs. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Sunday, 12 October 2014 14:15:23 UTC