Project news

Code List Representation (genericode) v1.0 approved as a Committee Specification

Genericode is ready for testing and implementation

OASIS is pleased to announce the approval and publication of an updated Committee Specification by the members of the OASIS Code List Representation TC [1]:

Code List Representation (genericode) Version 1.0
Committee Specification 02
06 April 2022


Code lists can be defined as controlled vocabularies or coded value enumerations. Examples of standardized code lists include country abbreviations, currency abbreviations, shipping container descriptors, and airport codes. Examples of non-standardized code lists used between trading partners include financial account types, workflow status indicators, and any set of values representing the semantics of related concepts known between the parties involved in information interchange. Code lists have been used for many years, and they have often been published and disseminated in manners that have not been IT-enabled for ease of computer processing.

The Code List Representation format, known as genericode, is a single semantic model of code lists and accompanying XML serialization (supported by a W3C XML Schema) that can encode a broad range of code list information. The serialization is designed to IT-enable the interchange or distribution of machine-readable code list information between systems. Note that genericode is not designed as a run-time format for accessing code list information, and is not optimized for such usage. Rather, it is designed as an interchange format that can be transformed into formats suitable for run-time usage, or loaded into systems that perform run-time processing using code list information.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The documents and related files are available here:

Editable source (Authoritative):
PDF marked with changes since previous public review:

JSON examples:
Schematron constraints:
XML examples:
XML constraints:
JSON translation in XSLT:

For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files. You can download the ZIP file at:

Members of the OASIS Code List Representation TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

This Committee Specification 02 incorporates changes since the previous public review [4].

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

Additional references

[1] OASIS Code List Representation TC

[2] Details of public review:

[3] Approval ballot:

[4] Committee Specification Draft 04, 16 October 2021
– Change description: