Re: [regrep] UDDI as the registry for ebXML components: Typo?

["Chiusano Joseph" <chiusano_joseph@bah.com>]

<Quote1>
It is not a typo. It's meant to say that you probably want to use only
one registry for both UDDI and ebXML. 
</Quote1>

But that's not what the following statement says:

"This introduces significant concerns of cost and manageability, because
ebXML and Web services impose separate infrastructure requirements and
platform components."

To me, that statement says that one cannot use ebXML for Web services,
because the two require separate infrastructure requirements and
platform components. That is definitely not the case. My concern is that
others may read this statement and interpret it the same way that I did,
which does nothing for raising awareness of ebXML Registry and Web
services (in fact, it deters it).

<Quote2>
Likewise the ebXML team might want to produce a similar technical note
that explains how you can use regrep to register WSDL services.
</Quote2>

Already done - please see:

http://xml.coverpages.org/RegisteringWebServices.pdf
(dated 12 March 2003)

Joe

Anne Thomas Manes wrote:
> 
> It is not a typo. It's meant to say that you probably want to use only one
> registry for both UDDI and ebXML. This technical note explains how you can
> use UDDI to register ebXML services. Likewise the ebXML team might want to
> produce a similar technical note that explains how you can use regrep to
> register WSDL services.
> 
> Anne
> 
> ----- Original Message -----
> From: "Chiusano Joseph" <chiusano_joseph@bah.com>
> To: <regrep@lists.oasis-open.org>
> Sent: Tuesday, July 01, 2003 4:07 PM
> Subject: [regrep] UDDI as the registry for ebXML components: Typo?
> 
> > In the UDDI Technical Note "UDDI as the registry for ebXML components"
> > [1], the Problem statement (p.3) states:
> >
> > "This introduces significant concerns of cost and manageability, because
> > ebXML and Web services impose separate infrastructure requirements and
> > platform components."
> >
> > Is this entirely accurate, given that one can register and maintain Web
> > services in an ebXML Registry? The entire Problem statement is
> > reproduced below. I wonder if this is a typo.
> >
> > Joe
> >
> > 1.1 Problem statement
> > Multiple consortia have initiated pilot projects using the ebXML
> > framework for business-to-business transactions, while corporations have
> > also begun adopting ebXML technologies for internal use. At the same
> > time Web service technologies, which have significant momentum due to
> > unprecedented industry support, are also being rolled out. This
> > introduces significant concerns of cost and manageability, because ebXML
> > and Web services impose separate infrastructure requirements and
> > platform components.
> >
> > As a universal technology for publication and discovery of service
> > metadata, UDDI allows the bridging of the two infrastructures by
> > accommodating metadata registrations for Web services as well as ebXML
> > framework components, enabling interoperability among trading partners
> > using ebXML or Web services. However, a prescribed methodology of
> > modeling services and components which are conformant to ebXML
> > specifications is required to make interoperable solutions possible.
> >
> > [1]
> >
> http://www.oasis-open.org/committees/uddi-spec/doc/draft/uddi-spec-tc-tn-udd
> i-ebxml-20030508.htm
> 
> ----------------------------------------------------------------------------
> ----
> 
> > You may leave a Technical Committee at any time by visiting
> http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.
> php
begin:vcard 
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@bah.com
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard