Replies: 5 comments
-
|
Beta Was this translation helpful? Give feedback.
-
@ahankinson @kepper Do you have any idea about utils/schematron? Is this needed in the repo at all? |
Beta Was this translation helpful? Give feedback.
-
Previously, there was an attempt at a) building a test set for MEI and b) validating both the schema and the schematron rules for every commit. I still think there is a need for this, but most of the other stuff has been stripped out. So I guess it can be scrapped? |
Beta Was this translation helpful? Give feedback.
-
The stuff in that folder is rather old, yes. More recent work in that area (though slightly different) can be found in this file, discussed in this issue. Before scrapping it, I'd like to check if things can be moved there. Not much time for the next ten days, though… |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
I stubbed over some files in the repo I was not aware of or do not know what their purpose is. Moreover I think some files should be moved for a cleaner repo structure. The idea of this discussion is to get things clear about those things before issuing a pull request.
source/css/.qicon
don't know why this is there or if it is needed I suppose it's there by acident?source/unusedImages.txt
andsource/usedImages.txt
if I gather correctly these are some remnants of the transformation process from markdown guidelines back to TEI-based guidelines. Are theses files still of use or needed?source/tei_odds.rng
is the schema file referenced from the customizations files. (Sidenote: maybe it would be wise to at some point make a transgression to the latest canon TEI version) as it not really part of the codebase actually we should get rid of it; if we want to keep it for convenience purposes, I think it should be moved tosource/validation
source/validation/mei_odds.odd
andsource/validation/mei_odds.rng
is this really part of our codebase? I don't really think so; shouldn't we move it to a separate repo?.keep
files in tests. Can anyone explain their purpose?utils/schematron
as this is definitely third party code, maybe we could integrate it as submodule? Apart from that: where and when is it needed?Whether you can answer my questions, have some similar of your own, or just want to give your five cents, please reply and contribute ;-)
Beta Was this translation helpful? Give feedback.
All reactions