- From: Jirka Kosek <jirka@kosek.cz>
- Date: Wed, 10 Oct 2012 10:58:01 +0200
- To: Felix Sasaki <fsasaki@w3.org>
- CC: Shaun McCance <shaunm@gnome.org>, "public-multilingualweb-lt@w3.org" <public-multilingualweb-lt@w3.org>
- Message-ID: <50753899.9010204@kosek.cz>
On 10.10.2012 10:47, Felix Sasaki wrote: > I agree that having the table in an appendix wouldn't make sense. Also, > there is a huge overlap between the table in sec. 6.1 and your table. And > finally, Jirka is addressing the "how to work with HTML5" in a separate > section too. Hi all, actually what I was going to write down in a couple of hours was dedicated section defining how local "XML" markup is used in HTML5 -- using its-*-* instead of camelCased attribute names, constant values are case insensitive in HTML5, etc. I think that one such generic section should be enough, especially if we will have table listing all local data categories together with corresponding HTML5 attribute name somewhere in the spec. I understand that having special HTML5 section parallel to GLOBAL/LOCAL sections can be more digestable to readers of spec but it will be almost verbatim copy of LOCAL section -- and keeping those two pieces synchronized seems as a lot of additional work with not a big gain. I think that if we want to server HTML5 community we can create separate document (Note or Rec) which will talk only about ITS in HTML5. It should reference ITS 2.0 and define syntax of its-* attributes on top of this. Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka@kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member ------------------------------------------------------------------
Received on Wednesday, 10 October 2012 08:58:25 UTC