4 ms·
The way XML does namespaces is one of the best things about it - you can host any XML dialect within another, with no name clashes, and without losing the schem
by int_19h 6y ago
The way XML does namespaces is one of the best things about it - you can host any XML dialect within another, with no name clashes, and without losing the schema identity of embedded parts. Infinite data composability, subject only to the constraints placed by schema authors. And namespaces are URIs, so they can be URLs.
The bad smell was mostly coming from all the things inherited from SGML - CDATA, entities etc. Although I would also add that separation into elements and attributes is not a particularly convenient way to model many things; it mixes up differences that should really be orthogonal (ordered/unordered, atomic/composite etc).
- recursive 6y agoI don't see why you even need the concept of namespaces to do that. In my schema, I have a <foreignDocument> element, whose contents is defined to be a foreign document.