[tei-council] Pure ODDness
Sebastian Rahtz
sebastian.rahtz at it.ox.ac.uk
Wed Nov 20 11:39:32 EST 2013
On 20 Nov 2013, at 16:29, Martin Holmes <mholmes at uvic.ca> wrote:
>> c) introduce a model.contentPart element called <pcdata> and say
>> <content><pcdata></content> (or some better name)
>>
>> Preferences? Alternatives?
>
> I go for c); it's parallel to RelaxNG and will be easier to understand.
as opposed to being parallel to XSD, and therefor being easier to
understand for a whole other group of people?
>
>>
>> 2. co-existence
>>
>> I think we agreed that the old and the new method of defining content
>> should co-exist at least for the next release. How should that be done?
>>
>> a) change the content model of <content> to permit either
>> model.contentPart or macro.schemaPattern
>> b) change macro.schemaPattern to permit either model.contentPart or
>> macro.anyXML
>> c) define a new element (howabout <model>) containing model.contentPart
>> ; allow both that and current <content> initially, then deprecate <content>
>
> c) seems cleaner to me.
i’d put in an extra small plea for a)/b) on the grounds that this is already
implemented and tested….
Sebastian
More information about the tei-council
mailing list