[tei-council] attribute lists

[Lou Burnard]

I wondered whether the class names should be followed by the lists of 
class members, as elsewhere?

Laurent's suggestuion would save space, at the risk of offending purists 
like me who think that the attribute @foo on element x is a different 
thing from the attribute @foo on the element y


Laurent Romary wrote:
> That's exactly the direction to follow. I am myself very bad at  
> presentation things. But I can already see the usefulness of it.
> 
> Would it make sense to have too views in the "used by" (one after the  
> other or toggling), that is:
> - like is now, sorted by elements
> - the other way round, sorted by attributes, with the list of  
> corresponding attributes behind (e.g. @value[eLeaf, eTree, iNode,  
> node, etc.])
> 
> Le 11 avr. 08 à 11:50, Sebastian Rahtz a écrit :
> 
>> starting to do action about better lists of datatypes and attributes
>> etc, can I ask you to look at
>> http://tei.oucs.ox.ac.uk/P5/Guidelines-web/en/html/ref- 
>> data.pointer.html
>> and comment? it looks like a dogs dinner. any suggestions for a  
>> layout?
>>
>> list of all attributes is still to come
>>
>> -- 
>> Sebastian Rahtz
>> Information Manager, Oxford University Computing Services
>> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>>
>> _______________________________________________
>> tei-council mailing list
>> tei-council at lists.village.Virginia.EDU
>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
> 
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council