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 3069 - [XSLT 2.0] XTDE0485
Summary: [XSLT 2.0] XTDE0485
Status: CLOSED FIXED
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
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-03 10:26 UTC by Michael Kay
Modified: 2007-10-10 20:45 UTC (History)
0 users

See Also:


Attachments

Description Michael Kay 2006-04-03 10:26:57 UTC
Error XTDE0485 reads:

[ERR XTDE0485] It is a non-recoverable dynamic error if namespace fixup is performed on an element that contains among the typed values of the element and its attributes two values of type xs:QName or xs:NOTATION containing conflicting namespace prefixes, that is, two values that use the same prefix to refer to different namespace URIs.

I haven't succeeded in writing a test case for this error, and I'm coming to the conclusion that it can't happen. The reasons are actually explained in the Note immediately preceding the error description:

(a) Namespace fixup happens before validation, so you can't create xs:QName attributes and then do fixup on them.

(b) You can't copy namespace-sensitive attributes to a new element while preserving the type annotation, because there is no mechanism to keep the namespace context the same.

I'd be interested if anyone can produce a use case showing how this error can happen.
Comment 1 Michael Kay 2006-04-27 20:33:33 UTC
The WG agreed that the condition described in error XTDE0485 can never occur and the error has therefore been removed from the spec.
Comment 2 Michael Kay 2007-07-26 22:24:56 UTC
The fix documented in this bug report was unfortunately not applied. The error condition (which we agreed can never happen) is still documented in the published Recommendation.
Comment 3 Sharon Adler 2007-10-10 20:45:19 UTC
To be fixed as erratum E16