On 27/03/17 14:02, Syd Bauman wrote:
> You *can* use @when together with (say) @notAfter if you don't
>> invoke schematron validation.
> "Cannot" does not mean that it is impossible for you to type that
> combination on your keyboard. Surely "cannot" means it is impossible
> for you to use that combination and remain TEI conformant, no?

Well, this is begging the question. Yes if you consider validity against
schematron constraints to be a necessary
part of TEI conformance. No if it isn't.

[snip]

> TEI conformance is not a general-purpose
> concept, but rather a concept that is expressed in relation to a
> particular version.

Yes, this is a good point, and the definition of the conformance
certainly needs to be more explicit about that,

> So here is a fictitious scenario.

This is all well and good. But am I wrong in thinking that occasionally
schematron constraints are introduced which do not cause any component
to be "deprecated" in the sense that they gain a @validUntil attribute
which sets in train the scenario you describe? Constraints which just
say "up till now the Guidelines may have permitted this because the
schema wasn't expressive enough, but it's always been wrong and now
we're going to check for it."