- From: <bugzilla@jessica.w3.org>
- Date: Fri, 30 Sep 2011 01:14:28 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12544 --- Comment #17 from Mark Watson <watsonm@netflix.com> 2011-09-30 01:14:26 UTC --- (In reply to comment #16) > (In reply to comment #15) > > > > Please check section 5.8.5.5. of the MPEG DASH specification, available at > > http://www.3gpp.org/ftp/Inbox/LSs_from_external_bodies/ISO_IEC_JTC1_SG29_WG11/29n12313.zip > > Is this the right link? It seems to be a zip file containing a zip file > containing XML files and a schema, along with an HTML file describing the > package and some files in a proprietary format I can't read. Is there an HTML > (or failing that, PDF) version somewhere? Yes, it's the correct file. The one you want is the large Word document. That seems to be the format use by MPEG and 3GPP for exchanging documents. > > > > Put another way, your argument above could equally be given by a container > > designer who says there is no point in marking a stream with some indication > > which could never be passed to the HTML presentation layer. > > I don't think that's a real concern. Historically people have had no problem > adding features to their languages and technologies before HTML APIs could > represent them. It seems unlikely that these features, if they are useful at > all, would only be useful in an HTML context. Oh, I completely agree that they would not be useful only in an HTML context. They are useful when provided in HTML *and* container formats. Again, it's a question of who goes first and again it makes more sense for the container-independent language to lead the way for things where the need for the feature by users is obvious and unquestioned, as is the case for clean audio. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Friday, 30 September 2011 01:14:34 UTC