W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2006

[Bug 3201] fn:id not subject to compatibility - an oversight?

From: <bugzilla@wiggum.w3.org>
Date: Thu, 04 May 2006 21:15:04 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1FblA8-00012i-3t@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3201

           Summary: fn:id not subject to compatibility - an oversight?
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: PC
        OS/Version: Windows 2000
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XPath
        AssignedTo: chamberl@almaden.ibm.com
        ReportedBy: david_marston@us.ibm.com
         QAContact: public-qt-comments@w3.org


In the function conversion rules at 3.1.5, regarding the extra steps for 1.0
compatibility mode, sub-step 2 is applied only for xs:string and xs:string?,
not for xs:string*. The first argument to fn:id is xs:string*, so it will
bypass sub-step 1. The consequence of sub-step 2 not applying to fn:id is that
fn:id(true()) would get a node whose ID is "true" in 1.0 but not in 2.0 (type
error instead), regardless of compatibility mode. If that was your intent,
please add that case to the list in Appendix I.1.
Received on Thursday, 4 May 2006 21:15:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:12 UTC