RE: Is "Expanded QName" underspecified?

>The current situation is that there is no way of converting 
> an expanded QName to a string (see...) and therefore there
> is no way of writing a QName to the result tree.

So I take it we should simply consider the behavior of this datatype 
"unstable" for now, and conversion to string should either throw an error 
or otherwise Do Something Reasonable until such time as the open issues 
are resolved... Good enough for dance music.

______________________________________
Joe Kesselman  / IBM Research