Re: [ubl-csc] Revised outcomes of coordination call 12 December 2003

["G. Ken Holman" <gkholman@CraneSoftwrights.com>]

At 2003-12-13 10:34 -0800, jon.bosak@sun.com wrote:
>2003-1212-01 Code list ownership clarification
>
>    Issue
>
>       Code list ownership (mechanism, population, identification)
>       needs clarification.
>
>    Outcomes (2003.12.12)
>
>       We think that this describes how it's going to work:
>
>        - LCSC produces the code list catalogue that identifies
>          which code lists need to be included in UBL and provides
>          the enumerated values that will be used to populate the
>          code lists.
>
>        - CLSC develops the standard schema format for the code
>          lists to be used in UBL according to schema naming and
>          design rules specified by NDRSC.  We hope that this
>          format will be adopted outside of UBL as well, but its
>          basic requirement is to accommodate the code lists in the
>          UBL code list catalogue and the values provided by LC.
>
>        - CLSC also develops a methodology for the maintenance and
>          user extension of code lists (example: standard / stock /
>          placebo mechanism).
>
>        - TTSC instantiates the code lists in the catalogue by
>          generating schemas that incorporate the values provided
>          by LCSC in the format defined by CLSC.
>
>    Assignments (2003.12.12)
>
>       Ken Holman, Mavis Cournane, and Sue Probert are assigned the
>       task of further clarifying the outcomes of 2003.12.12 above
>       and submitting the result to the CSC.
>
>    Carried forward (2003.12.12)
>
>       We need to reach out to external code list agencies to work
>       with us; could this be a job for the Liaison SC?  [Probably
>       not; the MoU/MG might be better.  We need to consider this
>       further.]

Yesterday the CLSC determined that we would, indeed, *draft* a standard W3C 
Schema format for the code lists but that we would deliver them to NDRSC 
for validation.  We then expect NDRSC to polish and return the official W3C 
Schema code list expressions back to CLSC for inclusion in the UBL Code 
List technical specification.

The LCSC catalogue and the NDRSC schema instantiation of the CLSC model are 
then all taken by TTSC to produce the UBL Code List Schemas.

There is some debate still in CLSC if the W3C Schema expressions should be 
a normative annex or a sibling chapter to the data model.  We want to 
promote the UBL Code List technical specification to other technical 
non-XML domains (e.g. database implementations of code lists) and not give 
the impression it is solely for W3C Schema implementations.

I hope this helps ... I'm going to try and attend tomorrow's coordination 
meeting to address any questions.

........................... Ken

p.s. the decision for CLSC to produce the draft W3C Schema expressions was 
not unanimous ... one position held that CLSC supply NDRSC only the data 
model and NDRSC return the W3C Schema expression back to CLSC to avoid any 
problems with interpreting the NDRSC rules ... the decision described above 
carried the day

--
North America (Washington, DC): 3-day XSLT/2-day XSL-FO 2004-02-09
Instructor-led on-site corporate, government & user group training
for XSLT and XSL-FO world-wide:  please contact us for the details

G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/o/
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
ISBN 0-13-065196-6                       Definitive XSLT and XPath
ISBN 0-13-140374-5                               Definitive XSL-FO
ISBN 1-894049-08-X   Practical Transformation Using XSLT and XPath
ISBN 1-894049-11-X               Practical Formatting Using XSL-FO
Member of the XML Guild of Practitioners:     http://XMLGuild.info
Male Breast Cancer Awareness  http://www.CraneSoftwrights.com/o/bc