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

[Bug 6807] New: [FO] ambiguity in fn:namespace-uri-for-prefix

From: <bugzilla@wiggum.w3.org>
Date: Mon, 13 Apr 2009 19:39:48 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-6807-523@http.www.w3.org/Bugs/Public/>

           Summary: [FO] ambiguity in fn:namespace-uri-for-prefix
           Product: XPath / XQuery / XSLT
           Version: Recommendation
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators
        AssignedTo: mike@saxonica.com
        ReportedBy: andrew.eisenberg@us.ibm.com
         QAContact: public-qt-comments@w3.org

Bug 5703, reported against XQTS and closed last year, suggested that the
correct response for

namespace-uri-for-prefix('', $in-xml)

was a zero-length string, where there is no default namespace in the in-scope
namespaces of $in-xml.

In 11.2.5 fn:namespace-uri-for-prefix we say,

"If $element has an in-scope namespace whose namespace prefix is equal to
$prefix, it returns the namespace URI of that namespace. If $prefix is the
zero-length string or the empty sequence, it returns the namespace URI of the
default (unnamed) namespace. Otherwise, it returns the empty sequence."

Where there is no default namespace, one could imagine returning either an
empty sequence or a zero-length string as the result.

Michael Kay has suggested that specifying the result as the zero-length string
would be consistent with namespace-uri and namespace-uri-from-QName.

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 Monday, 13 April 2009 19:39:57 UTC

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