Skip to content
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
wants to merge 76 commits into from
Closed

Strengthen some normative statements in schema (wrong branch) #1069

wants to merge 76 commits into from

Conversation

ColinMaudry
Copy link
Member

Closes #868

The goods, services, and any intangible outcomes in this contract. Note: If the items are the same as the award do not repeat.

Change second clause to either SHOULD or MUST statement.

I went for "should", as I don't believe repeating the items in the contract is harmful, just potentially confusing.

jpmckinney and others added 23 commits May 29, 2019 19:47
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]>
@jpmckinney jpmckinney changed the base branch from 1.1-dev to 1.2-dev September 16, 2020 20:06
@jpmckinney
Copy link
Member

jpmckinney commented Sep 16, 2020

@ColinMaudry If you create the branch from this repo (rather than your fork) the tests should pass. A few other notes:

  • Please change the base branch to 1.2-dev for all new PRs (I've edited your existing PRs).
  • Add an entry to changelog.md (I forgot to do this for Clarify role of publisher and definition of publisher name #1067)
  • Set the PRs milestone to 1.2.0
  • If you edit the release schema, you'll need to run python utils/make_dereferenced_release_schema.py
  • If you add a field to the release schema, you'll need to run python utils/make_versioned_release_schema.py

yolile and others added 24 commits October 12, 2020 10:47
Use standard.open-contracting.org instead of staging.standard.open-contracting.org
…ing/standard into 1060-parties/id-uniqueness
Signed-off-by: Yohanna Lisnichuk <[email protected]>
Co-authored-by: James McKinney <[email protected]>
Co-authored-by: James McKinney <[email protected]>
…-preference

String identifiers preference
@ColinMaudry ColinMaudry changed the title Strengthen some normative statements in schema #868 Strengthen some normative statements in schema (wrong branch) Nov 11, 2020
@ColinMaudry
Copy link
Member Author

Replaced this PR with #1112

@jpmckinney jpmckinney closed this Nov 11, 2020
@ColinMaudry ColinMaudry deleted the normative868 branch November 11, 2020 15:37
@jpmckinney jpmckinney removed this from the 1.2.0 milestone Jul 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Strengthen some normative statements in schema
5 participants