W3C home > Mailing lists > Public > www-tag@w3.org > June 2002

Re: Updated: issue qnameAsId-18

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Fri, 07 Jun 2002 15:19:10 -0400
To: www-tag@w3.org
Message-ID: <878z5qx5g1.fsf@nwalsh.com>

/ Elliotte Rusty Harold <elharo@metalab.unc.edu> was heard to say:
| At 10:01 AM -0400 6/6/02, Norman Walsh wrote:
|
|>| Note that XML Schema uses qnames in attribute
|>| values, so the W3C has already sanctioned this.
|>
|>Yes, and the finding sanctions it as well, provided that the attribute
|>in question contains only an xs:QName.
|
| What about the XSLT case? e.g.
|
| <xsl:apply-templates select =
| "child::Person/child::name:First[following-sibling::name:MI = 'M']" />

Given that XPath can't be "undone" at this point, there's no point
saying that the use of QNames in XPath is wrong.

I think the finding needs to say something about XPath explicitly, but
I haven't figured out what yet. Suggestions most gratefully accepted.

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM   | In a universe of electrons and selfish genes,
XML Standards Engineer | blind physical forces and genetic replication,
XML Technology Center  | some people are going to get hurt, other
Sun Microsystems, Inc. | people are going to get lucky, and you won't
                       | find any rhyme or reason in it, nor any
                       | justice.--Richard Dawkins
Received on Friday, 7 June 2002 15:20:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:55:52 UTC