A Plea for Schemas

[uche.ogbuji at fourthought.com]

Tim Bray:
> > [...]  I think large parts of the the 
> > "communal understanding" live in wetware between human ears and in messy
> > procedural code.

Richard Lanyon:
> Which is why, parenthetically, it's often quite awkward to process XML
> using a declarative, rather than procedural, language.

Eh, what?  This seems a blatant non-sequitur.  The fact that much legacy code 
is procedural is a historical accident and has nothing to do with present and 
future XML-processing.

To some minds, and for some purposes, procedural approaches are awkward: in 
other cases declarative approaches are awkward, but if one had to pick one 
with intrinsically less "awkwardness" for XML-processing, I would argue for 
the declarative approach.

-- 
Uche Ogbuji
FourThought LLC, IT Consultants
uche.ogbuji at fourthought.com	(970)481-0805
Software engineering, project management, Intranets and Extranets
http://FourThought.com		http://OpenTechnology.org



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)