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

Release reference: Add subschema definitions #1700

Open
duncandewhurst opened this issue Jun 25, 2024 · 1 comment · May be fixed by #1711
Open

Release reference: Add subschema definitions #1700

duncandewhurst opened this issue Jun 25, 2024 · 1 comment · May be fixed by #1711
Assignees
Labels
Focus - Documentation Includes corrections, clarifications, new guidance, and UI/UX issues
Milestone

Comments

@duncandewhurst
Copy link
Contributor

OCDS 1.2 introduces revised definitions for subschemas like Award and Contract which contain important information not documented elsewhere (e.g. what types of framework agreement contract belong in the contracts array). As far as I can see, the subschema definitions only appear in the schema browser and not in the release reference. Since the text in the schema browser is not included in the search index and not all readers are expected to use the schema browser, I think the subschema definitions should also appear in the release reference (like in the development version of OC4IDS).

@jpmckinney jpmckinney added this to the 1.2.0 milestone Jun 25, 2024
@jpmckinney jpmckinney added the Focus - Documentation Includes corrections, clarifications, new guidance, and UI/UX issues label Jun 25, 2024
@jpmckinney
Copy link
Member

Yes, good idea!

@duncandewhurst duncandewhurst self-assigned this Jun 27, 2024
@duncandewhurst duncandewhurst linked a pull request Oct 24, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Focus - Documentation Includes corrections, clarifications, new guidance, and UI/UX issues
Projects
Status: In progress
Development

Successfully merging a pull request may close this issue.

2 participants