[tei-council] specDesc spec vs. reality

[Sebastian Rahtz]

On 8 Dec 2013, at 22:43, Lou Burnard <lou.burnard at retired.ox.ac.uk> wrote:

> 
> a) should the attributes to be displayed for a <specDesc> be only those specified by @atts, or all those available?
> 
by default, you mean? it can’t be all those available, surely.

> b) should inherited attribuites be treated differently from locally-defined ones? i.e. can @atts request display of an inherited attribute?
> 
> ///
> Regarding (b) I don't think requesting an inherited attribute should be regarded as an error. We don't make that distinction elsewhere (e.g. I can modify an inherited attribute in a elementSpec) and it is certainly not the way I remember things being done before.

I am inclined to agree, unfortunately, that if you specify atts=“xml:id next resp” it should go and get those from attribute classes. 

> I have an open mind on displaying valLists: how would that be switched on or off?

same applies if the content model of the element is a <valList> too.

all I can think of is to say <specDesc display=“{full|medium|minimal}”>
--
Sebastian Rahtz
Director (Research) of Academic IT
University of Oxford IT Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431