[tei-council] new validUntil=

[Kevin Hawkins]

On 5/16/13 4:51 PM, Kevin Hawkins wrote:
> 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

And I have now deprecated the entire @status attribute (by using 
@validUntil, per TCW27) while cleaning up past "deprecations" to follow 
the policy in TCW27.  (For more on that, see: 
http://wiki.tei-c.org/index.php/Practices_no_longer_recommended_or_now_deprecated#5._Recent_.22deprecations.22_to_be_reviewed 
.)

--Kevin