W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2010

[Bug 9257] The rules for when an implied namespace binding conflicts should be more precise

From: <bugzilla@jessica.w3.org>
Date: Tue, 22 Jun 2010 14:48:53 +0000
To: public-qt-comments@w3.org
Message-Id: <E1OR4mT-0004b1-3x@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9257





--- Comment #3 from Jonathan Robie <jonathan.robie@redhat.com>  2010-06-22 14:48:52 ---
(In reply to comment #2)
> We believe you are correct - I will produce text to fix this here in this bug
> report.

I suggest we fix this by explicitly stating the exception for an attribute with
no namespace prefix in the three places where this problem occurs.

2.4.1 Insert
Bullet 3.b. 

No attribute node in $alist may have a QName whose implied namespace
binding conflicts with a namespace binding in the "namespaces"
property of $target [err:XUDY0023] <new>unless the namespace prefix
for the attribute is absent</new>.

Bullet 4.b. 

No attribute node in $alist may have a QName whose implied namespace
binding conflicts with a namespace binding in the "namespaces"
property of $target [err:XUDY0023] <new>unless the namespace prefix
for the attribute is absent</new>.


2.4.3.1 Replacing a Node
Bullet 4.b.

No attribute node in $rlist may have a QName whose implied namespace
binding conflicts with a namespace binding in the "namespaces"
property of $parent [err:XUDY0023] <new>unless the namespace prefix
for the attribute is absent</new>.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 22 June 2010 14:48:54 UTC

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