Lists Home |
Date Index |
- From: Tyler Baker <firstname.lastname@example.org>
- To: Bill la Forge <email@example.com>
- Date: Thu, 11 Feb 1999 16:51:47 -0500
Bill la Forge wrote:
> One of the problems with DOM/namespace is the difficulty of manipulating
> the tree while tracking namespace scoping. A partially lazy approach seems to work:
> 1. Do NOT make any namespace transformations while building the tree.
> Instead, propagate the xmlns attributes to all children. (Use the inheritance filter.)
> 2. Manipulate the tree as desired.
> 3. Layer additional methods onto the DOM (you can either subclass things or
> use static methods) for accessing the unique name based on the xmlns attributes
> attached to the Element being accessed.
> 4. When converting from the DOM to SAX events or when creating a document from the
> DOM, drop xmlns attributes which are assigned the same value in the parent element.
The issue here is using the standard DOM interfaces to do the job. If you subclass the DOM
and use this new type you defined to manage namespaces, then you might as well not use the DOM
at all because this is a proprietary feature.
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)