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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-regrep message

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

Subject: RE: UDDI


So it seems like we are talking about 2 things: 1) Interoperability and 2)
mapping.  I think both are useful.  However, I think that in order to have
meaningful interoperability, we would have to map concepts from the two
specifications first.  Otherwise the data looses its meaning.  

The second point is that as far as I know there is no client API defined in
UDDI.  There are SOAP message formats.  SO for a UDDI client to access ebXML
RegRep, ebXML RegRep would have to implement a SOAP processor and also will
heva to respond to messages such as save_Business.  This save_Business is
interesteing because it has very broad scope and takes things such as
IdentifierBag and CategoryBag.  


Waqar Sadiq

-----Original Message-----
From: Krishna Sankar [mailto:ksankar@cisco.com]
Sent: Wednesday, November 22, 2000 3:12 PM
To: ebxml-regrep@lists.ebxml.org
Subject: RE: UDDI


	For the Vancouver POC, I have proposed and if it get approved, plan
to work
on an interoperable suit for UDDI and ebXML Registry. We have some interest
from Scott H of IBM as well.

	The idea is to demonstrate a two way interoperability - UDDI client
the ebXMl RegRep and an ebXML Registry client using the UDDI registry. This
exercise will bring out the synergies and differences between the two as

	my 2 yens !


-----Original Message-----
From: Matthew MacKenzie [mailto:matt@xmlglobal.com]
Sent: Wednesday, November 22, 2000 1:05 PM
To: Waqar Sadiq
Cc: 'ebxml-regrep@lists.ebxml.org'
Subject: Re:


We have been playing with UDDI since it became public, and just a few days
I suggested internally at XMLGlobal that bridging UDDI to ebXML would be
relatively trivial assuming that the UDDI registry is complete, which it is
(test.uddi.microsft.com).  All that would have to be done is to build an
sort of like
the ObjectQueryManager object that this group has specified, except into
be called UDDIQueryManager, and it's methods or actions would correspond to
UDDI find and store methods, such as find_business, store_Tmodel, etceteras.
This object would accept payload and invocation requests over ebXML TRP, and
dispatch the queries on the UDDI registry either remotely with SOAP, or
with a client library, and send the response back using TRP.

example query and response:

Content-Type: multipart/related; version=1.0; boundary=**bound**
Content-Length: 2286

Content-Type: application/vnd.eb+xml; version=1.0
Content-Description: ebxmlHeader
Content-ID: 0
Content-Length: 1466

<?xml version="1.0" encoding="UTF-8"?>
<ebXMLHeader MessageType="Normal"

Content-Type: application/xml; version=1.0
Content-Description: find_binding_Req
Content-ID: 1
Content-Length: 324

<find_binding serviceKey="uuid" generic="1.0" maxRows="99"

... and the response would have the uddi response XML body in the payload.
may make sense to modify the ObjectQueryManager to handle UDDI requests
internally to itself, I am more partial to simply bridging ebxml and UDDI
now.  The UDDI API is very straight forward and is very useful for discovery
trading partners and processes.  I saw a really neat demo at the UDDI
in Redmond of UDDI integration with a procurement app (Great Plains) that
good use of this API and registry, I very much hope that we can work the
UDDI efforts into ebXML, and would be willing to elaborate further toward



Waqar Sadiq wrote:

> Hi All,
> I know that their is an effort going on in the transport team to map ebXML
> transport layer to other protocols.  I feel that a similar effort in the
> RegRep team may be a worthwhile effort.  More specifically, I think that
> should try to map ebXML to UDDI.  I wouldn't be surprised if some members
> have already gone through that effort and in that case sharing of the
> results would be great.
> I realize that everybody is pretty busy with other more core issues.
> However, I personally feel that UDDI and ebXML will both survive alongside
> each other and a mapping will strengthen the two specifications.  It will
> also reveal conflicts between the two standards sooner than later.
> Currently both specifications are in the process of being defined and they
> can be changed to align with each other.  Later on, it will be difficult.
> While ebXML defines a UML based information model, UDDI does not define
> a model.  So if we decide to undertake this, I will be perfectly happy to
> construct and provide the UDDI model.
> Thanks,
> Waqar Sadiq

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

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC