Draft DOM document

Hi all,

  I'm making progress on the DOM document, but I still have a lot of
  work remaining.  Attached is a snapshot of the document for group
  members to review before Wednesday's call.

  Please ignore the formatting, right now my main focus is the
  content.  Feedback on anything regarding the document would be
  greatly appreciated.

  I doubt section 1.1.1 Relationship with XML companion file to be
  clear enough, I'd like to hear opinions on what is missing if
  possible.

  If people have no objections, I'd like to propose that during the
  call on Wednesday, we start working on the green boxes.  We have to
  get ride of all the green boxes, they represent questions/issues
  that need to be resolved.

  Unfortunately, there are some differences between what we agreed
  upon in Cologne and what is in this document.  I tried to keep the
  number of differences to a minimum...

  1) We never talked about error handling and exceptions; all DOM
  specifications I know about throw exceptions when appropriate.  I
  think the WebCGM DOM should also use exceptions.

  2) I added an AppStructure interface because putting everything on
  the Node interface wasn't working.  The main reason is that too many
  APIs would have resulted in a strange behavior on the newly added
  namespace application structures.

  3) The third major change is that I've introduced
  getAppStructureAttr, setAppStructureAttr and removeAppStructureAttr
  to replace all the specific APS attribute calls we had enumerated.
  If people don't like this, I'm certainly open to reverting back this
  change.  There are two reasons why I made this switch; i) to be
  similar to the DOM getAttribute and setAttribute methods and ii) to
  reduce the number of API in our interfaces.

  Please let me know what you think!

  Regards,

-- 
 Benoit                 mailto: