RE: [uddi-spec] ebXML TN question

["Daniel Feygin" <feygin@unitspace.com>]

Paul,

The author's intentions in drafting the ebXML TN, if I correctly read them,
were to show how supported implementations of UDDI can be leveraged to
advance the adoption of ebXML-based B2B interoperability.  Therefore, the
TN's assumption is that no suitable ebXML reg/rep implementation is
available and it is not useful to publish ebRS endpoints to UDDI.  The TN
was reviewed by the ebXML community, which did not raise this issue in their
input.

The difference between ebRS interfaces and other ebXML framework artifacts I
see is in ebRS being very much a type of artifact (a Web service) that UDDI
is really made to manage, unlike the registrations of other ebXML framework
artifacts.  That makes it rather straightforward to publish ebRS endpoints
to a UDDI registry, especially since UN/CEFACT and OASIS endorsed a Sun/IBM
white paper [http://www.ebxml.org/specs/rrUDDI.pdf] on this very topic back
in 2001.

If there is an omission with respect to the use case you are referring to,
it is one on the part of the OASIS ebXML Reg/Rep TC, which has not pursued
the publication of their well-known tModels to the UBR.

In the long term, I look forward to the outcome of the work being done on
ebSOA, which I expect will further bind ebXML to Web services technologies.

Best regards,
Daniel


-----Original Message-----
From: Paul Denning [mailto:pauld@mitre.org] 
Sent: Thursday, May 13, 2004 2:36 PM
To: uddi-spec@lists.oasis-open.org
Subject: [uddi-spec] ebXML TN question

I was looking at the ebXML TN [1] and was wondering why the valid keyValues 
for the ebxml-org:specifications taxonomy only includes CPPA, MS, and BPSS.

I would think that it would also include RS for Registry Service.

Looking at ebRS 2.0 [2], Figure 4, it defines two bindings to a registry 
service: a SOAP interface and an ebXML Messaging interface.

I would like to use UDDI to discover ebXML Registries, but the TN does not 
tell me how to register them in UDDI.
The TN only addresses publishing CPPA, MS, and BPSS

There is WSDL for the SOAP binding [4] to an ebXML Registry [3], but I 
found no wsdlSpec tModel in UBR whose key could be used in a find_binding 
tModelBag to discover ebXML registries.

Did the TN intentionally omit this use case?

It would be nice to use UDDI to discover ebXML registries, then use the 
ebXML registry to find CPPA, MS, and BPSS.  It seems like the GIS industry 
is leaning toward ebXML Registries [5] for publishing of GIS services (WMS, 
WFS, ...).

[1] 
http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-uddi-e
bxml-20040219.htm
[2] http://www.oasis-open.org/committees/regrep/documents/2.0/specs/ebrs.pdf
[3] 
http://www.oasis-open.org/committees/regrep/documents/2.0/services/Registry.
wsdl
[4] 
http://www.oasis-open.org/committees/regrep/documents/2.0/services/RegistryS
OAPBinding.wsdl
[5] http://www.ionicsoft.com/products/main_catalog.jsp

Paul



To unsubscribe from this mailing list (and be removed from the roster of the
OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members/leave_workgro
up.php.