As discussed in November 2013 Council meeting ( http://www.tei-c.org/Activities/Council/Meetings/tcm56.xml#body.1_div.3_div.1_div.1_div.1 ), there are three tickets involving deprecation that can't be solved with the current mechanisms:
We need a way to deprecate members of a content model. As agreed in Oxford, these three tickets should be solved using a Schematron warning. We also need to add @validUntil on constraintSpec.
Council discussion 2014-07-01: All of these can be handled with Schematron. Make green and assign all those tickets to someone who can do the Schematron (MDH volunteers).
See also FR #459