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

[Kevin Hawkins]

To answer Gabby's question, when a practice is "no longer recommended" 
or "deprecated", these are two different things.  However, in the 
future, if we decide we don't like a certain practice, we're going to 
need to decide whether to make something "no longer recommended" or to 
deprecate it, so it makes sense to have them documented together.

I have removed mention of the P6-dev wiki page from the draft policy on 
"no longer recommended" and deprecated practices.  I agree with the 
objections that various people have raised and was only trying to 
capture our discussion in Providence.  (The discussion, as I recall it, 
went like this: in summarizing the "no longer recommended" option during 
our discussion in Providence, I said we should list the practice on 
P6-dev, but someone objected, perhaps because they thought that anything 
on P6-dev would definitely be implemented in P6.)  However, James just 
pointed out that presence on P6-dev makes no such guarantee.

K.