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

[Bug 5629] [UPD] Namespace conflict when renaming attributes

From: <bugzilla@farnsworth.w3.org>
Date: Tue, 15 Apr 2008 16:34:03 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1Jlo6d-0001Un-Bm@farnsworth.w3.org>

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





------- Comment #2 from jonathan.robie@redhat.com  2008-04-15 16:34 -------
(In reply to comment #0)

> (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 don't understand why this is no trouble at all. I think you are talking about
cases like this:

insert node attribute role { "agent" }
into <foo xmlns="purple.example.com"/>

If role has no prefix, what namespace should it be in? Should it adopt the
namespace associated with an absent prefix in the element where it is inserted?
Should it retain whatever namespace it had before insertion? I think either
answer can lead to some rather confusing scenarios.

Jonathan
Received on Tuesday, 15 April 2008 16:35:04 UTC

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