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

[Bug 5629] Namespace conflict when renaming attributes

From: <bugzilla@farnsworth.w3.org>
Date: Sat, 05 Apr 2008 14:23:57 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1Ji9JF-0000M0-B8@farnsworth.w3.org>

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

           Summary: Namespace conflict when renaming attributes
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Update Facility
        AssignedTo: andrew.eisenberg@us.ibm.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


In 2.4.4 clause 2b, a strict reading of the rule

If the namespace binding of $QName conflicts with any namespace binding in the
namespaces property of the parent (if any) of $target, a dynamic error is
raised [err:XUDY0023].

(in conjunction with the referenced definitions) suggests that if the new
attribute name has namespace binding (null, null) and the target element has a
namespace binding (null, "abc.uri"), then a conflict exists and XUDY0023 is
raised. However, this situation is clearly not a conflict, in fact, it is
likely to be very common and no trouble at all.

I suggest changing the rule to read:

If $QName has a non-absent namespace, and if the namespace binding of $QName
conflicts with any namespace binding in the namespaces property of the parent
(if any) of $target, a dynamic error is raised [err:XUDY0023].
Received on Saturday, 5 April 2008 14:24:28 UTC

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