[code] Agenda and prototype for tomorrow's meeting

Although we have not yet established our task group equivalent to a standing committee, I can think of the following areas that should be standing items for review at each meeting:

4.1. Code list task group deliverables

No change in the list of deliverables.

4.2. NDR rules related to code lists

Who will volunteer to write up and take the decisions of this group for NDR? At one point I thought Lisa was prepared to do this.

4.3. FPSC guidelines related to code list member supplemental information

Who will volunteer to write up and take the decisions of this group for FPSC? At one point I thought Dan was prepared to do this.

4.4. Code list catalogue

Anne has very kindly offered to maintain this catalogue. It will be delivered to LCSC as a roadmap to implementation of the decisions made by the code list task group.

5. Outstanding action items

20030814-Action1 - Tony - supplemental file approach summary

summarize the approach and justification of capturing supplemental information in an adjunct file separate from the W3C Schema expression used for validation
http://lists.oasis-open.org/archives/ubl-lcsc/200308/msg00028.html

20030814-Action2 - Gunther - namespace-based approach summary

summarize an approach and justification of using a namespace-based scheme for capturing information about a code list, rather than using attributes in a UBL instance
http://lists.oasis-open.org/archives/ubl-lcsc/200308/msg00055.html
on a personal note, I think there is some confusion in my mind over Gunther's use of "supplementary information" and what we have been talking about for "supplemental information" for presentation purposes; I wonder if during the last teleconference there were others as confused as I was when this item was brought to our attention

6. Agenda items

20030904-Agenda1 - review "code list straw-man 1 technical proposal"

Ken is unable to attend to present this document
at the time the document was prepared the Kavi system was unavailable to post documents and the package was distributed through the email list
the evolution of this document has the potential of being the record of the technical decisions of the code list task group, from which those members writing contributions to NDRSC, FPSC and LCSC

20030828-Agenda2 - supplemental non-validation information

a technical discussion on issues of maintaining supplemental information useful for presentation and other non-validation-oriented purposes
the lack of tool support is preventing meaningful experimentation in this area
some technical decisions highlighted in the straw-man proposal need to be addressed

7. Action items

A review of all action items both from before the meeting and established during the meeting.

8. Future meetings

The next teleconference will be September 11, 2003.

Important note: the meeting Thursday of next week should be the last teleconference of the code list task group, as we need to deliver our final results the following day to NDRSC, LCSC and FPSC

please be prepared to comment and contribute through the mail list between now and then
the next meeting should be a rubber stamping of the decisions and positions put forward through the week in the technical methodologies, as well as draft submissions to NDRSC, LCSC and FPSC based on those methodologies

9. Adjournment

Meetings will be held to less than an hour's length.

ubl-lcsc message

Code list task group - Agenda 20030904 - 15:00UTC (11:00EDT/08:00PDT) - DRAFT

1. Roll call and quorum

2. Agenda

3. Minutes of the last meeting

4. Reports of standing committees