Skip to content

Commit

Permalink
Merge pull request #1701 from open-contracting/1698-1699-framework-di…
Browse files Browse the repository at this point in the history
…agram

docs/guidance/map/framework_agreements.md: Update diagram
  • Loading branch information
jpmckinney authored Jul 3, 2024
2 parents e7bd89d + e5a5c8e commit 1b59759
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 3 deletions.
Binary file removed docs/_static/png/framework_agreement/model.png
Binary file not shown.
1 change: 1 addition & 0 deletions docs/_static/svg/framework_agreement_diagram.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
4 changes: 2 additions & 2 deletions docs/guidance/map/framework_agreements.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,9 +70,9 @@ OCDS models the first and second stages of framework agreement procedures as sep
The 'framework' code is only used to relate second-stage contracting processes to their first-stage contracting process, never to other second-stage contracting processes.
```

The following diagram shows how OCDS models a framework agreement procedure with two second stages: one with competition and one without competition. Grey blocks represent unused sections of the OCDS schema.
The following diagram shows how OCDS models a framework agreement procedure with two second stages: one with competition and one without competition.

![OCDS framework agreement model](../../_static/png/framework_agreement/model.png)
![OCDS framework agreement model](../../_static/svg/framework_agreement_diagram.svg)

### Extensions

Expand Down
2 changes: 1 addition & 1 deletion docs/history/changelog.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ Per the [normative and non-normative content and changes policy](../governance/n
* Pre-qualification and pre-selection [#999](https://github.com/open-contracting/standard/pull/999) [#1345](https://github.com/open-contracting/standard/pull/1345)
* Unsuccessful processes [#1007](https://github.com/open-contracting/standard/pull/1007)
* Milestones [#1048](https://github.com/open-contracting/standard/pull/1048)
* Framework agreements [#1123](https://github.com/open-contracting/standard/pull/1123) [#1269](https://github.com/open-contracting/standard/pull/1269) [#1332](https://github.com/open-contracting/standard/pull/1332) [#1461](https://github.com/open-contracting/standard/pull/1461) [#1549](https://github.com/open-contracting/standard/pull/1549) [#1671](https://github.com/open-contracting/standard/pull/1671)
* Framework agreements [#1123](https://github.com/open-contracting/standard/pull/1123) [#1269](https://github.com/open-contracting/standard/pull/1269) [#1332](https://github.com/open-contracting/standard/pull/1332) [#1461](https://github.com/open-contracting/standard/pull/1461) [#1549](https://github.com/open-contracting/standard/pull/1549) [#1671](https://github.com/open-contracting/standard/pull/1671) [#1701](https://github.com/open-contracting/standard/pull/1701)
* Electronic catalogs [#1223](https://github.com/open-contracting/standard/pull/1223)
* Beneficial ownership information [#1305](https://github.com/open-contracting/standard/pull/1305)
* [#1414](https://github.com/open-contracting/standard/pull/1414) Rephrase planning stage to planning process in worked examples.
Expand Down

0 comments on commit 1b59759

Please sign in to comment.