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

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

           Summary: The rules for when an implied namespace binding
                    conflicts should be more precise
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Update Facility
        AssignedTo: jonathan.robie@redhat.com
        ReportedBy: josh.spiegel@oracle.com
         QAContact: public-qt-comments@w3.org
                CC: josh.spiegel@oracle.com


>From section 1.1:
        [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.]

Now, consider section 2.4.1 bullet 3. b.  which indicates XUDY0023 should be
thrown when an attribute to be inserted has a QName with an implied namespace
binding that conflicts with a namespace binding in the namespaces property of
$target.  This seems wrong if you consider attributes with no prefix.  An
attribute name without a prefix should not conflict with the default
element/type namespace.

For example, assume we have the default element/type namespace
""="my_default_uri" defined in the namespaces property of some element.  Now,
consider what happens when we insert an attribute with the implied namespace
binding ""="".  According to the definition, it seems these conflict but they
should not in this case.


-- 
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.