ebxml-msg — archive

[System]

Marty (and also Ian Jones) You said ... >>>The solution of piling additional information into the message header to make up for the lack of a CPA should not be considered acceptable.<<< The ebXML messaging group has **agreed** that we want to separate the ebXML Messaging and CPPA specs so that they can be implemented independently or together (Ian, please correct me if I am wrong). I like others believe that CPAs can offer many benefits, particularly if you are doing individual point-to-point communications which **need** to be different in every case. Using a CPA for these situations will make it much easier to set up these types of links. However I think there is another use case where communities of users agree to exchange information in largely the same (or a few different) ways. This means that separate agreements for each link are not necessary and in fact create a barrier as it becomes a pre-requiste to negotiate re-negotiate the CPA before a new type of message can be sent that supports a new busines process. The alternative approach is to register your public key certificate, and the URLs associated with sending or receiving your messages with a particular service and action. For many businesses the same URL for all services and actions will be OK. What I am trying to do is make sure that ebXML works, as the group has agreed, either with a CPA or without. To this end I am making, what I hope are constructive suggestions on how to fix problems where they exist. So come on Marty !! make a suggestion on how to solve the problems we are trying to fix without saying ... "you need a CPA" !! Best wishes David