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 3336 - [XSLT 2.0] Clarification of namespace fixup rules
Summary: [XSLT 2.0] Clarification of namespace fixup rules
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 2.0 (show other bugs)
Version: Recommendation
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
Depends on:
Reported: 2006-06-15 21:01 UTC by Michael Kay
Modified: 2008-01-31 18:14 UTC (History)
0 users

See Also:


Description Michael Kay 2006-06-15 21:01:50 UTC
In Working group email 

it was suggested that in 5.7.3, the sentence

Namespace fixup may, if necessary to resolve conflicts, change the 
namespace prefix contained in the QName value that holds the name of an 
element or attribute node.

did not make it sufficiently clear that "changing the prefix" included the option of adding or removing a prefix.

The editor was asked to propose a clarification. The simplest option seems to be to add immediately after the quoted sentence, "This includes the option to add or remove a prefix."

And in 11.3, change

In the event of a 
conflict this prefix (or absence of a prefix) may subsequently be changed 
during the namespace fixup process


In the event of a 
conflict a prefix may subsequently be added, changed, or removed 
during the namespace fixup process
Comment 1 Michael Kay 2007-11-07 15:11:47 UTC
The accepted proposal involved a change to section 11.3. In fact the identical text was present in both sections 11.2 and 11.3, and the change was applied only to section 11.2. Erratum E18 will be raised so that the change is applied in section 11.3 as well.
Comment 2 Michael Kay 2007-11-15 17:45:01 UTC
The WG accepted this change at the telcon on 15 Nov 2007, and the editor was asked to prepare an erratum.
Comment 3 Michael Kay 2008-01-31 18:14:03 UTC
Erratum E18 which fixes this issue has been published, so the issue can now be marked resolved and closed.