- From: Toby Inkster <tai@g5n.co.uk>
- Date: Sat, 03 Oct 2009 10:59:25 +0100
- To: Maciej Stachowiak <mjs@apple.com>
- Cc: Sam Ruby <rubys@intertwingly.net>, Adrian Bateman <adrianba@microsoft.com>, HTML WG <public-html@w3.org>, Tony Ross <tross@microsoft.com>
On Fri, 2009-10-02 at 16:51 -0700, Maciej Stachowiak wrote: > Representatives of browser implementors other than Microsoft > have expressed reluctance to support a mechanism similar to XML > namespaces in text/html syntax for philosophical and technical > reasons. In particular, there are concerns about the usability of > prefix-based indirection for authors, and about the wisdom of allowing > unilateral extensions to the language in such a way that content using > them is still conforming. Perhaps the HTML5 specification could define the parsing of xmlns:* attributes, and element and attribute names containing colons, and represent them in the DOM in a namespaces-in-XML-like way, but declare their use to be non-conforming. There is precedent for the HTML5 spec to define non-trivial parsing and DOM representation requirements on non-conforming parts of the language: <frameset> and <applet> for instance [1][2]. Then people can write "other applicable specifications" [3] which use namespaces if they want to, safe in the knowledge that in user agents which don't implement the applicable specification, it will at least be parsed into the DOM properly. People using these other applicable specifications would not be writing conforming HTML5, but might be writing conforming, say, "HTML5+BeeKeepingML" or whatever. ____ 1. http://dev.w3.org/html5/spec/obsolete.html#frameset 2. http://dev.w3.org/html5/spec/obsolete.html#the-applet-element 3. http://dev.w3.org/html5/spec/infrastructure.html#other-applicable-specifications -- Toby A Inkster <mailto:mail@tobyinkster.co.uk> <http://tobyinkster.co.uk>
Received on Saturday, 3 October 2009 10:00:18 UTC