UDDI vs ebXML

[Dick Raman <Dick.Raman@cab-edi.net>]

Dear All,

 

I have been studying the UDDI stuff and it appears to me that - apart from politics - we could very well work out that there is no conflict between UDDI and ebXML.

The UDDI stuff supports more the 'UDD' but not much the 'I', whereas ebXML -let's be fair- mostly ignored the 'Discovery' part...until the SJ meeting when we set up the TPAteam.

In fact we could say that we have concentrated in ebXML on the what Gartner calls the "post-contract phase", whereas UDDI concentrates on the 'pre-contract phase'.  I know that many in ebXML are of the opinion that the ideas of 'open-edi' should be part of the specs, but we have been able to come up with a radical approach to the post-contract phase - we have not come up with new stuff on the TP discovery part.

UDDI is here now, and it brings two important players that have been missing from ebXML: Microsoft and Ariba.  I think this is an opportunity for all to embrace the UDDI initiative (with all its marketing power) and to align it with ebXML.  We can now involve Microsoft and Ariba to come up with one comprehensive spec to cover both the pre- and post contract phase in B2B eCommerce, making UDDI non-proprietary and enhancing ebXML with something the world needs also.

Maybe we can welcome the UDDI people in the TPA team - maybe renaming it to UDD Team - and work together in Tokyo.

 

Dick Raman 

BEGIN:VCARD
VERSION:2.1
N:Raman;Dick;;Drs.
FN:Dick Raman CAB
NICKNAME:dickcab
ORG:TIE Holding NV
TITLE:President & CEO
NOTE:TIE - the first Dutch Internet company to go public on the Amsterdam Stock Exchanges
TEL;WORK;VOICE:+31-23-5689999
TEL;WORK;FAX:+31-23-5689988
ADR;WORK:;;POBox 538;HOOFDDORP;;2130 AM;The Netherlands
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:POBox 538=0D=0AHOOFDDORP 2130 AM=0D=0AThe Netherlands
URL:http://www.DickRaman.com
URL:http://www.TIE.nl
EMAIL;PREF;INTERNET:Dick.Raman@CAB-EDI.net
REV:20000909T071054Z
END:VCARD