I don't think any magic would happen based on the documentation of it using prefixDef in the header... we just have a way to document that particular form of magic now. (The magic though, I suppose, is that the processing does anything with it at all.)
You know I dislike magic in that sense and want everything to be open and transparently honest in its processing. 😉
Excellent introduction. In the last example for supersetting chained ODDs you use the
magic to point to TEI version 3.0.0 p5subset.xml. While I know this works, and indeed it is of course possible that you've documented this in your TEI ODD customization file using a prefixDef in the header, wouldn't it be better in a how-to such as this to use the explicit URL of:
to point to the earlier version? It is important, in my opinion, for people know that all previous versions of TEI P5 releases are archived in the vault not only for them to use in chaining ODDs but also to compare different versions of the TEI Guidelines over time. Only a trivial note, otherwise looks good to me.
From: TEI (Text Encoding Initiative) public discussion list <[log in to unmask]> on behalf of Lou Burnard <[log in to unmask]>
Sent: 29 December 2017 20:49:30
To: [log in to unmask]
Subject: Chaining ODD tutorial updated
I've been amusing myself this penultimate day of 2017 by adding a worked example to my little tutorial on how to chain ODDs.
If it amuses you too, please take a peek at https://teic.github.io/TCW/howtoChain.html ... all comments welcomed!