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 1823 - Editorial: section 6.2, xs:NCNAME, XSL-T sample code
Summary: Editorial: section 6.2, xs:NCNAME, XSL-T sample code
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Linux
: P2 minor
Target Milestone: ---
Assignee: Ashok Malhotra
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-28 15:24 UTC by Frans Englich
Modified: 2006-09-18 10:36 UTC (History)
0 users

See Also:


Attachments

Description Frans Englich 2005-07-28 15:24:45 UTC
Hello,

* The second paragraph after the table in section "6.2 Operators on Numeric
Values" starts with:

"If the two operands are not of the same type,subtype substitution"

A space is missing after "type,"

* Some function signatures refer to the type "xs:NCNAME", but the valid name is
"xs:NCName". It is at least these functions:

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

I don't know how widespread this error is; it could be distributed, depending on
how you build the specifications, for example.

* The XSLT implementation in "D.1.2 eg:if-absent" has an error on the second line:
<xsl:param name="node()" type="node()?"/>

The attribute "name" is wrong, "node()". Judging from the other code, it should
be "node".

(If I had no constraints, I would put all XSLT code in separate files, validate
them with a Schema, and bring in the appropriate sections with XInclude.)


Cheers,
Frans
Comment 1 Ashok Malhotra 2005-07-28 18:33:10 UTC
I have fixed the first typo you found.  The other two issues have been
corrected based on earlier comments.