The OASIS Code List Representation Technical Committee has approved [1] a revised charter, included below. The TC name, statement of purpose, scope, list of deliverables, audience, IPR mode and language specified in the revision below will constitute the TC's official charter.
The TC will hold its first meeting under the revised charter on 05 March 2021 at 15:00 UTC. Submissions of technology for consideration by the TC and the beginning of technical discussions under the revised charter may begin no sooner than this first meeting.
OASIS and the TC welcome participation by all interested parties. The eligibility requirements for becoming a participant in the TC at the first meeting are:
(a) you must be an employee of an OASIS member organization or an individual member of OASIS, andd
â(b) you must join the Technical Committee after the revised charter is published to the TC's home page on 27 February 2021, which members may do by using the Roster "join group" link on the TC's home page at [2].
Note that everyone who wishes to participate must explicitly join the TC as described in (b) above. Membership under the original charter does not automatically carry over.
Non-OASIS members who wish to participate may contact us about joining OASIS [3]. Instructions for joining the Technical Committee can be found at the "Join This TC" link on the TC's public home page [4] Â
Please feel free to forward this announcement to any other appropriate lists. OASIS is an open standards organization; we encourage your participation in our work.
---
[1] Recharter ballot:
https://www.oasis-open.org/committees/ballot.php?id=3572
[2] TC web page:
https://www.oasis-open.org/apps/org/workgroup/codelist/index.php
[3] https://www.oasis-open.org/join
[4] https://www.oasis-open.org/committees/codelist
Revised Charter
Section 1: TC Charter
(1)(a) TC Name
Code List Representation (codelist)
(1)(b) Statement of Purpose
Many communities (for example business sectors and public authorities) exchange and process information in which commonly accepted semantic concepts can be expressed using concise mnemonics or abbreviations called "codes". Choosing a collection of these codes can constrain the _expression_ of information to an agreed-upon set, requiring the exchange to reference one or more members from only a limited list of such codes, variously called "code lists", "enumerations", or "controlled vocabularies".
Code lists then 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 nonstandardized 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. An advantage of using a controlled set of semantic concepts is in localization where the associated documentation for the coded values can include descriptions in different languages, thus not requiring the coded values themselves to be translated, or where translation is desired, the semantic equivalence of values can be described.
Code lists have been used for many years, and they have been published and disseminated in manners that have not been IT-enabled for ease of computer processing. To date no standardized IT-enabled representation exists.
The Code List Representation TC purpose is to develop IT-enabling standards that support the machine _expression_, interchange, documentation, management, processing, and validation of code lists for use in any information technology context.
Business Benefits
The standards developed by the Code List Representation TC aim to be beneficial for any community that needs to disseminate IT-enabled expressions of code lists for the exchange and processing of enumerated values.
Key stakeholders are standardization bodies that need to specify code lists and their representation for exchange and automatic process, registration and source authorities that publish code lists, business sectors and public authorities that use code lists in their business exchanges, and implementors of software and services that process code lists.
(1)(c) Scope
Define, develop and maintain a semantic library for code lists (genericode) and related syntax bindings to represent code lists in XML and other machine processable formats for their interchange, documentation and management in any machine-processing context.
Develop any related technical specifications to support the use of code lists.
Promote genericode as the international standard for the IT-enabled representation of code lists.
Should the TC decide so, submit genericode and any other standard developed by the TC as publicly available specification to external standard development organizations (SDOs) and, where possible, fulfill their associated responsibilities of being their designated maintenance authority.
The publication of code lists is out of scope of this TC.
(1)(d) Deliverables
The Code List Representation TC maintains the existing genericode Committee Specification and oversees its evolution to the following set of deliverables:
- a semantic model / meta-model of genericode
- an XML serialization of the genericode semantic model, with the intent of backward compatibility (or even no changes) to the existing genericode
- prepare examples of the use of and the reference to genericode resources
- possibly develop new specifications such as operations on a code list e.g. create, add, delete, update
- possibly develop new syntax serializations and schemas, such as JSON
- possibly include sample non-normative software for transliteration between syntaxes
- possibly develop a Schematron value validation script
- possibly document the use of genericode as a sparse-table serialization, including concepts such as joining tables and foreign keys
RF on limited terms
(1)(f) Audience
Anyone who works with code lists and has a requirement to transmit and process an IT-enabled _expression_ of the code list values and/or their metadata between systems.
Also source authorities and publishing authorities who create, publish, and disseminate code lists, based on specific business sector or public authority requirements, including those with pre-existing or 3rd party code lists.
Users and consumers of code lists, who may also find a standardized IT-enabled deployment format for such lists easier to employ.
Those who are responsible for defining XML vocabulariesvmay be interested in describing a constrained set of values to represent agreed-upon semantic concepts in order to control information items.
(1)(g) Language
English
Section 2: Additional Information
(2)(a) Identification of Similar Work
ISO/IEC JTC 1/SC 32 has developed ISO/IEC 15944-10 that defines the business operational view of and the need for code lists, without the functional services view of syntax serializations that are in scope of this TC.
(2)(b) First TC Meeting
The first meeting under the revised charter will be held Friday, 05 March 2021 at 15:00 UTC/10:00 EST/16:00 CET/02:00 AEDT via Zoom. The meeting will be sponsored by Crane Softwrights Ltd.
(2)(c) Ongoing Meeting Schedule
It is expected to be a weekly or bi-weekly meeting online and occasionally face-to-face meetings when needed and where a TC member can assume the responsibility for hosting the meeting.
(2)(d) TC Proposers
N/A
(2)(e) Primary Representatives' Support
N/A
(2)(f) TC Convener
Andrea Caccia, andrea.caccia@studiocaccia.com, Individual member
(2)(g) OASIS Member Section
N/A
(2)(h) Anticipated Contributions
The current deliverables of the Code List Representation TC, feedback from existing code list Source Authorities and Publishing Authorities.
(2)(i) FAQ Document
N/A
(2)(j) Work Product Titles and Acronyms
genericode
ChetÂEnsignChief Technical Community Steward OASIS Open | Â | Â | Â |
|