list of changes / deprecations?

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

list of changes / deprecations?

C. M. Sperberg-McQueen
Lou Burnard has just made me aware that a change in P5 has rendered an
ODD document I wrote a little more than a year ago invalid.

This leads me to a couple of questions; if they are answered in
documentation on the TEI-C web site, please point me to the relevant
documents; I’m happy to RTFM if I can find TFM.


1 Is there a list, in the current text of P5, or elsewhere, of changes
which will affect the validity of documents against the tei_all schema
or against schemas generated using ODDs?  Or at least those changes
which render invalid some documents which were previously valid?

I’m looking for a list one could scan to see whether and how one will
need to change one's documents to bring them into harmony with the
current version of TEI, a list which would tell me, for example, that
the ‘status’ attribute is no longer accepted on the ‘elementSpec’
attribute as of … (and perhaps give a pointer to the document in which
this decision is explained or motivated).

In [1], there is some mention of listing such things in the release
notes for a release of the Guidelines, but starting from [2] I have
not yet succeeded in identifying anything that looks like release
notes for any version of the Guidelines.  The page shown at [3]
(linked to from the phrase “Releases of the TEI Guidlines”) makes me
wonder whether by ‘release’, document [1] means only things like P1,
P2, … P5.  In that case, we should expect the list of changes to
appear only when the consortium issues a TEI P6.

[1] http://www.tei-c.org/Activities/Council/Working/tcw27.xml
[2] http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index.html
[3] http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TitlePageVerso.html


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?

I have used the site's search interface to search for 'deprecation'
(which I believe is how I found document [1] above) but have not found
a list of elements or attributes for which time is running out.  From
the wording of [1], I suppose I could simply scan the TEI-L archives
for the last few years, but I don't find myself willing to do that.


Thanks for any help readers of this list can give me.


********************************************
C. M. Sperberg-McQueen
Black Mesa Technologies LLC
[hidden email]
http://www.blackmesatech.com
********************************************
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: list of changes / deprecations?

Hugh Cayless-2
There is not a page listing deprecated features, but that might be a good idea. Release notes are to be found linked from  http://www.tei-c.org/Guidelines/P5/, and a search on "deprecated" is likely to prove useful. 

All the best,
Hugh

Sent from my phone. 

On Mar 24, 2017, at 14:57, C. M. Sperberg-McQueen <[hidden email]> wrote:

Lou Burnard has just made me aware that a change in P5 has rendered an
ODD document I wrote a little more than a year ago invalid.

This leads me to a couple of questions; if they are answered in
documentation on the TEI-C web site, please point me to the relevant
documents; I’m happy to RTFM if I can find TFM.


1 Is there a list, in the current text of P5, or elsewhere, of changes
which will affect the validity of documents against the tei_all schema
or against schemas generated using ODDs?  Or at least those changes
which render invalid some documents which were previously valid?

I’m looking for a list one could scan to see whether and how one will
need to change one's documents to bring them into harmony with the
current version of TEI, a list which would tell me, for example, that
the ‘status’ attribute is no longer accepted on the ‘elementSpec’
attribute as of … (and perhaps give a pointer to the document in which
this decision is explained or motivated).

In [1], there is some mention of listing such things in the release
notes for a release of the Guidelines, but starting from [2] I have
not yet succeeded in identifying anything that looks like release
notes for any version of the Guidelines.  The page shown at [3]
(linked to from the phrase “Releases of the TEI Guidlines”) makes me
wonder whether by ‘release’, document [1] means only things like P1,
P2, … P5.  In that case, we should expect the list of changes to
appear only when the consortium issues a TEI P6.

[1] http://www.tei-c.org/Activities/Council/Working/tcw27.xml
[2] http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index.html
[3] http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TitlePageVerso.html


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?

I have used the site's search interface to search for 'deprecation'
(which I believe is how I found document [1] above) but have not found
a list of elements or attributes for which time is running out.  From
the wording of [1], I suppose I could simply scan the TEI-L archives
for the last few years, but I don't find myself willing to do that.


Thanks for any help readers of this list can give me.


********************************************
C. M. Sperberg-McQueen
Black Mesa Technologies LLC
[hidden email]
http://www.blackmesatech.com
********************************************
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: list of changes / deprecations?

Lou Burnard-6
In reply to this post by C. M. Sperberg-McQueen
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>.


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: list of changes / deprecations?

C. M. Sperberg-McQueen
> On Mar 24, 2017, at 3:12 PM, Lou Burnard <[hidden email]> 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.

********************************************
C. M. Sperberg-McQueen
Black Mesa Technologies LLC
[hidden email]
http://www.blackmesatech.com
********************************************
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: list of changes / deprecations?

Lou Burnard-6
On 24/03/17 21:28, C. M. Sperberg-McQueen wrote:

>> On Mar 24, 2017, at 3:12 PM, Lou Burnard <[hidden email]> 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.
Loading...