- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 13 Jul 2005 18:00:09 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1570 Summary: [XQuery+XSLT] xml:id Product: XPath / XQuery / XSLT Version: Last Call drafts Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: XPath AssignedTo: chamberl@almaden.ibm.com ReportedBy: mike@saxonica.com QAContact: public-qt-comments@w3.org 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.
Received on Wednesday, 13 July 2005 18:00:13 UTC