[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [regrep] Clarification of 3 implementations requirement
David, You're speaking of CommerceOne Conductor. According to [1], the registry that is bundled with it is a "UDDI-like" registry, not an ebXML Registry: "The Registry adheres to UDDI standards at the root level and accommodates more sophisticated requirements through extensions that address organization data, user data, rights responsibilities, transformational data, process choreography, and version reconciliation" Joe [1] http://www.commerceone.com/solutions/conductor_reg.html David RR Webber - XML ebusiness wrote: > > Team, > > I've just remembered that CommerceOne are shipping > an 'ebXML Registry' component with their latest suite. > > I've pretty sure its not unbundled - but it definately > counts as an implementation - not sure what V.x.xx > they are supporting however. > > I think 'implementation' is a pretty loose term. It > would be hard to be really tough on this as there's > too many permitations possible. So if a company > is prepared to step-up to the plate and say 'Yes', > I think you have to go with that - provided as a TC > you are satisfied that their offering is non-trivial, > viable, and being actively promoted and supported. > > DW.
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]