Lists Home |
Date Index |
- From: Tyler Baker <firstname.lastname@example.org>
- To: David Megginson <email@example.com>
- Date: Wed, 10 Feb 1999 17:48:49 -0500
David Megginson wrote:
> Rick Ross writes:
> > Our XSL processor is designed to work with any XML parser that
> > implements DOM and SAX support - a fantastic benefit of reliance on
> > open standards. Unfortunately, if the DOM api is not rich enough
> > to support namespaces in XML effectively, then DOM becomes a
> > second-rate interface for XML/XSL application solutions.
> Although people would like more elegant solutions, there is no reason
> not to do namespace processing on the document before offering it
> through a DOM interface -- the names will not be XML names, but
> everything should still work.
Then the document is illegal. Namespaces can essentially be any set of characters you want.
When you replace the prefix with a namespace, you are creating an illegal XML Name as you
already stated. Should the DOM reflect a legal XML document or should the DOM allow anything
you want to serve as element and attribute names.
Last but not least, in XSL if you use this approach you suggested for expanding QNames, then
within ElementExpressions and AttributeExpressions, you will in essence run into problems with
parsing these expressions as characters like '@' and '/' and '|' are significant and will
screw up the entire PathExpression you are parsing.
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)