oasis-code-list-representation-genericode-0.1.pdf Details

Document Details     TC Member Document View
Title OASIS Code List Representation Specification
Name * OASIS Code List Representation Specification (268K)
Description The OASIS Code List Representation Specification and its drafts.
Group OASIS Code List Representation TC
Folder Discussion Drafts
Submitter Anthony Coates
Date Submitted Tuesday, 30 January 2007 08:25am
Document State Draft (A preliminary unapproved sketch, outline, or version.)
Access This document is visible to OASIS Code List Representation TC and shared with:
  • OASIS Open (General Membership)
  • General Public

Document Revisions
Name # State Submitter Date Action
14
Draft
Anthony Coates
2007-11-17
13
Draft
Anthony Coates
2007-10-12
12
Draft
Anthony Coates
2007-10-09
11
Draft
Anthony Coates
2007-10-08
10
Draft
Anthony Coates
2007-08-28
9
Draft
Anthony Coates
2007-08-27
8
Draft
Anthony Coates
2007-05-02
7
Draft
Anthony Coates
2007-04-30
6
Draft
Anthony Coates
2007-04-23
5
Draft
Anthony Coates
2007-04-15
4
Draft
Anthony Coates
2007-04-13
3
Draft
Anthony Coates
2007-04-04
2
Draft
Anthony Coates
2007-02-25
1
Draft
Anthony Coates
2007-02-22
0
Draft
Anthony Coates
2007-01-30
This doc

Comments  
Subject & Text Submitter Date Action
Initial comment by submitter
This initial 0.1 version is a sketch of the structure I am proposing for this document. Section 2 is a non-normative introduction to the concepts which underpin the genericode design.

Section 3 is very much a work in progress, which is intended to describe the main concepts in a normative fashion. I propose that we no longer seek to use a UML model normatively, as I don't think it can be done normatively with respect to the Schema, which must be normative. I am not sure what diagrams are appropriate for this section, whether to use some UML diagrams or graphical Schema diagrams to illustrate the concepts in a non-normative way, or whether to use Schema extracts (generated using XSLT stylesheets for repeatability) to do this. Perhaps both, I'm interested in feedback.

Section 4 is intended to be a normative reference to the constructs in the Schema. This is also a work in progress, but note that this entire section was generated from the Schema using an XSLT stylesheet. There is much more information yet to be added. Note that I have generated compact content model notation for the groups, and will also do so for the compact types. My plan is to put the necessary normative documentation into the Schema (much more than is in there now) and to have that documentation then rendered into this section.

I propose that the appendices should include a non-normative section on how to express simple code lists using genericode, and should also have some examples, e.g. from UBL and/or FpML.
Anthony Coates
2007-01-30
---