- From: Sean Hayes <Sean.Hayes@microsoft.com>
- Date: Wed, 1 Dec 2010 21:59:15 +0000
- To: Janina Sajka <janina@rednote.net>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Some comments: "XML-based nature raises concerns with regard to name-spacing, draconian error handling, etc" I still have yet to find out what precisely is the problem here, so I don't actually see this as a Con, however for those that do, I will also point out that TTML is actually formally defined in terms of a reduced XML infoset, thus it would be entirely possible to write a lenient non-namespace aware tag soup parser that produced this infoset. IMO doing so would not be in anyone's best interests but the option remains. "As currently specc'd cannot be styled with CSS" Cannot is not accurate. CSS can style any XML format. What you mean is that CSS is not currently very well set up to style a dynamically changing DOM, however it can be applied to the method documented at http://www.cwmwenallt.com/ttml/TTMLmapping.htm and utilize the host page's CSS to style to override the TTML inline style. While we are talking about style I'll also point out here that WebSRT has to rely on a future version of CSS being applied from the host page. I think that is a definite Con. "Will require a profile crafted to address what is perceived as an overly verbose and complex specification" Well I would compare it to the HTML5 spec before anyone starts calling it overly verbose or complex. There is the opportunity to write a profile if need be for sure, however given that I was able to write a complete mapping in JS in just over a week, I personally think the full profile will be fine. "Does not support hierarchical structure navigation" - I have added an example in the checklist, so this should be removed. -----Original Message----- From: public-html-a11y-request@w3.org [mailto:public-html-a11y-request@w3.org] On Behalf Of Janina Sajka Sent: 01 December 2010 21:33 To: HTML Accessibility Task Force Subject: Draft Summary Doc for our Media Call Today Colleagues: The following was prepared by John for our Media Subteam call today: http://www.w3.org/WAI/PF/HTML/wiki/TextFormat_Pros_Cons_Overview#Summary_o It is hoped this draft will give us a head start on finalizing a summary report that can be shared with the WG. Janina -- Janina Sajka, Phone: +1.443.300.2200 sip:janina@asterisk.rednote.net Chair, Open Accessibility janina@a11y.org Linux Foundation http://a11y.org Chair, Protocols & Formats Web Accessibility Initiative http://www.w3.org/wai/pf World Wide Web Consortium (W3C)
Received on Wednesday, 1 December 2010 21:59:50 UTC