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


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: ATTLIST question

[ Lists Home | Date Index | Thread Index ]
  • From: John Cowan <jcowan@reutershealth.com>
  • To: James Gray <jmgii@yahoo.com>, "xml-dev@xml.org" <xml-dev@xml.org>
  • Date: Thu, 28 Sep 2000 15:21:59 -0400

James Gray wrote:

> I'm trying to create a DTD that will incorporate an
> attribute list that will allow  the following case:
>   1. Define optional values for an element
>   2. Require one of the options be present
>   3. Not allow any option other than those listed

You mention attribute lists, but then talk about the value of an element.
DTDs don't allow you to control the value (content) of an element as such.

> I'd like to have a "shirt"
> element that is only allowed to the values:
> S, M, LG, XL

In order to make this work, we have to reformulate it as a "shirt"
element with an attribute "size" or the like.  In that case, the
following ATTLIST declaration will work:

<!ATTLIST shirt
	size (S|M|LG|XL) #REQUIRED>

This will require the size attribute to be present in all shirt elements,
and will allow its value to be "S", "M", "LG", or "XL".

> If the <shirt> element is filled with "XS" or "XXL",
> I would be able to reject it based on my DTD?

Yes, provided you use a validating parser.
There is / one art                   || John Cowan <jcowan@reutershealth.com>
no more / no less                    || http://www.reutershealth.com
to do / all things                   || http://www.ccil.org/~cowan
with art- / lessness                 \\ -- Piet Hein


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

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