[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [ebxml-cppa] CPAId; negotiation
The To and From parties must each understand what value of CPAId will be understood by the From party. As defined in the MS specification, the CPAId is a single value that must be understood by both parties. I suggest that: The CPAId must be an item of negotiation since the two parties must agree on a value that both understand. At least for convenience, we should add to the top-level element of the CPA a child element or an attribute that will be filled with the CPAId. Please note that the CPAId as sent in the message header is independent of any identifier metadata associated with storing a CPA or CPA template in a registry. The CPAId element is not needed in the CPP. However for convenience in the CPA composition process, it might be helpful to have a CPAId element or attribute in the CPP with a dummy value. There was previously (Vienna or earlier) discussion about the need for a CPP identifier in the CPP. At that time it was (I think) agreed that a CPP Id is an item of registry metadata and can only be assigned when the CPP is placed in the registry. Since the CPP may be signed by the creater, the CPP Id cannot be placed in the CPP after it is signed. Therefore, there is no CPPId element in the CPP. Regards, Marty ************************************************************************************* Martin W. Sachs IBM T. J. Watson Research Center P. O. B. 704 Yorktown Hts, NY 10598 914-784-7287; IBM tie line 863-7287 Notes address: Martin W Sachs/Watson/IBM Internet address: mwsachs @ us.ibm.com *************************************************************************************
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC