W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2005

[Bug 1824] New: Functions return xs:NCName, but xs:NCName is not support in XSLT 2.0 Basic

From: <bugzilla@wiggum.w3.org>
Date: Thu, 28 Jul 2005 15:56:42 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1DyAkU-0007EV-MI@wiggum.w3.org>

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

           Summary: Functions return xs:NCName, but xs:NCName is not support
                    in XSLT 2.0 Basic
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators
        AssignedTo: ashok.malhotra@oracle.com
        ReportedBy: frans.englich@telia.com
         QAContact: public-qt-comments@w3.org


Hello,

There are functions which returns instances of xs:NCName:

fn:prefix-from-QName($arg as xs:QName?) as xs:NCNAME?
fn:local-name-from-QName($arg as xs:QName?) as xs:NCNAME?

>From my understanding, they guarantee to return atomic values that not only has
a value space conforming to xs:NCName, but which also are or the type
xs:NCName(or they are the empty sequence). From what I can tell, one should be
able to rely on that:

"prefix-from-QName(QName("http:example.org/", "prefix:local")) instance of
xs:NCName" is always true.

But, the type xs:NCName is not a supported type in for example XSL-T 2.0 at
Basic conformance level(from what I can tell), although I don't know if that
matters.

How is this dilemma solved? What would allow an implementation to return
xs:string instead of xs:NCName, for example?

If that is not possible, which currently is my conclusion, I would say the best
solution is to change the return types to "xs:string?".


Cheers,
Frans
Received on Thursday, 28 July 2005 15:56:46 UTC

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