xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahesh P. Sooriarachchi" <mahes...@comview.com>
Subject Re: Yet Another Xerces/Xalan question
Date Thu, 02 Mar 2000 17:51:51 GMT
I dont see how building a standard leads to "not so clean and lean designs."
"not so clean and lean designs" are usually the result of a problem not well
thought... when you run into situations that are not aniticipated and start
trying to fit the existing design into the new moving target.  I guess the
best examples are Windows and the X86 architectures (if you can call them
standards)... lousy designs that have become standards by marketting and
kludges.

I dont see XML in this light though...  It does what it is designed to do
well, though a better API would have helped.
IMO building standards is like writing a good class library.  You have to
accept that you dont know all of the situations a user of the class lib
would run into, so take this into account for your design considerations.

--
Mahesh P. Sooriarachchi,
Sr. Software Engineer,
ComView Medical Systems
maheshso@comview.com
http://value.net/~mahesh

----- Original Message -----
From: Arnaud Le Hors <lehors@us.ibm.com>
To: <general@xml.apache.org>
Sent: Wednesday, March 01, 2000 12:35 PM
Subject: Re: Yet Another Xerces/Xalan question


> > The simple question is:  how can I move elements from one document to
another?
>
> Look at importNode().
>
> > The philosophical question:  If XML is so simple, why is DOM so
complicated?
>
> Because it's a standard. And unfortunately, in my experience, building a
> standard implies making compromises, which in general lead to not so
> clean and lean designs.
> This said, I would argue that XML is not so simple, but that's another
> topic.
> --
> Arnaud  Le Hors - IBM Cupertino, XML Technology Group


Mime
View raw message