[regrep-cc-review] CC Review 2/23/02 Minutes & Functional PointsMapping Template

["CHIUSANO, Joseph" <JCHIUSANO@lmi.org>]

Title: CC Review 2/23/02 Minutes & Functional Points Mapping Template

Hi All,
Our initial conference call went very well.  Minutes are attached below (thanks Lisa!) - please feel free to ask about anything you may not be clear on.  Our next call is Wednesday, Feb. 6 at 2:00 EST - call details are at end of minutes.

Also, below please find the Functional Points Mapping Template that we discussed.  Please use this as a starting point for the mapping between the CC spec and Registry specifications that we discussed.  No need to submit anything to me before our next call - we'll just discuss our progress at the call.  Please use version 1.75 of the CC spec which I'll be forwarding to the TC very shortly.  Our initial goal is simply to start filling in functional points and page numbers, with the other columns being populated later.  At some point we will centralize our individual documents into a master document that I will maintain.

<<CC Spec-Registry Functional Points.doc>>
PLEASE ALSO NOTE:  I'm not 100% sure that our listserv is functioning properly, so please reply to this e-mail and let me know if you received 1 copy of this e-mail or 2 (because I have sent it to both the listserv and individual addresses) - you can simply give a number.  If anyone responds "1", that tells me that there may be a listserv problem.  If all respond "2", then we can assume the listserv is functioning properly and I will no longer send 2 copies.  Thanks for your patience with this.

Looking forward to our next call!
Regards,
Joe
MINUTES:
Minutes of the OASIS/ebXML Registry TC Subcommittee on Core Components
Conference Call Meeting, Wednesday, January 23, 2:00 - 4:00 p.m. Eastern Time

Attendees:
Kathryn Breininger, Boeing
Lisa Carnahan, NIST
Joe Chiusano, LMI

1. Our DRAFT goal statement is fourfold:
-Understand the expectations and requirements for ebXML Registry functionality defined in the Core Components Technical Specification;
-Where appropriate propose changes and additions to the ebXML Registry V3 specifications to meet the expectations and requirements defined in the Core Components Technical Specification;
-Help ensure that the Registry TC efforts are aligned with CC-related ebXML committee by serving liaison roles;
- Serve as a resource to the Registry TC in understanding the CC model and processes.

2. In our discussion, Kathryn noted that Boeing has implemented a registry that is compatible with ebXML registry in functionality; however not compliant (with a little 'c' and not a Capital 'C'). One of the benefits for our subteam is that the Boeing registry developers have always had an eye toward the registration of core components. We will be able to use their insight and lessons learned as we proceed.

3. Joe provided the Core Component Technical Specification schedule.
-the new version was released on January 16;
-the committee comment period ends January 31;
-the anticipated plenary vote by the EBTWG is February 8;
-an open comment period ends 30 days after the vote;
-the document proceeds to UN/CEFACT approval.

4. Upon concurrence with the CC folks, Joe will be sending the new CC document to the CC sub-team members as well as the Registry TC (as per Kathryn).

5. Kathryn and Lisa both noted that Joe's document UN/CEFACT Core Components At-A-Glance is extremely helpful in understanding the CC spec. We reviewed the At-A-Glance document and produced a list of questions that Joe will be asking the CC folks (Mary Kay). The list includes items related to: cc transformations from UML to XML; representing use/re-use; clarification on discovery phrase such as "same definition", "appropriate generic definition and structure"; storing (or acting on) constraint rules and representing the CC UID.  This document will also be sent to the Registry TC (as per Kathryn)

6. The Core Components Realization document from the EBTWG was briefly discussed. Joe will be producing a similar At-A-Glance document for this spec. The outcome of the discussion was that we have more questions than answers.

7. We agreed to an approach to tackle the challenge of meeting our goals. In general terms we will be extracting the registry requirements from the CC specification and then determining whether our registry model/services and provide the necessary functionality to meet the requirements. Joe will be forwarding to the sub-team a table template that we will use to capture the requirements and our analysis. Joe, Kathryn, and Lisa each agreed perform this task by breaking the document down as Discovery of CCs (Joe), Storage of CCs (Kathryn), and Constraint Language (Lisa). Each will take a section respectively. We have a goal to have a first pass done by the next conference call.

8. For purposes of our sub-team, we agreed that Joe would serve as our liaison to the CC folks, and Lisa would serve as liaison to the EBTWG as necessary.

9. Our next meeting will take place Wednesday, Feb. 6 at 2:00 EST. Here is the call-in info.

CALL DATE: FEB-06-2002 (Wednesday)
CALL TIME: 02:00 PM EASTERN TIME
DURATION: 2 hr
USA Toll Free Number: 800-779-6816

PASSCODE: 21275
LEADER: Ms Lisa Carnahan

**************************************************************************
  Joseph M. Chiusano
  Logistics Management Institute
  2000 Corporate Ridge
  McLean, VA 22102
  Email: jchiusano@lmi.org
  Tel: 571.633.7722
**************************************************************************

CC Spec-Registry Functional Points.doc