-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
address #1981 with SchXslt (aka mausatron) instead of skeleton #2509
base: dev
Are you sure you want to change the base?
Conversation
…I was an idiot and did not merge *before* I started on move to mausatron (aka schxslt).
…of it in members of att.declarable.
…of it in members of att.declarable.
…h required manually merging 4 files (P5/Test/detest.xml, P5/Test/expected-results/detest_odd_schematron.log, P5/Test/expected-results/detest_xml_relaxng.log, and P5/Test/expected-results/detest_xml_schematron.log) and updating the Makefile
I just merged the current dev branch into this branch, Guidelines still build (include |
There seems to be an error with (I believe) the NVDL part of the build (note that this is not causing the build to fail, but is producing error messages—you can see it in the Actions build as well as when run locally):
|
* Compare SVRL output of Schematron validation of ODD file. * Deleted redundant "testingSpan" section of XML file (which I think I accidentally introduced on a previous attempt to merge in dev). * Updated expected-results/ accordingly.
In addition to a timestamp, the SVRL files contain filepaths and auto-generated namespace prefixes, so they cannot be directly compared. Instead, extract only the svrl:text elements and compare ’em.
Full Council discussion on April 13 at VF2F: European subgroup was getting the same errors.
Decision: find someone to fix nvdl validation |
I was unsuccessful in finding out about oNVDL support at Balisage. Next step is to ask on XML Slack, or no repo, or direct to author(s). |
I will say more shortly, but the main point now is that this PR updates our build process to use @dmj’s
SchXslt
(which I call “mausatron”) rather than the original skeleton implementation. This has quite a few minor advantages, but mainly allows users (including us) toReviewers — the lastest merge from dev into this branch (issue1981bis) required that the various Test/expected_results/detest*log files be hand-merged. Thus it is appropriate to take a pretty careful look at these.