[Home] [By Thread] [By Date] [Recent Entries]
>It seems then that isSpecified could be used to filter-out excess >attributes when attempting to recreate a document from a DOM That's the intent. >In looking over the Parser/DOM from JavaSoft, it looked like isSpecified >is always true, even for default values. > >In looking over the Docuverse DOM, it looked like isSpecified is also >always true, except for updates made by the application, for which it >is always false. If so, my reading is that those are deviations from the DOM Recommendation -- in other words, bugs. I sorta undertand why Docuverse could have gotten this wrong; the spec's description starts of with a discussion of "original document", which is probably an error... though the summary lays out the intent quite precisely in terms of assigned versus default values. I'll suggest a clarification of the document; you may want to contact your DOM suppliers and suggest that they recheck the definition of this parameter. ______________________________________ Joe Kesselman / IBM Research Unless stated otherwise, all opinions are solely those of the author. xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1 To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|

Cart



