W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2011

[Bug 11427] should allow use of xml:id for XHTML5

From: <bugzilla@jessica.w3.org>
Date: Tue, 04 Jan 2011 09:02:44 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Pa2my-0000Bp-5R@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11427

Henri Sivonen <hsivonen@iki.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hsivonen@iki.fi

--- Comment #9 from Henri Sivonen <hsivonen@iki.fi> 2011-01-04 09:02:39 UTC ---
I think we shouldn't make xml:id conforming or in any way facilitate its use.

Even though it doesn't look like it on the surface, breaking the assumption
that nodes have at most one attribute that has the IDness nature causes quite a
bit of complexity. A patch for implementing xml:id in Gecko was written, but
the patch ended up touching a lot of code and got rejected due to adverse
performance effects. I initially implemented xml:id support in Validator.nu
contrary to advice given to me by more experienced people, and supporting more
than one attribute with IDness caused unanticipated complexity in various parts
of the code base. WebKit has decided against supporting xml:id. At least some
SVG people seem to regret that they put xml:id in SVG 1.2 Tiny.

Instead of using xml:id, XML tooling should have a processing stage that
assigns IDness to the id attribute in no namespace. (You can call this
processing stage "XHTML id processor" analogously to on "xml:id processor".)

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 4 January 2011 09:05:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 4 January 2011 09:05:56 GMT