[tei-council] specDesc spec vs. reality

[Lou Burnard]

On 08/12/13 23:09, Sebastian Rahtz wrote:
> 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.

It *used* to be "all those available" before we invented attribute 
classes. Then we argued quite a lot about whether it should include all 
those available by inheritance or only all those locally defined. Then 
you implemented "only those explicitly stated"
>
>> 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.

Good. Not unfortunate at all! Please make it so Mr Spock.

>
>> 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}”>

That just punts on deciding what "full" or "medium" means, or leaves it 
to implementors to decide

You could  say  <specDesc key="valListkey"/> if valLists were 
identifiable, but as they're not something more precise is needed: how about

<specDesc atts="a b c" withValList="a b">

defaulting to "no valList display".

If a valList appears in a content model, then  I assume it will always 
be displayed in the doc: this doesn't affect what happens in a 
<specDesc> though, which is blessedly silent on the topic of content models.

While we're looking at this, I have long wanted some way of grabbing 
<egXML>s from the specs for display in the descriptive prose (or indeed 
vice versa)






> --
> Sebastian Rahtz
> Director (Research) of Academic IT
> University of Oxford IT Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>