OASIS Code List Representation TC

Join TC     TC Page     Send a comment to this TC

Defining an XML format for interchange, documentation and management of code lists (a.k.a. controlled vocabularies or coded value enumerations) in any processing context

Ken Holman, gkholman@CraneSoftwrights.com, Chair

Table of Contents

Announcements

Current project status:

Genericode: finalized version 1.0 Committee Specification published (Announcement; links copied below)

Context/value association: finalized version 1.0 Committee Specification CS01 (links below)


Overview

For more information, see the TC Charter and FAQ


Technical Work Produced by the Committee

Committee Specification genericode 1.0 28 December 2007:

Specification: PDF-US

Requirements (2 May 2007)

Schemata:
Genericode
XML

Namespace

Committee Specification Context/Value Association 1.0 15 April 2010:

Specification: HTML, PDF-A4, PDF-US

Schemata:
Context/value association
XML

Namespace

Wiki for OASIS Code List Representation TC member collaboration

  • deployments of genericode and CVA
  • publicly-available genericode and CVA files
  • published processes incorporating genericode and/or CVA

TC Mailing Lists and Official Comments

OASIS and the Code List Representation TC welcome your comments at any time, not just during public review cycles!

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be located via the button marked "Send A Comment" at the top of this page, or directly here.

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members.

Community Mail List

Both members and non-members of the Code List Representation TC are welcome to participate in the unmoderated Code List Representation Developer Mail List by subscribing at the OASIS mail list manager.

A community of volunteers both on and off the committee contribute to the open discussions on this developer list. Please join these discussions and contribute your questions and answers.

However, official comments still must be submitted to the TC by any person through the use of the OASIS TC Comment Facility indicated above and not through this developer list.



Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.