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

Bryan Rasmussen wrote:
> >> Also it seems that ebXML can do everything that UDDI can and more
> be
> >> a lot easier to implement than ebXML), is this the case?
> >Not sure about which is easier to implement (would depend on the
> >product, of course) - but in essence, one may consider ebXML Registry
> >be a "superset" of UDDI in ways that are described in [1].
> well actually my comment was sort of an alice in wonderland type of
> because UDDI can be easier to implement than ebXML, but ebXML can never
> easier to implement than ebXML, as well as, of course, referring to my
> opinion that if I had my choice of having to implement one of these
things I
> would go for the UDDI.
> > More specifically, do you need to store (vs. simply register)
> >artifacts in a repository?
> My opinion is that for what we have which we are currently providing an
> registry we will never need to store artifacts. Depending on what we
> as artifacts :)
> However I am of the opinion that it might be very worthwhile for us to
> an ebXML repository for other projects.
> > Also, how does the product landscape look for
> >UDDI? How does it look for ebXML Registry? These are only some of the
> >factors involved in such a decision.
> Though I'm not a big afficionado of UDDI, or ebXML either, from outside
> it looks like UDDI is currently more used, 

That is my experience as well - but I am speaking only from my
experience, without conducting a formal study.

> outside of large companies that
> have moved edi structures to ebXML, the way you phrased that though,
> me to expect that you thought I would have another opinion. Is this so?
> does the product landscape look to you.

That is a complex question that involves not just the number of products
available, but their quality, how they meet one's specific requirements,
the "survivability" of the vendors, etc. In general, from my experience,
I have seen Systinet as the most-mentioned UDDI product, while on the
ebXML side, Adobe purchased ebXML software vendor Yellow Dragon Sofware
(YGS) in late 2003 (and there are no public details yet to my knowledge
as to how Adobe will position this product in the future), and there is
the ebxmlrr open source ebXML Registry implementation that I referenced

Kind Regards,
Joe Chiusano
Booz | Allen | Hamilton
Strategy and Technology Consultants to the World
> >There is an open-source ebXML Registry SourceForge project called
> >"ebxmlrr" that you can find at [3]. Farrukh Najmi of Sun Microsystems
> >the leader for this project, and he is on this listserv.
> Yeah, I've seen that. I sort of dread downloading and installing it,
cause I
> can just see if I ever get it to work that then I would be in charge of
> :)

Kind Regards,
Joseph Chiusano
Booz | Allen | Hamilton

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: 

<<attachment: winmail.dat>>

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