Re: DOM Confusion
At 09:41 AM 4/30/98 -0400, you wrote: > > >My confusion comes from the fact that XMLNode doesn't inherit from >Node in the DOM spec. Thus, XMLNode doesn't have functions on >it like Node.getFirstChild(), or does it? This was a typo (mine!). XMLNode should have been defined to inherit from Node. Sorry for all the confusion this has caused. > >So why not dispense with XMLNode altogether and make the Node >interface implement these functions? Simply define that expandEntities >is "always true" for HTML documents, or some such. Something like that is under consideration; I can't be more specific because the methods for doing this have not been nailed down yet. > > >3) extra nit: the function names are overly verbose and option #2 >would solve it. > Whimper .... the function names are verbose because of the astonishingly complex web of constraints that they must satisfy. "Brevity" is actually one consideration, but less important than clarity, internal consistency, avoiding clashes with existing APIs in widespread use, compatibility with the name scoping scheme in ECMAScript .... etc. Mike Champion 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/ 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...)
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format