W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2006

[Bug 3069] [XSLT 2.0] XTDE0485

From: <bugzilla@wiggum.w3.org>
Date: Mon, 03 Apr 2006 10:26:58 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1FQMGw-0003kI-6t@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3069

           Summary: [XSLT 2.0] XTDE0485
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 2.0
        AssignedTo: mike@saxonica.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


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.
Received on Monday, 3 April 2006 10:27:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:11 UTC