I don't understand Sebastian's question, but I wonder whether he thinks that he can write a stylesheet that will produce Schematron warnings for us for any ODD construct that contains a @validUntil, saving us the work of creating these manually. If so, that's intriguing.
we will need to add Schematron rules here as well.
I suggest we don't bother adding Schematron warnings for the following deprecations since they've already happened more than two years ago and therefore will come up as invalid in future builds and be removed entirely:
use of @targets
Last edit: Kevin Hawkins 2013-12-11
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Per discussion on tei-council on 2013-06-21, we should warn about not only constructs for which the value of @validUntil is in the past but also those that are, say, less than 30 days in the future. That way we won't have a deprecation sneak up on us in the final days of making a release.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We have (some time ago) implemented a system that, at P5 build time, reads the @validUntil attributes and generates Schematron code that warns when instances use those constructs.
So closed-implemented.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
this would be an addition to stylesheets to generate a Schematron which produces a warning, I assume?
I don't understand Sebastian's question, but I wonder whether he thinks that he can write a stylesheet that will produce Schematron warnings for us for any ODD construct that contains a @validUntil, saving us the work of creating these manually. If so, that's intriguing.
Anyway, now that I've done http://sourceforge.net/p/tei/code/12284/ , here's a list of things in need of Schematron warnings:
<relationGrp><quotation><biblScope>Once I figure out how to do proper deprecations according to http://www.tei-c.org/Activities/Council/Working/tcw27.xml for the following:
we will need to add Schematron rules here as well.
I suggest we don't bother adding Schematron warnings for the following deprecations since they've already happened more than two years ago and therefore will come up as invalid in future builds and be removed entirely:
Last edit: Kevin Hawkins 2013-12-11
Per discussion on tei-council on 2013-06-21, we should warn about not only constructs for which the value of @validUntil is in the past but also those that are, say, less than 30 days in the future. That way we won't have a deprecation sneak up on us in the final days of making a release.
this is waiting on implementation of the generation of Schematron (Council meeting 11/13)
Ignore my comment above: it relates to the Guidelines build process, not what we provide to users.
Last edit: Kevin Hawkins 2013-12-08
See https://sourceforge.net/p/tei/feature-requests/486/ for the generation of Schematron that we are waiting on.
We have (some time ago) implemented a system that, at P5 build time, reads the @validUntil attributes and generates Schematron code that warns when instances use those constructs.
So closed-implemented.