One way to help remedy this perception might be to present on
"Registering Web Services in an ebXML Registry" at some of the Web
services conferences, such as Web Services One.
Some other things that might help are the Best Practices paper on
registering Web services in an ebXML Registry (currently in progress),
and perhaps in the future a high-level mapping between the 2 registry
architectures (such as "ebXML Registry Classification is *roughly*
equivalent to UDDI categoryBag", "ebXML Organization is *roughly*
equivalent to UDDI businessEntity", etc.)
Joe
Matthew MacKenzie wrote:
>
> Anne,
>
> You're right on. ebXML != Web Services, at least not general
> perception wise. I'd like to see that changed somewhat, ebXML
> messaging is web services based, and ebXML registry is a web service.
>
> On Thursday, Jan 30, 2003, at 07:40 America/Vancouver, Anne Thomas
> Manes wrote:
>
> >
> > I think RegRep's biggest issue is that it's so closely associated with
> > ebXML, and when most people think of Web services, they think of SOAP,
> > not
> > ebXML. Likewise, when they think of a Web services registry, they
> > think of
> > UDDI.
