Lists Home |
Date Index |
David Megginson wrote:
> Aside from those minor problems, though, the main difficulty with XML
> is precisely what Jonathan says -- it is meant for both documents and
> data, and as a result, is optimized for neither. What we need is not
> a new, simpler XML, but separate, more specialized layers on top of
> XML for data and documents (**). RDF, Topic Maps, and the SOAP
> serialization format all represent candidates for a standard data
> layer; unofficially, XHTML and DocBook are often used as the
> building more specialized documentation formats. Maybe we need
> something simpler than any of that to start with.
We have two prescribed layers already:
1: Infoset + W3C Schema + QNames
2: RDF + Model Theory + URIs
They're tuples of models in the form (data, typing, naming). You can
throw XML out tommorow and run with both or either of those two. The
likes of SOAP and OWL come in above those again.
The difficulty is bad engineering on top of XML, and a lack of
appreciation about what the benefits of using XML syntax as a
carrier are. There's no difficulty with XML.
Bill de hÓra