I'm looking at the following section: http://www.w3.org/TR/DOM-Level-2/core.html#Core-Document-importNode What is see is that the Level 2 specification says [unlike what you stated] that: Entity nodes can be imported, however ... Notation nodes can be imported, however ... That means for me to build a conforming implementation, I would need to support importing entities and notations, however meaningless that capability is. If the decision to allow importing these nodes is truly deferred until DOM Level 3, then I recommend the following change to that section: Entity nodes cannot be imported. Notation nodes cannot be imported. That way, a conforming implementation can take the easy way out, and the current API won't break if in the future you decide that there is a sensible reason to allow these nodes to be imported. Keith -----Original Message----- From: www-dom-request@w3.org [mailto:www-dom-request@w3.org]On Behalf Of keshlam@us.ibm.com Sent: Thursday, April 13, 2000 6:20 PM To: www-dom@w3.org Cc: www-dom@w3.org Subject: RE: createEntity and createNotation and importing these Basically, DOM Level 2 left what we had done in Level 1 unchanged. createEntity and createNotation, and whether it makes sense to allow importing these nodes, will be addressed as part of DOM Level 3's Content Model work. ______________________________________ Joe Kesselman / IBM ResearchReceived on Thursday, 13 April 2000 18:46:26 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:24:51 GMT