Change Log¶
OpenCodeList specification¶
0.4.0 _ August 31, 2026¶
Added:
-
Better support for localized text:
- Names and descriptions of columns, keys, and foreign keys, as well as descriptions of enumeration values, can now be specified not only as simple JSON strings but also as language-dependent values using BCP 47 language tags.
- Values of columns of type
stringcan also be specified as localized values using BCP 47 language tags.
-
For
identification.language, the semantics of a default language for the document content have been defined. Columns of typestring,enum, andenum-setcan override this default using theirlanguageproperty.
Changed:
- Breaking Change: For columns of type
document, theschemaproperty has been replaced byschemaUri. Embedded JSON Schemas as column definitions are no longer supported. - Breaking Change: Values of the
timecolumn type now explicitly represent a local time of day without a date or UTC offset, using the formatHH:mm:sswith optional fractional seconds of up to seven digits. - Breaking Change: Columns that are part of a key MUST have
optional: falseandnullable: false. The combination of key values MUST be unique within the dataset. - The rules for foreign keys have been clarified. The number and data types of the local foreign-key columns MUST match the columns of the referenced key; columns are matched by their order.
- The rules for data rows have been clarified. Non-optional columns MUST be present, optional columns MAY be omitted, and values MUST conform to the respective column type and its constraints.
- The
annotationobject has been clarified to explicitly allowdescriptionsandappInfoto be specified together. - The permitted extension points for custom
x-properties have been clarified to includeidentificationandpublisher.
Removed:
- The
referenceSetproperty of acodeListSetobject is no longer required. This allows a code list collection to be published as a pure CodeListSet metadata document without references.
In addition, numerous minor (and major) issues on the website have been fixed.
0.3.0 _ February 19, 2025¶
Changed:
- Breaking change: The
canonicalVersionUriproperty was marked as required for theidentificationsub-schema. - Breaking change: For the sub-schemas
documentRefandkeyRef, the required propertycanonicalVersionUrihas been changed tocanonicalUri.
0.2.0 _ January 25, 2025¶
- First publication