This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
There's an unnecessary inconsistency between the XSLT and XQuery specifications over xml:id. XQuery makes it an error if the value of the attribute isn't a valid NCName (a static error in the case of a fixed constructor, a dynamic error otherwise), XSLT doesn't make it an error unless you validate. I don't care which solution we adopt but let's get them into line. Note that XSLT permits <element xml:id="{expr}"/> while XQuery doesn't.
At its meeting today, the XSL and XQuery working groups decided to accept this comment and align XQuery with XSLT wrt xml:id as follows: In element construction, both direct and computed, remove the text, the string-value of the attribute must be in the lexical space of the type xs:NCName [err XQST0082] In addition, the word "informally, " can removed, since the prefix must be "xml". Or talk abuot xml:id instead of the namespace URI. There should also be a reference to the xml:id spec. I would be grateful if you could confirm your acceptance of this resolution by marking the bug entry as CLOSED; alternatively, if you have further comments to make, or if you feel the requirement has been misunderstood, please feel free to respond to that effect. In the absence of further comments, we will close the bug.
*** Bug 1458 has been marked as a duplicate of this bug. ***