[tei-council] respond by 1 May: summary of and path forward for "no longer recommended" and "deprecated" practices

Sebastian Rahtz sebastian.rahtz at it.ox.ac.uk
Thu Jun 20 04:26:49 EDT 2013


On 20 Jun 2013, at 05:40, Kevin Hawkins <kevin.s.hawkins at ultraslavonic.info> wrote:
> While implementing those past deprecations according to our policy, I 
> set some @validUntil dates that are in the past.  These yielded 
> Schematron errors that cause Jenkins to fail, so it appears Sebastian 
> implemented something he suggested back in April.
> 

not me, that's Syd's work :-}

> If everyone is satisfied with the way this is working and feels that 
> we've given enough notice for deprecation on these (despite not having 
> Schematron warnings as part of our releases for the past two years) I 
> suggest we actually go ahead and remove these deprecated things.


given that the deadline for changes is today, I'd be inclined to not risk it.
unlike me to be cautious, I know….
--
Sebastian Rahtz      
Director (Research) of Academic IT
University of Oxford IT Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431



More information about the tei-council mailing list