[0.9.3] - 2021-10-07¶
update the 'Mapping from OCDS' column to reflect the logic used in convert-to-oc4ids.
remove references to the PPP profile, reference individual extensions instead.
update project identification mapping for sector.
replace reference to Budget and projects extension with Projects extension.
remove reference to 'publicAuthority' code from OCDS mapping.
#216 - update CoST IDS & OCDS mapping documentation to separate the OC4IDS to CoST IDS mapping and the OCDS to OC4IDS mapping.
#217 - remove repeated 'OCDS:' in mapping documentation.
#220 - add reactive disclosure elements to CoST IDS & OCDS mapping documentation.
#246 - correct link and wording to Project extension in project identifiers guidance.
#278 - add reactive disclosures to worked example.
#304 - update blank OC4IDS file with schema changes, and add project package.
#316 - update wording around worked example file, add link to blank.json.
#260 - improve the clarity of the Getting Started documentation.
#329 - fix incorrect references to
document.typein the CoST IDS & OCDS mapping.
#339 - update link to CoST IDS on mapping page.
#277 - add
metrics, which can be used to publish implementation progress reports.
#317 - update fields shared with OCDS for PPPs 1.0.0-beta3 and OCDS 1.1.5.
#264 - add a field and class for natural persons.
#273 - add
contractingProcesses/summary/transactions, which can be used to publish disbursement records.
#284 - restore
#223 - add stricter validation rules to catch empty arrays, objects and strings.
#317 - update codes shared with OCDS for PPPs 1.0.0-beta3 and OCDS 1.1.5.
#261 Update description of 'feasibilityStudy' code to include "project".
#267 Update description of 'completionCertificate' code to include "project".
[0.9.2] - 2020-06-29¶
#96 - add guidance on providing project identifiers in OCDS data.
#120 - add list of registered project identifier prefixes to documentation.
#124 - clarify guidance on project identifier prefixes.
#131 - replace 'owner' with 'publicAuthority' in mapping.
#133 - improve clarity of 'what is a project' in getting started section.
#136 - add project identifier prefix to example file.
#143 - update worked example page to describe project package, use non-normative keywords, and edit for clarity.
#143 - add data user guide page.
#145 - re-order codelist reference page, refer to OCDS and extension documentation for codelists that are shared.
#146 - add 'publicAuthority' role to example file.
#218 - add link to CoST guidance note on OGP commitments.
#211 - update description of 'publicAuthority' role.
Project package schema¶
OC4IDS project schema¶
#127 - remove the requirement that linked OCDS releases must be provided in release packages containing only one release. Remove recommendation that OCDS releases are cached from schema and add guidance on caching releases from unreliable sources to implementation guidance.
#132 - add a publicAuthority organization reference field.
#140 - update the description of
project/periodto clarify that this field should be used to provide the planned start and end dates during the preparation phase, for comparison with the actual completion date for the project.
#141 - clarify that
contractingProcesses/summary/descriptionis for the contract's initial scope of work.
#141 - remove incorrect guidance about other fields from
#153 - add project/relatedProjects array.
#154 - add
project/budgetto record the date of the budget request for the project.
#156 - fix the description of
completion/endDateDetailsto refer to the end date of the project, not that of the contract.
#157 - fix spelling and grammar issues.
#158 - make
contractingProcesses/releases/tagan array, not a string (bugfix).
#160 - describe the components of
project/id, and link to guidance.
#161 - removed
contractingProcesses/summary/ocidbecause it duplicates
#182 - update validation properties to enforce unique items in arrays and minimum length on required string fields.
[0.9.1] - 2019-06-17¶
Update ocds-babel to 0.1.0.
Correct schema URLs in schema files.
[0.9.0-beta] - 2019-03-19¶
This changelog entry indicates notable changes since the alpha-2 development release of OC4IDS, it is not intended to be a complete list of changes.
In addition to the specific changes to schema and codelists noted below:
Various refinements and clarifications were made to schema and codelist descriptions.
Guidance on mapping values from OCDS was moved from the schema to the IDS and OCDS mapping section of the documentation.
Documentation was expanded and restructured.
sector- use projectSector open codelist.
ContractingProcess- add required
variations- rename to
Location- add required
projectSectorcodelist - add codelist for project sector.
projectStatus codelist - replace 'construction' with 'implementation'.
variationType codelist - rename to modificationType.
partyRole codelist - add OC4IDS codes mentioned in schema and mapping:
partyRole codelist - add codes from OCDS partyRole codelist:
partyRole codelist - remove PPP-specific codes:
documentType codelist - remove PPP-specific codes:
documentType codelist - add codes from OCDS documentType codelist: