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

[Bug 29617] New: [FO31] Typo in 18.2

From: <bugzilla@jessica.w3.org>
Date: Sun, 08 May 2016 12:25:55 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29617-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 29617
           Summary: [FO31] Typo in 18.2
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Functions and Operators 3.1
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

The third para in this sections starts as follows:

When a constructor function for a namespace-sensitive type is used as a literal
function item or in a partial function application (for example, fn:QName#1 or
fn:QName(?)) the namespace bindings that...

I think the subject of the paragraph is about
constructor-functions-as-a-function-item. But the examples within brackets give
the FO function fn:QName. I assume this was meant to be xs:QName#1 and

Furthermore, they are hyperlinked to the fn:QName function. And if fn:QName was
meant here (but rest of text suggests otherwise), this function takes two

I.e., I propose: s/fn:/xs:/

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 8 May 2016 12:27:51 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 8 May 2016 12:27:51 UTC