OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: Inheritance/defaulting of attributes

[ Lists Home | Date Index | Thread Index ]
  • From: akirkpatrick@ims-global.com
  • To: xml-dev@ic.ac.uk,ricko@allette.com.au
  • Date: Thu, 9 Oct 1997 17:34:12 +0000

Firstly, I thought Paul's little essay on subclassing and inheritance
in DTDs was fascinating.

Re the question below from Rick: as I understood Paul, if an element
inherited a content model, it could define a more restrictive model for
itself but still had to be valid according to the parent model (see   
below).

The question I have is about restricting the use of generic elements in   
the
instance. For example, suppose we have:

<!ELEMENT para (#PCDATA | inline | block)*>
<!ELEMENT inline (#PCDATA)>
<!ELEMENT block (para+)>

<!ELEMENT title TYPEOF para (#PCDATA | inline)*>

<!ELEMENT filename TYPEOF inline>
<!ELEMENT emphasis TYPEOF inline>
...

<!ELEMENT admon TYPEOF block (title?, para+)>
<!ELEMENT note TYPEOF admon>
<!ELEMENT tip TYPEOF admon>
..
(look familiar?)

How do we stop the authors actually using <inline> and <block> which
have little meaning as they are? Do we need a "pure virtual" syntax
which indicates that an element type cannot be instantiated in the
instance?

Either way, I like this idea a lot. Does the instance syntax proposal for
XML take any of this into account? If so, I might be converted, on the
assumption that this type of thing won't make it into the SGML revision.

Alfie.

 ----------
From:  ricko@allette.com.au
Sent:  Thursday, October 09, 1997 4:10 PM
To:  xml-dev@ic.ac.uk; Kirkpatrick, Alfie
Subject:  Re: Inheritance/defaulting of attributes

 --------------------------------------------------------------------------  
 --
Has anyone come up with a good solution for what order element
types can be in if you have inheritance?

<!ELEMENT cat  (head, whiskers, paw+, tail)>
<!ELEMENT kitty  (cry) INHERITS cat>

is all very well, but what is the resulting content model?
It sounds like people expect it to be (using the SGML "&"
connector, which is not in XML):

<!ELEMENT kitty (( head, whiskers, paw+, tail ) & cry )>
   

which is not very satisfactory IMHO.

Rick Jelliffe

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)





 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS