-
Notifications
You must be signed in to change notification settings - Fork 1
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
GEMINI 2.3 fixes #5
Comments
Comment by archaeogeek Any chance of a diff between this and the previous version? |
Comment by nmtoken Added a diff between the files, I uploaded a new file rather than change the existing one for two reasons, first is that the original file has a version number attached, and second related to that is that we may want a candidate release for all new proposed changes. These changes should be for consideration/testing at the moment, not latest GEMINI. |
Comment by PeterParslow I challenge the test that triggers MI-18a (line 33 in the diff) test="($hierarchyLevelCLValue = 'dataset' or $hierarchyLevelCLValue = 'series') and ($srES > 0 and $srES > 0) surely one of the two $srES should be $srD? And you would then want to fix the report that it gives (line 35 in the diff) |
Comment by nmtoken This is now out of date. |
Issue by nmtoken
Mon Nov 2 17:27:37 2020
Originally opened as AGIuk/Schematron#4
Proposed changes to GEMINI 2.3.n schematron
nmtoken included the following code: https://github.com/AGIuk/Schematron/pull/4/commits
The text was updated successfully, but these errors were encountered: