Lists Home |
Date Index |
- From: "Ingo Macherius" <Ingo.Macherius@TU-Clausthal.de>
- To: email@example.com
- Date: Mon, 10 Nov 1997 13:18:58 +0000
> From: "Thorsten Kitz" <firstname.lastname@example.org>
> Subject: List of possible choices in a DTD
> I have a really simple problem: I like to define a choice list in a
> DTD, eg for element <Weekdays> a list of possible values like
> "Monday", "Tuesday", etc.
So the name of the weekday is data content, not structural
information. Consider how this is done with HTML 4:
<!ELEMENT SELECT - - (OPTION)+ -- option selector -->
<!ELEMENT OPTION - O (#PCDATA) -- selectable choice -->
so a typical instance would be
Display of the list is a processing semantic, that can't be expressed
in the DTD. It's up to your application to make this a choice list,
eiher like a pulldown menu, a item list, etc.
Of course you could use specific names for your list, like
<!-- or <monday/> if no content is necessary -->
but the more tags you have, the more compicated your stylesheets etc.
become. To me names of days are data, not structure. Anyway, the last
example is different, as it may contain information *about* the
weekdays, e.g a hourly schedule.
Alternatively, weekdays could be attributes
Choice is up to you, but nowhere I can see a need for entities.
BTW: XSL does not say anything about forms ! Should there be a
standard forms set, just like there are CALS tables and MathML ?
Ingo Macherius // L'Aigler Platz 4 // D-38678 Clausthal-Zellerfeld
Information!=Knowledge!=Wisdom!=Truth!=Beauty!=Love!=Music==BEST (Frank Zappa)
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)