Print

Print


On 24/03/17 21:28, C. M. Sperberg-McQueen wrote:
>> On Mar 24, 2017, at 3:12 PM, Lou Burnard <[log in to unmask]> wrote:
>>
>> On 24/03/17 18:57, C. M. Sperberg-McQueen wrote:
>>> 2 Is there a list on the TEI-C site of pending changes,
>>> e.g. deprecations whose term has not yet expired, which do not
>>> currently affect the validity of one's documents, but are expected to
>>> in the future?
>>>
>> A specification which is in this state gets an attribute @validUntil specifying the planned date at which it will be withdrawn. So one easy way to make such a list would be by means of an Xpath such as "document('http://www.tei-c.org/release/xml/tei/odd/p5subset.xml')//*[@validUntil]"
>>
>> It's much less easy to find a list of things which have been both deprecated and withdrawn since a given date, other than by scanning the release notes since that date.  The safest thing to do, if you just want your ODD to go on working, is to tie it to a particular release date by including a value for the @source attribute on its <schemaSpec>.
> If I understand correctly, that will ensure that the TEI declarations used
> always come from the specified version.  That may be useful.
>
> In this case, the proximate problem is that a change has made the ODD
> document — not the schema generated from it, and not the documents
> valid against that schema — invalid against the current version of
> tei_all.rng.  tei:schemaSpec/@source is not going to help with that.
Ah yes, my mistake. So you'd need to recompile tei_odds.odd (or whatever 
the ODD source for your ODD validation schema is) against an 
appropriately dated  @source.