Response posted at the request of original author, Mary Kay Blantz.
Please forgive the duplicate posting if you've already seen this.
-------- Original Message --------
From: - Wed Apr 17 16:32:28 2002
X-UIDL: DC>!!ZQN!!MmB!!1-?!!
X-Mozilla-Status: 0013
X-Mozilla-Status2: 00000000
Return-Path: <[EMAIL PROTECTED]>
Received: from c011.snv.cp.net (c011-mx000.c011.snv.cp.net
[209.228.34.206]) by jacknix.metronet.com (8.10.1/8.10.1) with SMTP id
g3HIbxb08806 for <[EMAIL PROTECTED]>; Wed, 17 Apr 2002 13:37:59 -0500
(CDT)
Received: (cpmta 3378 invoked from network); 17 Apr 2002 11:39:06 -0700
Delivered-To: [EMAIL PROTECTED]
Received: (cpmta 3375 invoked from network); 17 Apr 2002 11:39:06 -0700
Delivered-To: [EMAIL PROTECTED]
Received: (cpmta 3366 invoked from network); 17 Apr 2002 11:39:06 -0700
Received: from 63.65.132.35 (HELO karloff.boston.amer.iona.com) by
smtp.c011.snv.cp.net (209.228.34.206) with SMTP; 17 Apr 2002 11:39:06 -0700
X-Received: 17 Apr 2002 18:39:06 GMT
Received: from AMERWEST-EMS1.IONAGLOBAL.COM ([10.81.1.38]) by
karloff.boston.amer.iona.com (8.9.3/iona-1.02-sjamison) with ESMTP id
OAA11761; Wed, 17 Apr 2002 14:39:02 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: [EDI-L] Article on ebXML Core Components -posted for Mary K
Blantz -IONA Technologies
Date: Wed, 17 Apr 2002 11:39:01 -0700
Message-ID:
<[EMAIL PROTECTED]>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [EDI-L] Article on ebXML Core Components
Thread-Index: AcHloh5yVAFcY0HeSEO68CdO+yB30wAnGRyg
From: "Loos, Claus" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>, "edi-l" <[EMAIL PROTECTED]>,
"ebxml-dev" <[EMAIL PROTECTED]>, "XML/EDI" <[EMAIL PROTECTED]>
Cc: "Blantz, Mary Kay" <[EMAIL PROTECTED]>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by
jacknix.metronet.com id g3HIbxb08806
X-UIDL: DC>!!ZQN!!MmB!!1-?!!
Status: U
As a former Co-Chair of ebXML Core Components, a current member of two of the ebXML
Core Components Project Teams and the Chair of X12 Materials Management, I feel
compelled to respond to some of Mike's comments. While much of what he has said is
true, I do not agree with his conclusions on Core Components.
It is likely that the Core Components project was the most ambitious of all the ebXML
efforts; which probably made it the most likely to fail, but also the most likely to
be of genuine global value. The goal was the development of syntax-neutral, reusable
building blocks that would allow interoperability no matter what syntax was being
used. This is an incredible goal, and requires the support and participation of
widely diverse business and technical experts.
Some EWG and X12 subcommittees have agreed to work jointly on both Core Components and
ultimately on the development of international XML documents. Materials Management,
for example, has made this decision. This is excellent news for all businesses that
will implement XML for their Materials Management processes.
Our previous attempts to align X12 and EDIFACT were helpful, but it would have been
much better not to have two different syntaxes for the same business processes in the
first place. It is very exciting that if we are successful we will have one
international XML standard message for any given business process, and through the
work of ebXML Business Process and Core Components will be able to interoperate with
the other syntaxes. While this does not preclude companies developing their own
special customized versions, it gives them the opportunity to align with the global
standard and reduce costs for themselves and their trading partners.
The use of UIDs for Core Components, both Basic and Aggregate, is a key to
interoperability. When this concept is presented to groups developing their own XML,
they greet this ability with enthusiasm and commitment.
The new ebXML Core Components Supplemental Documents Project Team is 'proving' the
validity of the ebXML Core Components Technical Specification, while developing an
end-to-end example based on an existing business process. While our group is already
quite large, we would welcome participation by additional business and technical
experts.
The results of our work will be used to
* Recommend changes to the Technical Specification, if any are needed
* Serve as a basis for the CC Primer, which will be used by teams all over the world
to discover Core Components
I am sure that our Chair, Melanie McCarthy, would invite anyone to join our list
serve, participate in our conference calls, and attend our meetings. The next meeting
will be help May 20th to 24th, in Barcelona.
For CCSD:
Boeing and why chosen
Ultimate goal to do ebXML BP and CC end-to-end example
Detailed steps
Learned that the BP Worksheets need change and didn't help much
Learned that an accurate Class Diagram is critical
Way we worked
Team list
List serve
Spreadsheet
Mention OAGI
Conference Calls
Next meeting
-----Original Message-----
From: Mike Rawlins [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 16, 2002 3:45 PM
To: edi-l; ebxml-dev; XML/EDI
Subject: [EDI-L] Article on ebXML Core Components
I've just posted the next to last article in my series on ebXML - A
Critical Analysis. You may find "ebXML Core Components - the master
data dictionary?" at the URL below.
--
Michael C. Rawlins, Rawlins EC Consulting
www.rawlinsecconsulting.com
------------------------ Yahoo! Groups Sponsor ---------------------~-->
HOW to SEE & RECORD EVERYTHING!
TINY Camera for Under $80 BUCKS! PRICE BREAKTHROUGH --> CLICK!
http://us.click.yahoo.com/w7toOC/.o6DAA/yigFAA/OIFolB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
Message Identifiers: , , , , , ,
Access the list online at: http://groups.yahoo.com/group/EDI-L
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
--
Michael C. Rawlins, Rawlins EC Consulting
www.rawlinsecconsulting.com
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
