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: Paul Prescod <papresco@technologist.com>
  • To: xml-dev@ic.ac.uk
  • Date: Fri, 10 Oct 1997 09:58:20 -0400

akirkpatrick@ims-global.com wrote:
> 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).

That's close, but not quite correct. According to my terminology, why
you've described is subtyping. If you *inherit* a content model then you
get that content model -- unchanged. We could invent straightforward
mechanisms to allow you to inherit content model parts but I'm not sure
yet if it is worth the extra syntax. Especially if we were to move to
structured attributes. Then today's complex content models could be
broken up into small components and the benefits of inheriting content
model parts would be reduced.
 Paul Prescod

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