Minutes of UBL Library Content Subcommittee

Minutes of UBL Library Content Subcommittee

Tuesday, May 14, 2002, 8:00-9:52 am, California Time

Attendees

Ron Schuldt, Joseph Chiusano, Tim McGrath, Peter Yim, Kurt Conrad, Ray Seddigh, Lisa Seaburg, Marion Royal, Sue Probert, Monica Martin, Mike Adcock, Bill Meadows, Sally Chan

Minutes

Agenda Item #1: Welcome from Chair and appointment of Secretary to take minutes

Marion Royal appointed to take minutes.

Agenda Item #2: Acceptance of previous minutes

Without objection, the minutes are approved

Agenda Item #3: Action arising from previous meeting

Examples of ontology
Peter suggests that we have three one-hour primer sessions, then one half hour session to discuss the relationship of Ontology and UBL. Plans could include a working lunch session or perhaps a plenary. Leo will join us at the meeting.
Examples of controlled vocabulary, Mike was having difficulties with the conference call, so this item was not discussed in detail
Examples of elements for Order Response, discussion of this occurred later in the meeting.
Examples of context drivers, Arofan was not in attendance
Business process model for SCM, Tim reported that Mike Conroy was updating the UML model for three UBL Schema. Tim will request a mapping to our existing format.
Liaison Committee comments
- Tim discussed our Liaison with ARTS and said that this round of comments (from ARTS) should be considered as general as we become more aware and familiar with each others work.
- Arofan had had good response from the EIDX Guidelines committee

Agenda Item #4: Current Review - Editorial Team report

The conference call on Thursday at 9:00 am (California time) is now arranged and will be using the same telephone number and access code as the LCSC.
Lisa has combined all the comments into a spreadsheet and are ready for the LCSC to begin considerations.
Tim wants to make sure that the Editorial Team has a good understanding of the comments. If we need to get clarification, it should be done prior to the face to face meeting (F2F).

Agenda Item #5: Workplan

Mike reported no progress on the business rules dependencies
Next Document is Order Response
Discussion and debate on what the Order Response document is and what it should do took place. It appears obvious that the xCBL Order Response document tries to accomplish too much. Tim described the Order Response is either:
1. A message that indicates the correctness of the data in the order document or
2. A message that indicates the correctness of the data in the order document and allows modification.

Peter points out that in the business world we deal with an offer and a counteroffer. A mutual acceptance must occur before a contract is put in place. [Tim says a little later that we are not talking about trading partner agreements]

Sally expressed a strong preference to number 1 and introduced Order Change document as a separate document. This representation is in the use case and activity diagram for business process that she forwarded to Tim.

The aerospace (Ron) Order Response document serves two purposes. It acknowledges receipt and may propose a change. The buyer receives the proposed change and submits an Order Response indicating acceptance. The Order response is never an offer, but it may be counteroffer. Only the buyer can accept offer changes to be legitimate.

Mike suggests that an order change request can go in both directions. The seller may indicate an acceptance of an order but offer a different quantity. The buyer would then do an order response confirming the acceptance of the change .

Monica raised the awareness that many may confuse order response with acknowledgement of receipt. Tim said there are three levels of response:

1. transport level receipt
2. the secound level is the acknowledgement of who I am and understand how to talk with each other.
3. The third level is the commercial acceptance

It’s the third level that we are addressing here, and Tim would prefer to avoid the word "receipt" if possible to avoid confusion.

One can deduce that the order response document needs to indicate an acceptance of an offer in an order document. An order change document may be a separate document that may be responded to with a new order response document.

Tim is to prepare a summary of this and distribute to the mail list.
The next question is how to proceed, because can we without finalizing our consensus on the order change.
Shall we take the xCBL and strip out the components we don’t need or shall we create based on the work of the UBL order document. The consensus was that the latter approach was the correct one.
Codes and Identifiers
Ron suggest that the distinction between the two is not that difficult. A social security number is clearly an identifier, as in a license plate number. Identifiers are constantly changing and growing. The problem is that the term has been misused by EDI and EDIFACT.
Tim asks if the country code was an identifier because it changes and Ron responded that it should be a code because it was relatively stable.
Sue points out that there are maybe 3 or 4 different contexts of codes/identifier and that these different contexts compete with each other. None are right or wrong, they just have different definitions.

The conclusion of this discussion is that we need to come up with as many examples as we can as we approach the F2F and apply these terms to UBL.

Agenda Item #6: Reports on status of other UBL subcommittees

Tools and technique sc ()

No Report

Naming and design rules sc (anyone)

Preparing documents for F2F
New version of codelist paper out. Tim will forward to the LCSC

Context drivers sc (Sue)

Waiting for F2F

Context assembly sc ()

No report
Context assembly having regular meetings, getting very deep, but don't expect answers until after face-to-face that will impact LCSC.

Agenda Item #7: Reports on status of other related projects

Sue has been appointed as our liaison to the UN/CEFACT.

Agenda Item #8: Other Business

Tim is working on the F2F agenda and will be incorporating Peters Ontology program.

Agenda Item #9: Next meeting.

This has been the best attended meeting for a while
Next call is at this time on 21 May 2002.