-
Notifications
You must be signed in to change notification settings - Fork 46
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
Strengthen some normative statements in schema (wrong branch) #1069
Closed
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
OCDS 1.1.4 - Bug Fix Release
Merge #875 from 1.1-dev onto 1.1
Merge 1.1-dev into 1.1
Signed-off-by: Yohanna Lisnichuk <[email protected]>
Signed-off-by: Yohanna Lisnichuk <[email protected]>
…xample-personal-identifiers Signed-off-by: Yohanna Lisnichuk <[email protected]>
…xample-personal-identifiers Signed-off-by: Yohanna Lisnichuk <[email protected]>
Signed-off-by: Yohanna Lisnichuk <[email protected]>
Merge 1.1-dev into 1.1
Merge 1.1-dev into 1.1
@ColinMaudry If you create the branch from this repo (rather than your fork) the tests should pass. A few other notes:
|
Clarify role of publisher and definition of publisher name
add localization docs
…fiers Add personal identifiers example
Closes #789 Signed-off-by: Yohanna Lisnichuk <[email protected]>
Use standard.open-contracting.org instead of staging.standard.open-contracting.org
Merge 1.1-dev into 1.2-dev
…anization identifier
…ing/standard into 1060-parties/id-uniqueness
…89-string-identifiers-preference
Signed-off-by: Yohanna Lisnichuk <[email protected]>
Co-authored-by: James McKinney <[email protected]>
Co-authored-by: James McKinney <[email protected]>
Co-authored-by: James McKinney <[email protected]>
…ness 1060 parties/id uniqueness
…-preference String identifiers preference
ColinMaudry
changed the title
Strengthen some normative statements in schema #868
Strengthen some normative statements in schema (wrong branch)
Nov 11, 2020
Replaced this PR with #1112 |
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.
Closes #868
I went for "should", as I don't believe repeating the items in the contract is harmful, just potentially confusing.