-
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 updates in generated files #846
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also update corresponding Schematron rules.
Fields BT-503-Organization-Company and BT-506-Organization-Company are now optional except for buyers. Update corresponding Schematron rules.
The fields are not mandatory anymore for organisations that are not a buyer. Update corresponding validation reports to remove fired rules.
Also update corresponding Schematron rules.
Also remove corresponding schematron rules.
Only check that "Future Notice" (BT-127-notice) is later than the notice dispatch date if the notice is not a change notice. Also update corresponding Schematron rules.
Do not check that "Deadline Receipt Expressions" (BT-630(d)-Lot) is later than the notice dispatch date if the notice is a change notice. Also update corresponding Schematron rules.
Remove presence constraints for fields BT-118-NoticeResult and BT-709-LotResult in notice subtypes 38 and 39, as they cannot be fulfilled. Also update corresponding schematron rules
Also update corresponding schematron rules.
Also update some labels for existing codes.
Also update labels for existing codes, and affected tailored codelists.
This does not change the structure, it just puts the "_captionFieldId" property next to relevant siblings.
This reflects that they are synchronised with the corresponding publication on EU Vocabularies.
bertrand-lorentz
requested review from
rousso,
pdonohoe,
YvesJo,
ferrakaop and
rouschr
February 27, 2024 13:21
YvesJo
approved these changes
Feb 27, 2024
ferrakaop
approved these changes
Feb 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Possibly the last significant changes before the first release candidate for 1.11.0.
See the individual commits.