[tei-council] list types and rends: bug 460

[Kevin Hawkins]

On 12/21/2013 12:49 PM, Sebastian Rahtz wrote:

>> "ordered": As we have discussed on the ticket and in meetings, "ordered"
>> and "unordered" are really meaningless; all lists are ordered and cannot
>> be otherwise. Neither are they types of list
> some danger here in flying in the face of the rest of the world, who
> use<ul>  and<ol>  happily. In most cases one would expect things like
> that to map to @type in TEI. But I accept your arguments
>
>> 	Recommendations:
>>
>> 	Remove "ordered" as a suggested value for @type.
>> 	Add "numbered" as a suggested value for @rend.
>
> hmm. I am less happy about that.  if, for example, you
> use a sequence like a), b). c), calling it “numbered” doesn’t
> really fit the bill. I’d actually keep @rend=“ordered”, simply
> cos the rest of the world does so.

But if in the spec we add examples of "numbered" that are not just 
arabic numerals but also roman numerals, Greek numerals, Cyrillic 
numerals, or sequences of letters.

>> "bulleted"/"bullets": This is clearly a rendering feature, not a type of
>> list.

> again, “bullets” is very specific rendering. I have always disliked that.
> I wish there was another word… But I think I can’t fight it.

In case it's helpful, I note that 
http://www.w3.org/wiki/CSS/Properties/list-style-image uses the term 
"list item marker".

--Kevin