Lists Home |
Date Index |
> If you think unqualified attributes being in "no namespace" is a
> mistake, then it's far better to break such documents than to change
> what they mean. In that way it's a compromise.
DTDs are already broken as far as namespaces are concerned, so I'd only
worry about this if DTDs get revised to handle namespaces. W3C XML
Schema has its own notions about this, but they seem mostly to give
elements an equal share of the "unqualified child" problem.
In practice, I think the way around this is to encourage people to treat
attributes with no namespace as if they had the same namespace as their
element. That doesn't have to mean a simple reassignment, though it's
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!