OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] Effective DOM (was RE: [xml-dev] Effective XML)

[ Lists Home | Date Index | Thread Index ]

Leigh Dodds wrote:
> >  The reason for not allowing
> > tagName to be changed has been explained to me (that an implementation
> > may use different classes to implement different elements), but
> > doesn't seem sufficient (allowing tagName to be mutable or throw some
> > exception may be tolerable, and being able to ask the DOM
> > implementation if it allows general element renaming would be useful.
> I wasn't aware of that. Interesting. Presumably this is to allow custom
> DOM implementations (e.g. for SVG) to substitute their own implementations?
> Is this feature used in practice?

Not only custom DOM implementations, but also DOM wrappers around other
APIs. If you had getTagName() return a static constant or
getClass().getName() (excuse my Java), what meaning would changing the
tag name have?



News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS