[tei-council] note in sourceDesc
Martin Holmes
mholmes at uvic.ca
Wed Mar 12 12:54:35 EDT 2014
On 14-03-12 09:04 AM, James Cummings wrote:
> On 11/03/14 18:47, Sebastian Rahtz wrote:
>> b) your problem today that you want to constrain <p> very severely but don’t
>> want that to affect the header. the solution you propose (allowing
>> note in sourceDesc) is uncharacteristically limited and non-scaleable, imho.
>
> 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 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.
Cheers,
Martin
More information about the tei-council
mailing list