Re: [ubl-clsc] Teleconference minutes - 2004-01-14 10:30PST/13:30EST/18:30UTC

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

(Edited comments from other committees near end)

Roll:

Anne Hendry
Alan Stitzer
Marty Burns
Paul Spencer
G. Ken Holman

Regrets:

Mavis Cournane
Sue Probert

Absent:

Tony Coates

At 2004-01-13 13:14 -0500, the agenda was posted as:

   http://lists.oasis-open.org/archives/ubl-clsc/200401/msg00009.html

>The minutes from the last meeting were posted at:
>
>   http://lists.oasis-open.org/archives/ubl-clsc/200401/msg00004.html

Accepted.

>The agenda is at the least:
>
>1) Deliverables
>
>  - chapter structure agreed upon in email thread:
>
>    http://lists.oasis-open.org/archives/ubl-clsc/200401/msg00006.html

closed.

>2) Requirements document
>
>  - Ken's revisions of intro and chapter 1 supplied to Marty
>  - status of document

Requirement paragraphs needed
  - Alan and Ken to offer paragraphs through the list

All members please review the latest (note after opening the available Word 
file to refresh all fields (typically the F9 key) and feedback any and all 
input to the list for Marty to incorporate.  Marty needs feedback.

>3) Feedback on Tony's submission

Closed as an agenda item ... content now partially incorporated into the 
committee document being edited ... could Tony please review and supply 
updated content for the committee document?  Will be treated from this 
point as a chapter of the main document.

>4) TC184/SC4
>
>   http://lists.oasis-open.org/archives/ubl/200401/msg00004.html
>
>   - can any of the attendees to the teleconference contribute on this topic?

No input available on TC184/SC4.

Alan commented on the insurance industry's prevalent use of code lists and 
will post pointers to publicly available information.  One comment observed 
the ACORD perspective of code lists includes a concept of sub-lists ... 
discussion ensued and two ways of looking at this came to light:

    (1) - each sub-list is a separate code list and the set of codes is a 
union of the lists
        - trading partners need to agree on the collection of code lists to use
    (2) - the list is a whole and has members in different sub-lists
        - trading partners need to agree on which sub-lists to use

What about "related" code lists, such that a two-part entry would have the 
code list of the second part dependant upon the choice of the code for the 
first part.

Marty noted that the simplest "one indivisible atomic code list" in the 
data model could be used to build other code list models.

A short discussion of trading partner agreements brought to light the 
importance at times for larger trading partners to dictate what others must 
follow.

>5) Any other business

Anne brought the following observations from other committees:

ISC - member noted development of production system for UBL PO and Invoice 
created and deployed by IMPAQ, being used (for example) by Sun and Q 
Associates (keep an eye out for press on this topic)

LCSC - chair agreed to take TTSC use scenarios for compliance definitions 
and turn into a discussion paper for LCSC

Coordination - discussion of contextualization

TTSC - the EDIFIX tool will be used to generate schemas and Michael Dill 
needs code list fragments ASAP


Meeting conclusion

Ken expressed concern that more effort is needed between meetings to help 
Marty with the content of the committee specification.  Working back from 
the February face-to-face, we need to be in a position soon to guide LCSC 
in the construction of code lists for TTSC to use for synthesis.  VERY SOON!

Marty is encouraged that we have a lot of what we need and it is only a 
matter of checking the implementation details against the recorded 
requirements to see where we sit.

Would all members please try to be active on the email list so as to get 
work accomplished between teleconferences.

Thanks!

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


--
North America (Washington, DC): 3-day XSLT/2-day XSL-FO 2004-03-15
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