Re: integration testing of xml:ID

/ Dan Connolly <connolly@w3.org> was heard to say:
| This section "Impacts on Other Standards" is great...
|   http://www.w3.org/TR/2005/CR-xml-id-20050208/#impact
|
| I see
|  "Informed readers that C Impacts on Other Standards will be removed
| before xml:id becomes a recommendation"
|
| Hmm... well, it would be great to remove the "Impacts..." stuff
| because it's all taken care of, but looking at a draft
| implementation report...
|   http://www.w3.org/XML/2005/01/xml-id-implementation.html
|
| ... I don't see, for example, a test corresponding to
| this ID selectors test...
| http://www.w3.org/Style/CSS/Test/CSS3/Selectors/current/xhtml/tests/css3-modsel-15.xml
|
| Before removing the "Impacts..." section, please at least
| add a link from the implementation report to something
| from the CSS WG that says "yes... good question... we'll
| look into that."

In an effort to address this comment, I was able to persuade the
authors of Amaya to demonstrate integration of xml:id processing.

| 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...
|
| "Document languages may contain attributes that are declared to be of
| type ID." is pretty waffly
| http://www.w3.org/TR/1998/REC-CSS2-19980512/selector.html#id-selectors
|
| I haven't looked into DOM, XPath, etc. as closely, but the concern
| applies.

We believe that xml:id can be implemented in each of these cases and
have taken (at least some) steps to demonstrate this fact.

Please let us know if this resolution is unsatisfactory to you.

                                        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.