Skip to content

Commit

Permalink
docs/schema/reference.md: Quote descriptions from references
Browse files Browse the repository at this point in the history
  • Loading branch information
duncandewhurst committed Dec 23, 2024
1 parent a29b342 commit 18da662
Showing 1 changed file with 16 additions and 1 deletion.
17 changes: 16 additions & 1 deletion docs/schema/reference.md
Original file line number Diff line number Diff line change
Expand Up @@ -257,6 +257,11 @@ The [Bid statistics and details](https://extensions.open-contracting.org/en/exte

The award section is used to announce any awards issued for this tender. There can be multiple awards made. Releases can contain all, or a subset, of these awards. A related award block is required for every contract block, as the award contains information on the suppliers. In particular cases there can be multiple suppliers for a single award: for example, in the case of [consortia](../guidance/map/buyers_suppliers.md#consortia-suppliers) and in [framework agreements](../guidance/map/framework_agreements).

The `awards` array is defined as:

```{field-description} ../../build/current_lang/release-schema.json /properties/awards
```

An `Award` is defined as:

```{field-description} ../../build/current_lang/release-schema.json /definitions/Award
Expand Down Expand Up @@ -290,6 +295,11 @@ Each `Award` has the following fields:

The contract section is used to provide details of contracts that have been entered into. Every contract must have a related award, linked via the `awardID` field. This is because supplier information is contained within the 'award'.

The `contracts` array is defined as:

```{field-description} ../../build/current_lang/release-schema.json /properties/contracts
```

A `Contract` is defined as:

```{field-description} ../../build/current_lang/release-schema.json /definitions/Contract
Expand Down Expand Up @@ -323,7 +333,7 @@ Each `Contract` has the following fields:

Implementation information can be updated over the course of a contract. It belongs nested within the contract it relates to.

The `contracts/implementation` section is defined as:
The `contracts/implementation` object is defined as:

```{field-description} ../../build/current_lang/release-schema.json /definitions/Implementation
```
Expand Down Expand Up @@ -364,6 +374,11 @@ To represent planned payments, use [Milestones](#milestones) instead.

In most circumstances, the `payer` identifier will match that of the `buyer`, and the `payee` identifier will match that of the `supplier`.

The `contracts/implementation/transactions` array is defined as:

```{field-description} ../../build/current_lang/release-schema.json /definitions/Implementation/properties/transactions
```

A `Transaction` is defined as:

```{field-description} ../../build/current_lang/release-schema.json /definitions/Transaction
Expand Down

0 comments on commit 18da662

Please sign in to comment.