Hi,
as for test files, I guess we should test roughly three classes of things
1. as you pointed out, that sample ODDs including <model> elements do
validate against TEI schemas
2. sample TEI Simple files can be converted into output using processing
model and this output is as expected (test files for this are in
https://github.com/TEIC/TEI-Simple/tree/master/tests, let me clear them up
a bit and provide you with magic commands for executing the tests)
3. tests that sample ODDs get converted into expected XSLTs/XQueries by
processing model
2 is already in place, or almost, 1 most probably straightforward for Lou
or James and I guess even I could do it if I had an afternoon to kill. We
have nothing for 3 as yet, though what we could easily do is take the ODD
we have and results of application of current processing model
implementations as our expected output.
To satiate your curiosity: "poligon" in Polish means military training
area, where you can shoot and run soldiers around without causing
collateral damage. The closest English word (in looks, not meaning, though
I believe the roots of the Polish and English words are indeed the same) is
polygon, so that's how it got to be named like that. Sorry if it tells too
much about my mental processes.
I am trying to keep afloat and not to sink under pressing work obligations,
but if I took to it early next week would that be acceptable for you?
Magdalena
On 28 January 2016 at 10:22, Lou Burnard
The next step in getting procmod into the Guidelines ought to be to produce some test files. However, as James mentioned earlier, this is not entirely straightforward.
I can dream up sample ODDs which include <model> elements no problem, and can then validate them against the schemas generated from the current source. I can also re-use the ones in the Polygon directory in the original tei-simple repo, written by Magdalena. (why is it called "Polygon" btw?)
However, should we not also be producing a test implementation or two showing the actual output generated with the aid of those models? That would require adding, presumably into the Stylesheets tree, some version of Magda's pilot version of a stylesheet for transforming <model>s into XSL. Or is that already there somewhere?
Or are we just planning to keep quiet about the whole thing?
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived