This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29617 - [FO31] Typo in 18.2
Summary: [FO31] Typo in 18.2
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 3.1 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 editorial
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
Depends on:
Reported: 2016-05-08 12:25 UTC by Abel Braaksma
Modified: 2016-07-21 14:19 UTC (History)
0 users

See Also:


Description Abel Braaksma 2016-05-08 12:25:55 UTC
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 xs:QName(?)?

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 arguments.

I.e., I propose: s/fn:/xs:/
Comment 1 Michael Kay 2016-06-06 15:29:28 UTC
Thanks, I have corrected this typo.