[tei-council] <specList>s in Guidelines: exhaustive or selected?

[Kevin Hawkins]

On 12/28/12 12:16 PM, Lou Burnard wrote:
> On 28/12/12 17:06, Kevin Hawkins wrote:
>> I am unclear on whether <specList>s in the Guidelines are supposed to
>> list all child elements or just those that are most relevant.
>
> That is a stylistic issue. A specList will typically list all the
> elements discussed within a given section. Sometimes (quite often in the
> Header) sections are organised in terms of the hierarchic structure but
> this is definitely not necessarily the case: you can group the elements
> discussed in a section in any way that makes sense (as for example in
> the Core chapter). You can also choose not to discuss all the elements
> which might appear as content for the elements being discussed -- lots
> of elements have a content model of paraContent: you wouldn't want all
> the components of para Content to be listed anew each time each such
> element is discussed.

Okay, that all makes sense.  I've clarified in tcw20.

>     This has
>> come up in http://purl.org/TEI/FR/3585570 , and I would like to clarify
>> it at
>> http://www.tei-c.org/Activities/Council/Working/tcw20.xml#body.1_div.1 .
>
> I've commented on the ticket.

Thanks.

On the ticket, Lou suggests that we might want the ability to specify a 
model class (and its members) within a specList.  I've created a new 
ticket for discussion of that: http://purl.org/TEI/FR/3598775 .