Use cases for XML failure (was Re: #2 Re: [SML] Whether to support Attribute or not?)

[Don Park]

>> My experience with the DOM WG *and* my recent day jobs  is
>> similar -- the least useful parts of XML cause the most work 
>for people
>> supporting it. Both CDATA sections and external parsed 
>entities caused
>> *massive* amounts of work and contention for us in devising 
>the DOM API.
>
>Sure, so what? I was part of those battles, and I don't see 
>the relevance.
>
>Come up with some use cases where XML simply *cannot* be deployed in a
>handheld device, and SML could, and I might even start to see the point
>of SML. I'd be more convinced if you projected the technological trends
>over a year or two, and could still have the same use-case a year from
>today.

Gavin,

I was part of those battles too and I agree entirely with
Michael.  DOM got the nasty-end of the stick because of
arcane features of XML and others (i.e. namespace spec).

SML is not about doing what XML *cannot*.  SML is about
creating an ideal tool.  We are not asking people to cut
steak with a fork so please let the knife and the fork
lie side-by-side.

We can gang up on the 'spoon' and 'chopstick' folks
later. <g>

Best,

Don Park    -   mailto:donpark at docuverse.com
Docuverse   -   http://www.docuverse.com


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo at ic.ac.uk the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)