W3C home > Mailing lists > Public > www-dom-ts@w3.org > June 2001

SV: Second attempt at DOM 1 generation

From: Dimitris Dimitriadis <dimitris.dimitriadis@improve.se>
Date: Tue, 5 Jun 2001 20:45:01 +0200
Message-ID: <9F67DC27F4CCD311ABA600508B6A66A44A66E6@VXOIMP1>
To: "'Curt Arnold'" <carnold@houston.rr.com>, www-dom-ts@w3.org
comments inlined

-----Ursprungligt meddelande-----
Från: Curt Arnold [mailto:carnold@houston.rr.com]
Skickat: den 1 juni 2001 10:19
Till: www-dom-ts@w3.org
Ämne: Second attempt at DOM 1 generation


My second attempt is at http://home.houston.rr.com/curta/domtest/dom1.zip
<http://home.houston.rr.com/curta/domtest/dom1.zip>  which includes
minimally checked schema, DTD, documention and one sample.
 
The following significant changes from previous versions.
 
1) <declare> was changed to <var> to eliminate conflict with
HTMLObjectElement.declare
 
I'm open to other suggestions.  Basically:
 
<declare var="node" type="Node"/>
 
has been replaced by
 
<var name="node" type="Node"/>
 
2) <size> changed to <hasSize> and <add> to <plus> to avoid other conflicts
 
3) assertDOMException now uses a child element for the code
 
<assertDOMException>
    <INDEX_SIZE_ERR>
        <substringData obj="str" start="-1" count="5"/>
    </INDEX_SIZE_ERR>
</assertDOMException>
 
The content model for the child elements is determined by seeing if the text
description has
code name + ":".  Seems to work okay, but is a kludge.  "data" gets
generated twice for
one code and needs to be manually removed.
 
4) Used named templates for organization, pure static schema content
isolated
 
5) <package> added, <suite> removed
 
6) interface optional (but only one choice) when unambiguous
 
Things that need to be done:
 
1) Add optional id attributes to everything that doesn't already have them
(assertions and tests have required IDs)
 
[dd] OK  
 
 2) Write transform that will extract interface information from DOM
specification docs and generate a compact representation
 
3) Write equivalent transform to produce DTD
 
[dd] to simplify things, we could run the schema through a schema editod and
look through it and make any changes by hand
 
4) Explore generating schema/DTD from DOM 2, DOM 3 or SVG spec
 
 
Received on Tuesday, 5 June 2001 14:45:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 April 2009 12:58:44 GMT