[tei-council] VOTE ON DEPRECATION WORDING (was "Re: Next TEI-C Guidelines Release (presumably 2.6.0)")

[Peter Stadler]

C - B - A
(you forced me to vote)
Well, first I like transparency and second I think D is just misleading. People will still find http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-relationGrp.html after 2014-06-17 as long as there is no new release. So, on 2014-06-18 we have a webpage saying "I was removed yesterday“, or am I missing something? 
Additionally, I’d add „subsequent“ (or the like) to "available in any *subsequent* P5 releases after that date“ to make it even more explicit.

Best 
Peter

Am 08.01.2014 um 14:28 schrieb James Cummings <James.Cummings at it.ox.ac.uk>:

> 
> I'd agree that the simplicity is good. As long as the Council 
> understands that what we really mean is "removed from the TEI 
> source code before the release which follows this date". Then I 
> think having the definitive statement is better than being 
> perfectly transparent.
> 
> On 08/01/14 13:08, Hugh Cayless wrote:
>> I like the simplicity of D (even though it’s not technically true; C is more accurate but I agree with Fabio, too wordy). Being definitive will help concentrate people’s attention, so:
>> 
>> D, B, C, A
>> 
>> Hugh
>> 
>> /**
>>  *  Hugh A. Cayless, Ph.D
>>  *  hugh.cayless at duke.edu
>>  *  Duke Collaboratory for Classics Computing (DC3)
>>  *  http://blogs.library.duke.edu/dcthree/
>> **/
>> 
>> 
>> On Jan 7, 2014, at 23:03 , Syd Bauman <s.bauman at neu.edu> wrote:
>> 
>>>>> [xslt] WARNING: use of deprecated attribute ― The TEI-C may drop
>>>>> support for @type of the biblScope element as early as 2014-12-17.
>>> 
>>> SR> Which reminds me that I (still) don't like the vague wording of this.
>>> 
>>> OK folks, time to stand up and be counted. We've had 4 alternate
>>> suggestions for the wording of the "you used a deprecated doohicky"
>>> message. Please vote for one, or put them in your preference order, or
>>> (ack!) suggest another wording ASAP.
>>> 
>>> a. The TEI-C may drop support for relationGrp element as early as
>>>   2014-06-17
>>> 
>>> b. The TEI-C will drop support for the relationGrp element after
>>>   2014-06-17
>>> 
>>> c. The relationGrp element will be removed from TEI source code on
>>>   2014-06-17, and will not be available in any P5 releases after
>>>   that date.
>>> 
>>> d. The relationGrp element will be removed from the TEI on 2014-06-17
>>> 
>>> 
>>> Note: the value of validUntil= does not have to be a complete date. If
>>> it is precise only to the month, we'd replace "on DATE" with "in
>>> DATE". Perhaps even convert 2014-06 to "June 2014".
>>> --
>>> tei-council mailing list
>>> tei-council at lists.village.Virginia.EDU
>>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>> 
>>> PLEASE NOTE: postings to this list are publicly archived
>> 
> 
> 
> -- 
> Dr James Cummings, James.Cummings at it.ox.ac.uk
> Academic IT Services, University of Oxford
> -- 
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
> 
> PLEASE NOTE: postings to this list are publicly archived

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.village.Virginia.EDU/pipermail/tei-council/attachments/20140109/4fd35ee8/attachment.bin