naming odd4odds when it's in Exemplars/
In Prague we agreed that odd4odds should be put into Exemplars/ and thus the oXygen framework, and that I should have that ready by the conference (on which I'm giving a talk on it). IIRC we decided to call it "tei_customization.odd" (and thus .rng, .rnc, etc.). I was recently reminding Martin of this schema and the differences between it and tei_odds, and he wondered aloud if we shouldn't think of tei_customization as a schema to use when creating a TEI customization that is a profile of, or subset of, or constraint of the TEI. (I.e., the set of documents that conform to the customized TEI is a proper subset of the set of documents that conform to tei_all.) And that we think of tei_odds as a schema to use when creating a TEI customization that is an extension of the TEI. That might mean renaming them to tei_customization_extension and tei_subset_customization or some such. Thoughts? (Remember that the present problem we are worrying about is how to explain to the oXygen user the difference between the two. If I understand correctly, we only get to present the user with the name of the thing, no pop-up or mouse-over gloss available. However, we do get to put comments in the template. :-)
I'm just watching Lou's video of his presentation for TEI 2017 (he's presenting by video) and he makes exactly the same distinction between a subset and an extension. I think it's a really important distinction to make, and I like that terminology. Almost all extensions are also subsets, of course. Cheers, Martin On 2017-11-05 02:49 PM, Syd Bauman wrote:
In Prague we agreed that odd4odds should be put into Exemplars/ and thus the oXygen framework, and that I should have that ready by the conference (on which I'm giving a talk on it).
IIRC we decided to call it "tei_customization.odd" (and thus .rng, .rnc, etc.).
I was recently reminding Martin of this schema and the differences between it and tei_odds, and he wondered aloud if we shouldn't think of tei_customization as a schema to use when creating a TEI customization that is a profile of, or subset of, or constraint of the TEI. (I.e., the set of documents that conform to the customized TEI is a proper subset of the set of documents that conform to tei_all.) And that we think of tei_odds as a schema to use when creating a TEI customization that is an extension of the TEI.
That might mean renaming them to tei_customization_extension and tei_subset_customization or some such. Thoughts? (Remember that the present problem we are worrying about is how to explain to the oXygen user the difference between the two. If I understand correctly, we only get to present the user with the name of the thing, no pop-up or mouse-over gloss available. However, we do get to put comments in the template. :-)
participants (2)
-
Martin Holmes
-
Syd Bauman