- From: Chris Lilley <chris@w3.org>
- Date: Wed, 22 Jun 2005 02:57:41 +0200
- To: Norman Walsh <Norman.Walsh@Sun.COM>
- Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, Dan Connolly <connolly@w3.org>, public-xml-id@w3.org
On Monday, June 20, 2005, 10:09:58 PM, Norman wrote: NW> / Chris Lilley <chris@w3.org> was heard to say: NW> | On Friday, June 10, 2005, 11:11:34 PM, Bjoern wrote: NW> | | BH>> * Norman Walsh wrote: |>>>/ Dan Connolly <connolly@w3.org> was heard to say: |>>>| I can't tell if the intent is that the CSS specs get revised |>>>| to refer to xml:ID or if CSS implementations are to independently |>>>| pick up xml:ID support or what. The current spec is kinda waffly, |>>>| as far as I can tell... NW> | |>>>We believe that xml:id can be implemented in each of these cases and |>>>have taken (at least some) steps to demonstrate this fact. NW> | | BH>> This does not really answer Dan's question, or what I understood the | BH>> question to be. From NW> | | BH>> | BH>> http://www.w3.org/TR/2004/CR-CSS21-20040225/selector.html#id-selectors | BH>> http://www.w3.org/TR/2005/CR-xml-id-20050208/ NW> | | BH>> could you please state whether adding text like NW> | | BH>> If an implementation supports CSS 2.1 and also supports | BH>> xml:id, then the xml:id attribute must be treated as an | BH>> ID for the purposes of CSS selector processing. NW> | NW> | I must say that this is exactly the sort of conditional conformance NW> | requirement that i would like to see (and the same for DOM and XPath). NW> I think it would be great to see such a statement in CSS 2.1 (and DOM NW> and XPath 1.0; in fact, XPath 2.0 supports xml:id directly). NW> But I don't see how any of this can be accomplished by the xml:id NW> specification itself. NW> I took steps to demonstrate that it was possible to implement xml:id NW> support in CSS and XSLT 1.0 (and by extension other specifications) NW> *without* any changes to the "upper level" specifications. NW> Hopefully, the timely publication of xml:id as a Recommendation will help NW> those specifications adapt to support it. NW> If you object to closing this issue as Dan raised it, please let us NW> know. No objections, but please (ok so this is barter) make the statements you made above as last call CSS2.1 comments. It is in Last Call now. -- Chris Lilley mailto:chris@w3.org Chair, W3C SVG Working Group W3C Graphics Activity Lead
Received on Wednesday, 22 June 2005 00:57:47 UTC