Subject: RE: Resubmission of Distributed Registry Approaches.ppt
Hmmmmmmm, I think you mean TP which defines ebXML's CPP purpose ! Anyway I did look at : ebXML Registry Services, ebXML Registry Project Team, Working Draft 3/19/2001, Version 0.88 5 and it seemed to me their discussions on the CPP was jiving with the TP teams description/prescription as it's intended use. You say "it will be ..." does that mean you haven't recently checked the documents or think was put in the documents ? Anyway to be clear for the record, the CPP I'm talking about is a Collaboration-Protocol Profile and I'm looking at what is defined in the TP team's work today (hey, the document title is a dead giveaway !!!) : Collaboration-Protocol Profile and Agreement Specification (Version 0.93), ebXML Trading-Partners Team, 03/19/01 5:38 PM. I think we've probably beaten this up enough, and I propose we just stick to what / how ebXML is formally defining in it's soon to be public documentation as the CPP; so we're helping ensure later compatability as people not here start building their CPP's and registries. Thanks DMcSW > David, > > It will be in the Registry docs, not the TRP ones. > > When you look at a CPP - it is evident that the 'party' can > in fact be the registry itself - acting as a service provider. > > Then the registry queries themselves are the actions > that can be supported - GetRegistryContent() et al... > > Somewhere in the email archives should be the ones > Farrukh did for Tokyo - I recall each participant had to > create their own and send them to Dale.... > > Thanks, DrrW. >
Powered by
eList eXpress LLC