Posted at the request of the original author.  Please forgive the 
duplicate if you've already seen this.

-------- Original Message --------
From: - Wed Apr 17 16:32:28 2002
X-UIDL: 57Y"!OoF"!7BI"!2~S"!
X-Mozilla-Status: 0013
X-Mozilla-Status2: 00000000
Return-Path: <[EMAIL PROTECTED]>
Received: from c011.snv.cp.net (c011-mx001.c011.snv.cp.net 
[209.228.34.207]) by feenix.metronet.com (8.10.1/8.10.1) with SMTP id 
g3HIa3q08349 for <[EMAIL PROTECTED]>; Wed, 17 Apr 2002 13:36:03 -0500 
(CDT)
Received: (cpmta 900 invoked from network); 17 Apr 2002 11:37:20 -0700
Delivered-To: [EMAIL PROTECTED]
Received: (cpmta 898 invoked from network); 17 Apr 2002 11:37:20 -0700
Delivered-To: [EMAIL PROTECTED]
Received: (cpmta 895 invoked from network); 17 Apr 2002 11:37:19 -0700
Received: from 63.65.132.35 (HELO karloff.boston.amer.iona.com) by 
smtp.c011.snv.cp.net (209.228.34.207) with SMTP; 17 Apr 2002 11:37:19 -0700
X-Received: 17 Apr 2002 18:37:19 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 
OAA11685; Wed, 17 Apr 2002 14:37:14 -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 
Melanie McCarthy, GM
Date: Wed, 17 Apr 2002 11:37:13 -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+yB30wAm9HoA
From: "Loos, Claus" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>, "edi-l" <[EMAIL PROTECTED]>, 
"ebxml-dev" <[EMAIL PROTECTED]>, "XML/EDI" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by 
feenix.metronet.com id g3HIa3q08349
X-UIDL: 57Y"!OoF"!7BI"!2~S"!
Status: U



Many things are easier said than done and I am learning that some of the most 
challenging concepts are SIMPLE, REUSEABLE and CONSISTENT- particularly when there are 
preconceptions on what/ how these term apply.

To reminisce down standards "memory lane" the EDI world did attempt to meet the needs 
of all within a defined business document.  Though I would not have called it the 
"kitchen sink" approach, I agree that the problem was that the definitions were, at 
times, unclean and riddled with semantics that often caused problems with reuse.  

Then came XML, a new syntax, which also had the potential of exchanging trading 
partner messaging.  But more importantly it created the awareness that as technology 
continues to evolve there will most likely be other syntaxes.  So the value 
proposition created by Core Components, created independently from syntax, grew 
exponentially.

EbXML began by stating that they would deliver templates (not core components) that if 
implemented, would create an ideal solution.  The issue that we are now facing is the 
transition from today's messaging (regardless of the syntax) to the envisioned state.  
The fact that the road is difficult does not imply that the original concepts should 
be discarded, or rushed, for the sake of speed.  If we take either of those steps, the 
result will be just another vocabulary of terms.  

Where I disagree with Mike Rawlins article is the supposition that the work is moving 
slowly and/or will ultimately be discarded.  When I attended the March EWG meeting in 
Barcelona I saw the draft results of six different global organizations' work with 
ebXML Business Processes and/or Core Components as well as progressing the work that I 
chair on eBTWG Core Components Supplemental Documents (CCSD).  I also have heard about 
many other similar efforts where the participants are very positive about the results. 
  But I agree everyone is longing for the Catalog of Core Components (I think there 
are nights that I lust for it!).  The hesitation has been driven by the need to do 
things correctly, and only through multiple trials will there be confidence in exactly 
what and how should information be presented.  For example, I am as concerned that the 
Core Components will be so "generic" that there will not be enough substance to be of 
value to implementers or not enough definition to insure consistency throughout the 
process.  But we have one opportunity to publish the information correctly, because 
this information is the foundation that everything  else will be built upon.  So the 
real solution is premium participation/involvement to assist in expediting this work.  
The detailed discussions are thought provoking and require both innovative thinkers as 
well as detailed executioners to meld the brightest and best concepts from both worlds 
of thought.  So I would implore additional participation in all of the continuing 
work, though the following website www.ebtwg.org.  

In conclusion, I believe UN/CEFACT has an interim role to lead all us of to the 
ultimate simple, reusable low cost solution that ebXML promised to deliver.  It seems 
like we are transitioning through a curve where the last steps are the steepest and 
most difficult to accomplish.  It is similar to what I imagine climbing Mt. Everest 
would be, the last day of the climb in the toughest.  But when you arrive at the top, 
there are two results: everyone knows that you have made it and on a personal level 
there is a feeling of tremendous accomplishment.  Each of you has the opportunity to 
join the expedition in the final trench to the top!

Melanie McCarthy, GM

____________________________________

End 2 Anywhere

Claus Loos
Pre-Sales Consultant
Western Region

IONA Technologies Inc.
City Center Bellevue
500 108th Ave NE, Suite 800
Bellevue, WA 98004

Cell:     (425) 785-4462
Phone: (425) 646-7358
Fax:     (425) 646-7359
e-mail:  [EMAIL PROTECTED]

http://www.iona.com
____________________________________

Expose Your Web Services! 
* IONA Dream Warrior Challenge. Take the Challenge. Explore distant worlds. Defend 
your stronghold and challenge your peers.
* Win cool prizes. Oh, yeah, and get hands-on experience building, consuming and 
exposing Web Services.
* (Well, you've got to have some excuse for playing on company time...!)
http://portals.devx.com/iona/dreamwarrior


 -----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


Reply via email to