Re: integration testing of xml:ID

/ Chris Lilley <chris@w3.org> was heard to say:
| On Friday, June 10, 2005, 11:11:34 PM, Bjoern wrote:
|
| 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...
|
|>>We believe that xml:id can be implemented in each of these cases and
|>>have taken (at least some) steps to demonstrate this fact.
|
| BH> This does not really answer Dan's question, or what I understood the
| BH> question to be. From
|
| 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/
|
| BH> could you please state whether adding text like
|
| 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.
|
| I must say that this is exactly the sort of conditional conformance
| requirement that i would like to see (and the same for DOM and XPath).

I think it would be great to see such a statement in CSS 2.1 (and DOM
and XPath 1.0; in fact, XPath 2.0 supports xml:id directly).

But I don't see how any of this can be accomplished by the xml:id
specification itself.

I took steps to demonstrate that it was possible to implement xml:id
support in CSS and XSLT 1.0 (and by extension other specifications)
*without* any changes to the "upper level" specifications.

Hopefully, the timely publication of xml:id as a Recommendation will help
those specifications adapt to support it.

If you object to closing this issue as Dan raised it, please let us
know.

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

Received on Monday, 20 June 2005 20:10:08 UTC