- From: Maciej Stachowiak <mjs@apple.com>
- Date: Sat, 03 Oct 2009 06:15:56 -0700
- To: Toby Inkster <tai@g5n.co.uk>
- Cc: Sam Ruby <rubys@intertwingly.net>, Adrian Bateman <adrianba@microsoft.com>, HTML WG <public-html@w3.org>, Tony Ross <tross@microsoft.com>
On Oct 3, 2009, at 2:59 AM, Toby Inkster wrote: > 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. Yes, HTML5 could do that. But that wouldn't solve the compatibility issues with Microsoft's proposal, or the issues of understandability. > 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]. This is only the case for legacy features required for Web compatibility. HTML5 does not do that for new features. It would be a poor use of time for a browser developer to implement a feature that's not required for Web compatibility and that authors are not supposed to use in new content. Regards, Maciej
Received on Saturday, 3 October 2009 13:16:30 UTC