[tei-council] *Spec content inconsistency
Lou Burnard
lou.burnard at retired.ox.ac.uk
Mon May 6 10:29:24 EDT 2013
Care to tell us more about your "odd4odds" schema?
Maybe we can load some of it into the "foxglove" proposals -- e.g.
making content models contingent on context is already there
On 06/05/13 13:52, Syd Bauman wrote:
> Great minds think alike: already done for the new "odd4odds" schema
> we will be using at our Customization seminar later this week. (This
> is the schema that used to be called brown_odds, but y'all didn't
> like the name.)
>
> But I am hesitant to create such a constraint in the Guidelines
> proper for fear of breaking existing ODDs.
>
>>> model.glossLike*, model.descLike*,
>>>
>>> you might be tempted to make <desc> mandatory always,
>>> but sadly that makes working in change or delete mode
>>> unreasonably hard.
>> We could do this with Schematron, surely --
>>
>> "if (not(@mode='delete' or @mode='change')) then child::desc"
More information about the tei-council
mailing list