From 2f239e40d94c52b9a1880073e76273cb6261cf20 Mon Sep 17 00:00:00 2001 From: Duncan Dewhurst Date: Tue, 3 Oct 2023 11:30:21 +1300 Subject: [PATCH] docs/schema/records_reference.md: Add jsonschema directive for Record --- docs/schema/records_reference.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/schema/records_reference.md b/docs/schema/records_reference.md index b3171895f..d5d2f08cf 100644 --- a/docs/schema/records_reference.md +++ b/docs/schema/records_reference.md @@ -38,7 +38,7 @@ The following example demonstrates the package metadata and record fields. :title: package ``` -## Record structure +## Record A record **must** contain an [ocid](identifiers.md#open-contracting-process-identifier-ocid) and one or more of: @@ -47,6 +47,11 @@ A record **must** contain an [ocid](identifiers.md#open-contracting-process-iden A record **may** contain a [versionedRelease](#versioned-release) object, which aggregates, into a single object, all values of all fields from all releases up to the time of the record's publication. The versioned release is designed to make it easy to see how values change from one release to another, and will often be generated by data users, rather than by publishers. +```{jsonschema} ../../build/current_lang/record-package-schema.json +:pointer: /definitions/Record +:nocrossref: +``` + ### Releases Each release in a record can be provided as either a linked release or an embedded release.