Cart
[Home] [By Thread] [By Date] [Recent Entries]
Simon St.Laurent wrote:
> Yes, and you've completely missed my point yet again. I'm not arguing
> that prefixed attributes should be in the namespace of the element
> containing them. I'm arguing that _unprefixed_ attributes should be
> treated as if they had the same namespace as the element containing
> them.
I mostly agree. You've argued that doing the following
<x:y xmlns:x="http://example.com/" x:a="1" a="2" />
while legal per the ns rec, is idiotic and shouldn't be done. Agreed.
You've further argued that it was a design error that the ns rec allws
this. Agreed.
Where we may disagree is, if you're making an API, you'd better not
report the final attribute above (to use JJC's notation) as
{http://example.com}a, whether or not the first attribute is there or
not. For better or worse, at the API level, the final attribute there
has a local part of "a" and no namespace name, but is attached to an
element with a namespace name. -Tim
|
