OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: ebxml and uddi

At 
	http://www.oasis-open.org/committees/uddi-spec/doc/tns.htm

along with other great TN's, you will find a nice note entitled:
	
	"UDDI as the registry for ebXML Components"

"This UDDI Spec Technical Committee Technical Note (TN) provides technical
guidance on how to use UDDI registries within the ebXML framework of B2B
services. Specifically, it addresses the issues related to enabling
automated discovery of ebXML framework components, such as Collaboration
Protocol Profile and Business Process Specification Schema, using UDDI.

By adopting the technical guidance of this TN, users will enable trading
partners and their Web services and ebXML infrastructures to interact using
UDDI as a common registry."

Joel David Munter
   Program Manager, PSM Technology Office
Intel® Solution Services 
   Telephone: 480.552.3076
   Mobile: 602.790.0924
   eMail: joel.d.munter@intel.com
   URL: http://www.intel.com/go/intelsolutionservices


-----Original Message-----
From: Bryan Rasmussen [mailto:brs@itst.dk] 
Sent: Wednesday, July 14, 2004 12:18 AM
To: ebxml-dev@lists.ebxml.org
Subject: ebxml and uddi


HI

Going through the enormous amounts of documentation on these technologies
there is often discussion of them as being complementary, does anyone have
any case studies of real world implementation that show them actually
complementing each other (I've seen the notes on finding ebxml services via
uddi etc.)

Also it seems that ebXML can do everything that UDDI can and more (except be
a lot easier to implement than ebXML), is this the case? Is this just an
accidental effect of trying to provide for all business processes? I'm
asking because it was requested that I do some checking on the possible
future  feasibility of moving our UDDI repository to an ebXML one, from my
viewpoint and tastes this does not seem to be a worthwhile thing to do (I
would almost always rather use the smaller technology designed for a
specific domain, rather than the more general that accidentally covers the
domain). It seems more reasonable to build an ebXML repository for
particular business processes and have those findable via UDDI. 



The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> The
list archives are at http://lists.ebxml.org/archives/ebxml-dev/
To subscribe or unsubscribe from this list use the subscription manager: 
<http://www.oasis-open.org/mlmanage/>


smime.p7s



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]