http://www.w3.org/Bugs/Public/show_bug.cgi?id=4487 ------- Comment #1 from john.snelson@oracle.com 2007-04-27 10:02 ------- I don't understand why this situation is any different to having an attribute with a namespace prefix that cannot be used since the prefix is already bound on the same element to a different namespace URI. In both cases the XDM shouldn't care, because the prefix is irrelevant to the actual name of the attribute (the namespace URI/local name pair). In my opinion this situation is a serialisation issue, and should be dealt with during serialisation. I think the obvious solution is to make up a namespace prefix for the attribute in both cases - but an alternative solution is to raise an error.Received on Friday, 27 April 2007 10:02:32 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:14:19 GMT