[tei-council] note in sourceDesc

[Martin Holmes]

On 14-03-12 10:29 AM, James Cummings wrote:
> On 12/03/14 16:54, Martin Holmes wrote:
>>> It might be desirable to be able to limit the content of <p> in
>>> the header (or text), but the you get into the question of
>>> whether we really should be having two different elements.  I
>>> still support the replacement of a highly limited <para> (or
>>> whatever) in the header.
>>
>> I really don't like the idea of two separate elements. What I'd prefer
>> is that Pure ODD enable us to define the content model of elements based
>> on context; that this be convertible into models based on complexTypes
>> in XSD; that it be convertible into Schematron in RelaxNG; and that DTDs
>> leap into the dustbin of history.
>
> I think I would prefer that as well. I can understand that it
> might be confusing for some people ("I can put element X in my
> paragraph here, but why not there?!"), but I think we could live
> with that. And you know I'd prefer if we didn't support DTDs any
> more.
>
>> I know this is a bit distant, but I would like us to consider whether it
>> should be one of the aims of moving to P6.
>
> Do you feel this is a change that necessitates a move to P6? My
> reading of the Birnbaum Doctrine
> (http://www.tei-c.org/Activities/Council/Working/tcw09.xml)
> doesn't make that necessary.  (Though it is, of course, a
> significant break of backwards compatibility.)

I think dropping DTDs would mean a move to P6. Lots of people still use 
them, and will complain if they disappear from P5.

Whether the Pure ODD stuff justifies a P6 would depend on whether we 
actually made use of that functionality in the standard. If we ourselves 
define two separate content models for <p>, one for the header and one 
for <text>, then I think the backward-compatibility problem would be 
significant enough to warrant a change. If we just provide this 
functionality for customizers to use themselves, then it wouldn't.

So we could envisage a process where we put the changes in place to 
support this, in the existing P5 universe, without using it ourselves; 
then when we come to P6, we can take full advantage of it to build a 
more sophisticated document model.

Cheers,
Martin