Lists Home |
Date Index |
Elliotte writes about:
> That seems to me to fall into the same territory as caring about the
> difference between character and entity references and CDATA
> sections: it's relevant to one style of editors. It's really pretty
> pointless for everything else. SAX, DOM, JDOM, XOM, etc. just aren't
> really up to the needs of an source code based XML editor, but that's
> OK. Source-obvious XML editors (i.e. programs like XML Spy that
> expose the XML to the author but not programs like OpenOffice that
> don't show the XML to the end user) are a use case with lots of
> strange requirements that just aren't present in any other use case.
> Adding the features necessary for editors would immensely complexify
> an API for other, more common use cases. Editors justifiably need a
> different API.
I'm not sure that I accept that the difference between "editor" APIs and
"processing" APIs is that clean-cut in practice, though there's
certainly a cultural divide between developers who are creating markup
by marking up information (which I think you're categorizing as
"editor") and developers who expect information to come prepackaged in
neat little boxes.
There's certainly room for both, but I'm definitely tired of working in
neat little boxes, whether or not I'm explicitly editing a document.
Hopefully some others may find it interesting to look beyond the box.
Simon St.Laurent - SSL is my TLA
http://simonstl.com may be my URI
http://monasticxml.org may be my ascetic URI
urn:oid:22.214.171.124.4.1.6320 is another possibility altogether