XML API specification

[Richard Light]

In message <3.0.32.19970227083301.009c3960 at mailhost.criinc.com>, Derek
Denny-Brown <ddb at criinc.com> writes
>hmmm...
>
>How does is a Property which is a NodeList represented?
>What about a integer/string/boolean Property? 
>Or even worse, and integer list or a string list!  

The way it's done in the Property Set approach is to start by defining a
set of data types, some of which are 'lists of' more primitive data
types.  Excuse the home-grown notation:

{node}
{nodelist listof=node}
{enum} (for enumerated sets of values)
{char}
{string listof=char}
{integer}
{intlist listof=integer}
{strlist listof=string}
{compname} 
{cnmlist} (the last two relate to the Property Set defns themselves, and
don't concern us - I think!)

Once you've got that out of the way, you simply associate a data type
taken from this list with each property you declare.

In a similar spirit, every {node} has intrinsic properties:

PROPERTY SET: NODEPROP

Module: INTRBASE
    Property: CLASSNM (class name) [COMPNAME]
    Property: GROVROOT (grove root) [NODE]
    Property: SUBPNS (subnode property names) [CNMLIST]
    Property: ALLPNS (all property names) [CNMLIST]
    Property: CHILDPN (children property name) [COMPNAME]
    Property: DATAPN (data property name) [COMPNAME]
    Property: DSEPPN (data sep property name) [COMPNAME]
    Property: PARENT [NODE]
    Property: TREEROOT (tree root) [NODE]
    Property: ORIGIN [NODE]
    Property: OTSRELPN (origin-to-subnode rel property name) [COMPNAME]

Richard Light
SGML and Museum Information Consultancy
richard at light.demon.co.uk
3 Midfields Walk 
Burgess Hill
West Sussex RH15 8JA
U.K.
tel. (44) 1444 232067

xml-dev: A list for W3C XML Developers
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To unsubscribe, send to majordomo at ic.ac.uk the following message;
unsubscribe xml-dev
List coordinator, Henry Rzepa (rzepa at ic.ac.uk)