UBL LCSC Minutes

Tuesday - July 16, 2002

Attendees: Tim McGrath (chair), Mike Adcock, Bill Meadows, Lisa Seaburg, Debbie Quezadaz, Monica Martin, Joe Chuisano, Sally Chan, Marion Royal

1. Welcome from Chair and appointment of Secretary to take minutes - Lisa

2. Acceptance of previous minutes - We don't have quorum, so no minutes accepted.

3. Action arising from last week

• Update Schema Generator (Gunther). - No report.
• Speak to Oracle about XML database (Debbie/Garrett). - Nothing yet.

4. Items under review

The papers below are all being held till the 30th for comments. Tim: we need time to put these together, we are hoping they submit sooner rather than later.

Process for comments, authors to deal with them. Instead of passing them back through Lisa, go direct to author, author gets back to group through the list.

• Methodology - document on website, sent out email to group announcing document, no comments yet.
• Code/Identifier - Mike is working on examples. Monica had given her comments in, these are being worked on.
• Date/Time - Alan Stitzer has submitted comments along with Bob Miller.

  This paper is both a Library Content and NDR. Eve has suggested that the NDR team help deal with the comments. Mike and Gunther are affected by whether or not the NDR team deals with the comments on Date/Time and Code/Identifier.

  Mike: I have had a look at the Order Spreadsheet and made notes of where the spreadsheet needs to be changed to match the Date/Time paper. the next task is to go through and apply the changes. Mike and Gunther want to do this together.

• Order Response model - Lisa has not had time to get to it. But, there has also been no comments through the week. If and when they come, they will be incorporated into this model and then a new version sent out.

  ACTION ITEM: Bill: will research and send out a list of codes for the document, they should be a subset of the EDIFACT and X12 code lists. There are a lot of codes that clearly don't work for this document.

5. Other Work Items

• Class Diagram Librarian (Frank) -

  Mike: Went through Order spreadsheet, created UML diagram to it. It is complete as the spreadsheet. The process has actually thrown up a number of areas of objects that are not connected to anything. There are also multiplic objects that need to be looked at. Mike sent notes on this to Tim and Lisa. On the whole, Mike is quite pleased. There are some problems with Rational Rose, but other than that, it seems to work quite well.

  We can probably put the UML diagram into Word document to ship around to the group. One question is, do we want to distribute this at this point? There will be a few changes within the week.

  TIM: This proves the value the exercise and of having a graphical model. It gives our model strength. It is a moving target right now, so do we distribute or hold until later? It won't hurt us to distribute today together with the issues list. Model is a reflection of the current library as it stands today and will be changing along with the library.

  ACTION ITEM: Lisa, put up on the webpage. This is the word document, the Rose file, and comments. Work with Mike on this.

• Private vs Standard Identifier (Frank, Mike, Gunther) - Background paper,
• Actioning Disposition tasks (Various) - Put the Action Item document on the website and send email to the group. Tim received the document late (because of email problem between Lisa and him).

  ACTION ITEM: Lisa, critical path list for next week.

6. Schedule for next release

• Editing team report - Next week we need to have this coming together. Issues that Mike identified as part of class diagraming also need to go on the list.
• Timeline update - There are two milestones we need to look at. Meeting of the Liaison committee is something we need to target as a publish date, because that gives us a place to focus our deliveries. Tim: brief the LSC about the next release. Important things is to end up with a quality distribution package instead of going quickly.

7. Proposed requirements for tools and techniques - Arofan and Gunther are both at CCTs meeting, not present.

There has been some progress on getting XML Spy licenses. UBL has been granted 10 licenses, to be shared. Some people already have one, so right now its: Sally, Mike and Bill. Tim will organize this.

• Status of research - No report.
• XML Spy requirements - No report.

8. Reports on status of other UBL subcommittees

• Tools and technique sc - No report.
• Naming and design rules sc - Meeting was to small to continue, deferred till next week.
• Context drivers sc - No report.
• Context assembly sc - No report.
• Chairs sc - No report, has not met until next Monday. On agenda are issues such as positions papers.
• Liaison sc - Met last Friday, Tim had emailed his comments and agenda items. Tim gave them a status report on disposition of comments and next distribution. Also explained the fact we would produce a more comprehentive set of documentation. We want comments on reusable types as a priority over the actual document elements. LSC has a new member, NACS (John Harvey). They are an affiliation of the retail group. They also had Bob Matsey of UIG who attended as an observer.

9. Reports on status of other related projects

• Core Component Technical Specs (Mike) - They are meeting this week, so no full report today. They should have something by our next meeting. Sally will raise the subject of how to get the comments and document public. There is a document called the ebtwg Open development process. The fixed TS should be coming out within the next couple of weeks. Comment was made about the length of time it has taken to handle the number of comments they had been given. Also comment was made about their website not being kept up to date.
• eBTWG CCSD (Sally/Monica) - Sally spent last two weeks trying to summarize what they have done in the meetings.

  This summary document is rough draft now, but shows how the work ties to the business process. Shows step by step how you identify Core Components using your business process. Also shows example of how to write the XML document using these dictionary entry names that have been identified. (Mike has a Message Assembly document to send me for review. ) An example purchase order in EDI format, which is currently being implemented at Boeing, ATA XML format, and ebXML core component message format is show. This document was sent out to the CCSD group last week for review.

  TIM: There are a few areas of interest for us, how the CC were identified, and how the XML was done.

  SALLY: Its shows the step by step analysis of the business data, identifying the BCC and ACC, BBIE and ABIE. It shows what you need to start, how you do it, what is the deliverables, and how to use the deliverables.

  TIM: how does this fit in the UMM business process models?

  Sally: If you don't start with a UMM model, then you have to define the business context of the model.

  TIM: Is this document available to the public yet.

  SALLY: Not yet, we are still reviewing the step by step process with in the document.

  TIM: We will look forward to seeing this document. We see the overlaps and it is of interest to us all.

10. Other Business - None

11. Next meeting - Tuesday, 23 July 2002