OASIS Open

Code List Representation V1.0 has been presented to the membership by the Code List TC [1] as a candidate for OASIS Standard. Do you consent or object to its approval as an OASIS Standard?

Code lists have been with us since long before computers. They should be well understood and easily dealt with by now. Unfortunately, they are not. As is often the case, if you take a fundamentally simple concept, you find everybody has their own unique view of what the problem is and how it should be solved.

The OASIS Code List Representation format, genericode, is a single semantic model of code lists and accompanying XML serialization 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.

The TC received 3 Statements of Use from the Universal Business Language (UBL) Technical Committee, the LegalXML Electronic Court Filing Technical Committee, and the NIEM Technical Architecture Committee (NTAC). [2].


This is a call to the Organizational Members of OASIS to consent or object to this approval. You are welcome to register your consent explicitly on the ballot; however your consent is assumed unless you register an objection [3]. To register an objection, you must:

1. Indicate your objection on this ballot, and

2. Provide a reason for your objection and/or a proposed remedy to the TC.

You may provide the reason in the comment box or by email to the Technical Committee on its comment mailing list or, if you are a member of the TC, to the TC's mailing list [4]. If you provide your reason by email, please indicate in the subject line that this is in regard to the Call for Consent. Note that failing to provide a reason and/or remedy may result in an objection being deemed invalid.

URIs:

The Committee Specification is available here:

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

Editable source (Authoritative):
https://docs.oasis-open.org/codelist/genericode/v1.0/cs02/genericode-v1.0-cs02.xml

HTML:
https://docs.oasis-open.org/codelist/genericode/v1.0/cs02/genericode-v1.0-cs02.html

PDF:
https://docs.oasis-open.org/codelist/genericode/v1.0/cs02/genericode-v1.0-cs02.pdf

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:

https://docs.oasis-open.org/codelist/genericode/v1.0/cs02/genericode-v1.0-cs02.zip

Please contact OASIS TC Administration at tc-admin@lists.oasis-open.org with any questions you may have about this ballot.

--- Additional information ---

[1] OASIS Code List Representation TC
https://www.oasis-open.org/committees/codelist/

[2] Statements of use

- UBL TC:
https://lists.oasis-open.org/archives/codelist/202206/msg00002.html

- LegalXML Electronic Court Filing TC:
https://lists.oasis-open.org/archives/codelist/202207/msg00004.html

- NIEM Technical Architecture Committee (NTAC):
https://lists.oasis-open.org/archives/codelist-comment/202211/msg00000.html

[3] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent

[4] Comments may be submitted to the TC through the use of the OASIS TC Comment Facility as explained in the instructions located at https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=codelist

Comments submitted to the TC are publicly archived and can be viewed at https://lists.oasis-open.org/archives/codelist-comment/

Members of the TC should send comments directly to codelist@lists.oasis-open.org.