Subject: Re:Conference Call Correction
Mike, Unfortunately, I am with a client at a DoD EMall meeting all day Friday. I may be able to join the conference call for a short time depending on when we have lunch. I think there are four issues that need addressed - 1) XML in ebXML. I challenge anyone to find where we are using XML in what is being developed by the project teams. Not only in the TRP effort, but those of core components, business process, and registry and repository as well. In my opinion they are off developing (reinventing) OO/Open EDI under the guise of XML. Sorry folks - it won't sell. 2) Organizational submissions. Klaus has made it very clear that we are individuals participating in ebXML. My guess is no organization has "formally" reviewed our requirements document and "voted" on an organizational submission. Unless specifically directed to by Klaus, I don't believe any "organizational" submission should be treated as anything other than a submission by the individual making it. 3) Accomodating comments. WE are the ebXML requirements team. We are the ones who should determine what the contents of our document are as it moves forward. Certainly we listen to the technical expertise from the various project teams, and incorporate to the extent we don't disagree with them. However, in my opinion, the final decision on what is included in the requirements document coming out of our team is ours. The full plenary can certainly vote to reject the document, as can the steering and executive committees. 4) Process. My sense is you all should review the various submissions and identify as a group any you feel strongly about - one way or the other. I will then take that guidance in incorporating comments for the next draft. Mark Mark Crawford Research Fellow ______ LMI Logistics Management Institute 2000 Corporate Ridge, McLean, VA 22102-7805 (703) 917-7177 Fax (703) 917-7518 email@example.com http://www.lmi.org "Opportunity is what you make of it"
Powered by eList eXpress LLC