redo the ODD as a chained add-on? #4
Description
There is something conceptually odd about the current ODD (and I know who to blame). The MAF-1 additions should be a single add-on that someone can either incorporate into their ODD, or chain. As it is, it e.g. restricts the text structure, for no good reason.
The reason is that it came from an example suite that was at first meant to be a document demonstrating that there is a way to validate all of the MAF examples that have been converted into the TEI. But now, the aim has changed. The original examples document should be an example of how to "attach" MAF to anyone's TEI.
I think (and some of my memories are very vague) that I just wanted the TEI Bare ODD to work with MAF additions, and hence the restrictions, attribute deletions, etc. And there's completely nothing wrong with attaching MAF to TEI Bare, because the result is then as transparent as can possibly be, and users can diagnose their TEI against Bare to identify and remove any potential problems. But it should also be a live demonstration of how to employ MAF for (nearly) any TEI. Especially in the standOff form, no problems should arise concerning the re-use of vanilla TEI attributes, etc. (unless of course someone produces a resource-wide set of Schematron constraints for vanilla TEI attributes - - but then, it's clear how to fix that).