In connection with Isidro's comments, there is a lot of work undergoing in EU that hardly one can imagine. There are/were EC funded projects covering both the research/technological and business dimension Take for example openXchange http://www.openxchange.org which is dealing with complete B2B process integration and make outstanding progress based on ebXML framework and LAURA - a project that we are co-ordinating - http://www.lauraproject.org which is seting up adaptive zones for B2B ecommerce in 4 *Least Favoured Regions* in EUrope - Greece (Epirus - Meccinia), Germany (Saxony Anhalt) and Bulgaria (South Central)- based on ebXML framework (gradually adotion of Messaging, Registry and so on) And you knwo what LFRs are? potentially no! We are dealing with chambers of Commerce and SMEs who hardly have the infrastructure or money to invest in proprietary B2Bsolutions and they are looking at such intitiatives with great interest. And we are not discussing for 10s of SMEs but nearly 100s per region from whom we are getting continuous feedback. I think that it doesn't gain only traction but more a snowball effect. And if ebXML proves to work and ease the tech/money pain that the SMEs facing, then for sure it is not a matter of EU vs US rather than SMEs vs Large Organisations ============================ Kostas Petropoulos 01 PLIROFORIKI S.A. http://www.01p.gr Tel.: +30 210 2594699 Fax: +30 210 2533161 =========================== -----Original Message----- From: Duane Nickull [mailto:duane@yellowdragonsoft.com] Sent: Friday, October 03, 2003 6:52 AM To: Farrukh Najmi Cc: Chiusano Joseph; ebxml-dev@lists.ebxml.org Subject: Re: ebXML: Will it Gain Traction in the US? > > >> >> My questions are: >> >> (1) Is this observation valid? > I have to agree with David (yes and no). Yellow Dragon Software is working on around 12 engagements with ebXMLK components in North America. We are not at liberty to discuss all of them however one is a full blown implementation of the Core Components Methodology within a Registry using the BCF (and UMM). We are harmonizing the CCTS, ebXML RIM, ISO TC 154 and 11179 data element models as well as taking others into account. If you deem ebXML implementatiuons to include all the components however, I would have to say no. BPSS execution is lacking. I think that will be better in 12-18 months. We also have no less than 15 or so others evaluating our Registry and messaging products and another 20 in the pipeline in early stages. Sufficient to say that there is enough ebXML work to support many vendors. > It is true that ebXML is seeing significant adoption in Europe and > Asia. This includes adoption in companies large and small, vertical > industries as well as entire governments. Yes. Again - Yellow Dragon is heavily involved in some of these. > It is also true that ebXML adoption in US is not as strong as Europe > and Asia. Hard to say. I can't judge the depth of implementation of "ebXML" but can say that certain components, most notably registry, messaging and CPA, are getting some very real traction. Once we are able to publish our work with CCTS, we expect to share that information and believe it will make it easier for others to follow suite. One barrier to adoption of the entire stack is a lack of API definition between components. For a business process to be able to be executed, it must talk to CPA's, messaging and some form of payload processing. Getting that nailed down is crucial. Other bits like the CAM type methodology is also important, regardless of whether it is manual of automatic. Using this list to share "best practices" will also get us further up the stack. Duane > > > However, ebXML adoption in US is not to shabby is one may think. GM > (automotive), Sabre (travel), HL7 (healthcare standard), RosettaNet > (supplychain), CDC (US Gov.) and many others are adopting ebXML. > >> >> (2) If so, what is the projected future direction of ebXML adoption here >> in the US? Will it increase, decrease, or remain the same? >> > It will increase significantly. And it will happen long before the > metric system is adopted ;-) > >> >> (3) If we were to consider the various "components" of ebXML (business >> processes, registry, collaboration, etc.) rather than ebXML as a >> framework, do any components in particular look more promising than >> others for adoption here in the US? >> >> > ebXML specs are designed to work stand-alone but work even better as a > cohesive stack. The strongest adoption I have seen is for ebXML > Messaging and ebXML Registry so far. > -- *************************************************** Yellow Dragon Software - http://www.yellowdragonsoft.com Web Services & ebXML Messaging / Registry Downloads UN/CEFACT eBusiness Architecture/ ebXMl Technical Architecture Phone: +1 (604) 738-1051 - Canada: Pacific Standard Time Direct: +1 (604) 726-3329
<<attachment: winmail.dat>>