> I wouldn't claim it to be THE general solution, but I think it covers a
> sufficient number of use-cases that's it's worth a vocabulary designer
> looking at before considering me elaborate schemes.
Yep it's intended to be a guide just for someone looking for advice
when creating an internal format consumed by non-xml devs.
> That said, I don't think you'd have to be that smart to get around the
> cut-and-paste-from-the-middle problem.
Agreed, but you would be surprised the number of times developers look
at unprefixed xml and assume it's in no namespace.
--
Andrew Welch
http://andrewjwelch.com
