[tei-council] list/@type example

[Martin Holmes]

On 13-04-22 09:22 AM, Kevin Hawkins wrote:
> Well, a computer doesn't necessarily know that the labels "(1)" and
> "(2)" indicate order.  In order to classify lists with various labeling
> systems, such as "(1)", "1)", "a.", "i.", and many others, as all being
> ordered, you might want to use @type.

This was the heart of our discussion, surely: we decided (and we've 
already partially implemented) a change from @type to @rend for this 
sort of thing. Types of list are things like "ingredients"; ordering, 
numbering, bulleting and all that sort of thing is rendition, so it uses 
@rend.

So if we keep "ordered" here, it should become another token in @rend:

<list rend="runon ordered">

Cheers,
Martin

>
> --K.
>
> On 4/22/2013 11:22 AM, Martin Holmes wrote:
>> Hi all,
>>
>> I'm doing the conversion of list/@type to @rend, and came across this
>> rather odd example from the CO chapter (full quote below):
>>
>> <list rend="runon" type="ordered">
>>          <label>(1)</label>
>>          <item>My first rough manuscript, without any
>> intermediate copy, has been sent to the press.</item>
>>          <label>(2)</label>
>>          <item>Not a sheet has been seen by any human
>> eyes, excepting those of the author and the printer:
>> the faults and the merits are exclusively my own.</item>
>>       </list></egXML>
>>
>> (There are two of these.)
>>
>> I contend that @type="ordered" is pointless here, because the numbering
>> is supplied in any case by the<label>, so I propose to remove it. All
>> who disagree please say nay loudly and soon; silence = assent.
>>
>> Full quote:
>>
>> <p>Each distinct item in the list should be encoded as a distinct
>> <gi>item</gi>  element.  If the numbering or other identification for the
>> items in a list is unremarkable and may be reconstructed by any
>> processing program, no enumerator need be specified.  If however an
>> enumerator is retained in the encoded text, it may be supplied either by
>> using the<att>n</att>  attribute on the<gi>item</gi>  element, or by
>> using a<gi>label</gi>  element.  The following examples are thus
>> equivalent:
>> <egXML xmlns="http://www.tei-c.org/ns/Examples" source="#GibAut">I will
>> add two facts, which have seldom occurred in
>> the composition of six, or even five quartos.
>> <list rend="runon" type="ordered">
>>          <label>(1)</label>
>>          <item>My first rough manuscript, without any
>> intermediate copy, has been sent to the press.</item>
>>          <label>(2)</label>
>>          <item>Not a sheet has been seen by any human
>> eyes, excepting those of the author and the printer:
>> the faults and the merits are exclusively my own.</item>
>>       </list></egXML>
>> <egXML xmlns="http://www.tei-c.org/ns/Examples"  source="#GibAut">I will
>> add two facts, which have seldom occurred in
>> the composition of six, or even five quartos.
>> <list rend="runon" type="ordered">
>>          <item n="1">My first rough manuscript, without any
>> intermediate copy, has been sent to the press.</item>
>>          <item n="2">Not a sheet has been seen by any human
>> eyes, excepting those of the author and the printer:
>> the faults and the merits are exclusively my own.</item>
>>       </list></egXML>
>>
>> Cheers,
>> Martin

-- 
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)