From: "Arjun Ray" <aray@[...].net> 

>  Rather, it would be up to the document to map
>  its various parts to the various schemas that the instance composer had to
>  have known about. 

This seems like a less constrained version of XSD's substition groups, but in
reverse.

Your element declaration says
  <!ELEMENT div (title, ( p | table | list )> 
and then you provide some external declaration to say
  "when it says 'table', you can/should use table from the HTML namespace"
and/or
  "when it says 'table', you can/should use tbl from the CALS namespace"

This is interesting because it provides a distinctively different approach to
handling the composition of schemas than, I think, XSD or RELAX NG.  

The biggest use for namespaces I ever saw in SGML was exactly that
there were two table languages (I think CALS and WP) that someone
wanted to have both, but they both used some of the same element
names.

Cheers
Rick Jelliffe

-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org> 

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>