[
Lists Home |
Date Index |
Thread Index
]
Hi Paul,
Well, outside have having listHeading as an optional first element of a
regular list, I see it this way: if you have a special list with the
special element as its first element, then you have a special list with
its own name (e.g. "headedList"). If you have a special name for a list
with a special first element, then (as long as the special element is
always first) you no longer need to identify the special element--you
could just have this special list type for which the first element was
always special.
This is just thinking through the possibilities. I was just curious
which of the possibilities had been implemented anywhere, and it looks
like the optional special first element of a "regular" list is the most
sensible.
Bob
Paul Prescod wrote:
> Bob DuCharme wrote:
>
>> DocBook offers seven kinds of lists, but none that quite fit this
>> bill: I'm looking for a list with a content model that is a rough
>> equivalent to a <em><li/></em> followed by li+. That is, a list where
>> a processing application is to assume that the first list item is
>> something to be set apart from the others through whatever
>> capabilities a given platform offers. Has anyone ever heard of such
>> an animal in any DTD or schema that might serve as a model for me?
>
>
> If the first one is special, why doesn't it have its own element type
> name? i.e. "list heading".
>
> Paul Prescod
>
>
> -----------------------------------------------------------------
> 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>
>
>
>
|
