Hesitation on setAttributeNS

Hi,

setAttributeNS() and friends with similar parameters has text to stricly 
forbid a qName with a prefix for a null nsURI, but nothing on whether it 
is legal to use it with a defined nsURI, and a qName that doesn't 
contain a prefix part.

Most implementations seem to accept it, and then fail to serialise it 
properly. Some rightfully complain that you can't have a namespace URI 
on an attribute that doesn't have a prefix. This is a sorry state of 
affairs :)

So it would be nice to see it resolved either way: either it is clearly 
flagged as an error, or it is clearly allowed, with indication of how 
the implementation may produce the prefix (not overwriting the one of 
that attribute if it exists, using a prefix in scope if there's one, 
generating one).

Or have I missed something?

-- 
Robin Berjon