- From: <bugzilla@jessica.w3.org>
- Date: Tue, 14 Sep 2010 14:06:37 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9257 --- Comment #8 from Jonathan Robie <jonathan.robie@redhat.com> 2010-09-14 14:06:34 --- I decided to fix this by adding the following text to the definition of an implied namespace binding, in addition to taking the approach shown in comment #3: Definition: The implied namespace binding of a QName is the association of its namespace prefix (or absence thereof) with its namespace URI (or absence thereof).] [Definition: Two namespace bindings are said to conflict if their namespace prefixes (or absence thereof) are the same but their namespace URI's (or absence thereof) are different.] Update operations that result in conflicting namespace bindings generally raise errors, as described in this document. <add>However, if the namespace prefix of an attribute is absent, it is in no namespace, and an update operation can create such an attribute in an element even though its implied namespace binding conflicts with a namespace binding in the "namespaces" property of the element.</add> -- 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, 14 September 2010 14:06:38 UTC