Lists Home |
Date Index |
- From: Tyler Baker <firstname.lastname@example.org>
- To: David Megginson <email@example.com>
- Date: Wed, 10 Feb 1999 18:45:43 -0500
David Megginson wrote:
> Rick Ross writes:
> [about preprocessing namespaces for the DOM]
> > Doesn't that presume that a "document" exists?
> Preprocess your information, whatever its source.
>From an entire database. Pass over the entire document tree and prepreprocess everything
before actually presenting it to the application. This is not practical. In my limited
experience on these matters I have seen this tried before and with horrendous results.
Nevertheless, it does not take a computer scientist to see the real world problem with this
> > There should not be a requirement for the data to get emitted as
> > XML, just so it can be reparsed - the XML-implied DOM
> > representation would suffice beautifully if not for this namespace
> > problem.
> I cannot understand why you would have to do this.
There is a big difference between "having to do something" and doing something because it
makes perfect sense from a real world perspective. Preprocessing the entire source tree just
do handle namespaces hardly makes a case for supporting namespaces at all in a product. You
can have the most elaborate features in the world for an application but if they don't work in
the real-world problem domains of real people, then they are pretty useless no matter what
their original intentions were. "Namespaces in XML" and the hacked up manner in which you
need to deal with them in XML is a prime example of a specification not realistically trying
to solve the problems of its target audience.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)