[tei-council] new validUntil=

[Kevin Hawkins]

Below ...

On 5/16/2013 3:27 PM, Syd Bauman wrote:
> 4. status of "deprecated" of status=
> -- ------ -- ------------ -- -------
> I presume that the "deprecated" value of the status= attribute of
> att.identified is the first thing to be deprecated with the new
> validUntil= attribute, and have done so. Should the entire status=
> attribute of att.identified be deprecated by validUntil=, or do we
> think status= still serves a purpose? We do not (currently) use any
> value other than "deprecated" in the source of the Guidelines.

When we first implemented this ( 
http://sourceforge.net/p/tei/feature-requests/118/#724e ), we had in 
mind other values, but we haven't used them.  On reflection, I don't 
think we generally introduce things we consider unstable, and if we do, 
we don't know at the time whether they will end up being unstable.  So I 
think we should just deprecate the whole @status attribute.  I've noted 
this at

http://wiki.tei-c.org/index.php/Practices_no_longer_recommended_or_now_deprecated#1._Decide_remaining_questions

> I presume that the "deprecated" value of the status= attribute of
> att.docStatus should be left alone.

Right.  That's an unrelated @status.

> 7. tests
> -- -----
> I have not added any tests in P5/Test yet. Should we? Since the only
> important tests are based on the current date, it seemed a bit
> problematic, if not silly. I suppose we could test that
> validUntil=3015-05-16 doesn't fire and that validUntil=1015-05-16
> does. But we can't really test the equality test easily.

It's problematic because of what you described in section 1 of your 
email?  If so, and we don't find a way around this, then I think we'll 
need to just add a manual step to tcw22.  Both options are described in 
brief at

http://wiki.tei-c.org/index.php/Practices_no_longer_recommended_or_now_deprecated#3._Modify_release_building_procedure

--K.