W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2010

[Bug 9606] New: Run-time QNames in xsl:key etc.

From: <bugzilla@jessica.w3.org>
Date: Wed, 28 Apr 2010 18:47:52 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-9606-523@http.www.w3.org/Bugs/Public/>

           Summary: Run-time QNames in xsl:key etc.
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: XSLT 2.1
        AssignedTo: mike@saxonica.com
        ReportedBy: sca@us.ibm.com
         QAContact: public-qt-comments@w3.org

There are various places in XSLT where we use run-time lexical QNames: for
example, the first argument to xsl:key, the third argument to format-number,
etc. It would be nice if these could be written in a way that doesn't depend
on knowledge of the static in-scope namespace prefixes. This is particularly
true when the XPath expression is a dynamic one evaluated using

Several approaches come to mind:

(a) allow an argument of type QName instead of string. This seems a natural
approach, the only problem is that we don't allow this kind of function
overloading. We would have to change the function signature to accept

We could solve this problem if we extended the type system to allow a union
type to appear in a function signature. This would be a generally useful
capability. We could then define our own union type union(string, QName) for
use in these function signatures.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 28 April 2010 18:48:33 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:42 UTC