[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [Fwd: ebXML:CoreComponents/Meeting Agenda Topics]
Hi all, possibly again. I sent this out earlier today, and receive an error "permanent delivery failure". OASIS asked that I resend to see if the error occurs again. For those that already received this, sorry for the duplication. Regards, Lisa M. Shreve
Hi everyone!
- From: "Lisa M. Shreve" <lms@wwnet.com>
- To: "ebxml-core@lists.oasis-open.org" <ebxml-core@lists.oasis-open.org>, lms@wwnet.com
- Date: Wed, 19 Jan 2000 09:13:15 -0500
I hope everyone has been as busy as I have reviewing our set of reference documents! With the meeting quickly approaching, we can maximize our productivity with everyone familiar with the various projects & activities related to our work effort.
Below is a report on the first steering committee conference call, which took place late last week. And following that is an agenda outline for the upcoming meeting. I look forward to seeing everyone there, and hope your travel is uneventful.
Lisa M. Shreve
Late last week was a conference call for all of the Project Team leaders, which I participated in. At long last, the web site is up and operational, but they are still working on the site. Hopefully, the listserv is stable now. In the conference call the following was discussed:
Agenda Topics:
- Hotel selection to be finalized by Friday, 1/14. Initially, there were some problems with getting reservations ... they didn't show the group. They corrected this problem late in the morning Monday, and I trust that reservations directly through the hotel are going smoothly now.
- Monday 1/31 afternoon session will include 15 minutes from each project team, to provide visibility for work items for the week. Friday AM session will start at 8:00, to ensure completion by 12:00 Noon. The steering committee [each team leader plus the executive committee] will meet Tuesday - Thursday, to review days events and bring attention to any issues or coordination necessary.
- Coordination
- The Requirements Project Team wants to meet with each Project team on Tuesday, for approx 30 minutes. I will try to delay this to as late in the day as possible
- Requirements project team expects to complete their work during the meeting, and requested details on the approval cycle.
- The approval process is under discussion still, but this will be completed and disclosed prior to the meeting.
- The Marketing Project Team wants to meet with each group on Thursday, 30 minutes
- We will need to assign members to monitor activities of groups which we need close coordination with, and will need to schedule some joint meeting time. The ones which come immediately to mind, but this is something we can discuss, are:
- Business Process
- Technical Architecture
- Registry/Repository
- Transport/Routing
From the short time we spent together in San Jose last November, it was clear that we as a group have varried experiences and knowledge we are bringing together for this effort. It is critical that we quickly come to a common vision for products and deliverables.
We have a very aggressive delivery schedule, the less we have to invent, the quicker we complete our work. It is essential that we borrow/accept input from the variety of reference materials proposed. Once we establish a common vision to a level where the fundamental elements are visible, we can then look to our reference materials to determine what we can use from each. For example, the ASC X12 Technical Report contains an algorithm for converting a text string to a label. This may be of value, and we could utilize this as a starting point if we have a need for such an algoritm.
- Establish Common Vision
- Define ebXML deliverables
- Define ebXML CoreComponents deliverables, within context of overall ebXML deliverables
- Identify dependencies/expectations for outside activities and assumptions on what that project team is responsible
- Identify key elements/characteristics of CoreComponents solution
- Conduct a complete walk through with an example
- Key elements of solution Versus Reference Materials
- For each key element of the solution identify related reference materials
- form work groups for each major subject area [this may combine multiple key elements]
- review related reference documents for what we can use
- Identify missing information/needs for additional information
- Plan future work
- work to be completed between meetings
- work for the May meeting
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC