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 9433 - [SER11] Invalid reference to XSLT 2.1
Summary: [SER11] Invalid reference to XSLT 2.1
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Serialization 3.0 (show other bugs)
Version: Working drafts
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: Henry Zongaro
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-06 17:13 UTC by Jim Melton
Modified: 2010-06-29 17:14 UTC (History)
0 users

See Also:


Attachments

Description Jim Melton 2010-04-06 17:13:56 UTC
In section 9, Character Maps [1], there is a reference that reads textually as follows:

   See Section 20.1 Character MapsXT of [XSL Transformations (XSLT) Version 2.1] for examples of using character mapping in XSLT.

The "XT" is in superscript and the sequence "Section 20.1 Character Maps" is an a <a> element...that is, a link.

Unfortunately, the markup causes the link to be a link to XSLT 2.0, not to XSLT 2.1. 

I think that the markup should use "XT21" instead of "XT".  That is:

   <xspecref spec="XT" ref="character-maps"/>

should be changed to read:

   <xspecref spec="XT21" ref="character-maps"/>

There is at least one other xspecref element in this document that has the same error. 

[1] http://www.w3.org/TR/xslt-xquery-serialization-11/#character-maps
Comment 1 Henry Zongaro 2010-04-06 17:57:50 UTC
Quite right.  I included an Ed. Note in section 2 of serialization 1.1 [1] to remind us that links to XSLT 2.0 need to changes to links to XSLT 2.1.  At the time the first working draft of Serialization 1.1 was published, there was no public working draft of XSLT 2.1, so I couldn't issue the Serialization draft with broken cross-document links.

We can use this bug report to track the need to update the links as soon as the first working draft of XSLT 2.1 is published.

[1] http://www.w3.org/TR/2009/WD-xslt-xquery-serialization-11-20091215/#serdm
Comment 2 Henry Zongaro 2010-06-29 17:14:14 UTC
I have fixed this in the latest internal draft of Serialization 1.1.  I would be grateful if you could verify that, and mark this bug CLOSED.