-
Notifications
You must be signed in to change notification settings - Fork 31
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
Various changes for SDK 1.10 #695
Conversation
The rule BR-BT-00738-0053 already enforces that the preferred publication date must be after the dispatch date. Remove corresponding Schematron asserts.
The preferred publication date (BT-738) can now be equal to the dispatch date (BT-05). Also update corresponding schematron rules, and translations of rule message.
Allow multiple digits in SDK version number.
This notice is not about a framework contract.
This ensure the check for the presence of the field is fired even if cac:OpenTenderEvent is not present.
Add new tailored codelist "contract-term" and fix preset value of OPP-030-Tender-List.
This field was missing. Also add corresponding field for its attribute, and the schematron rules.
Update rules on when BT-105-Procedure is forbidden, and add checks on possible values based on the notice subtype. Those checks are implemented via tailored codelists. Update corresponding codelists, and schematron rules.
Also update corresponding schematron rules.
This includes all the newly added conditional forbidden/mandatory rules. Also update affected validation reports.
Under specific conditions, only CPV codes corresponding to works were allowed. Also allow CPV codes corresponding to services.
This reflects codes added and removed.
This reflects codelists added and removed.
Also add corresponding schematron rules.
Also update corresponding schematron rules, and affected validation reports.
Update affected validation reports.
This reflects the latest changes in the codelists themselves.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK with me
fields/fields.json
Outdated
} ] | ||
}, | ||
"mandatory" : { | ||
"value" : false, | ||
"severity" : "ERROR", | ||
"constraints" : [ { | ||
"noticeTypes" : [ "1", "2", "3", "4", "5", "6", "7", "8", "9", "10", "11", "12", "13", "14", "15", "16", "17", "18", "19", "20", "21", "22", "23", "24", "25", "26", "27", "28", "29", "30", "31", "32", "33", "34", "35", "36", "37", "CEI", "T01", "T02" ], | ||
"noticeTypes" : [ "1", "1", "2", "2", "3", "3", "4", "4", "5", "5", "6", "6", "7", "7", "8", "8", "9", "9", "10", "10", "11", "11", "12", "12", "13", "13", "14", "14", "15", "15", "16", "16", "17", "17", "18", "18", "19", "19", "20", "20", "21", "21", "22", "22", "23", "23", "24", "24", "25", "25", "26", "26", "27", "27", "28", "28", "29", "29", "30", "30", "31", "31", "32", "32", "33", "33", "34", "34", "35", "35", "36", "36", "37", "37", "38", "39", "40", "CEI", "CEI", "T01", "T01", "T02", "T02" ], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Notice subtypes listed twice
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, this is problem in the content of the DB, I've created a ticket for it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm merging this as-is, the diff and the number of changes in this PR are already too large.
The issue spotted here will be correct in a subsequent commit and PR.
See individual commits for details.