[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Fwd: Re: [ebxml-cppa-negot] Re: Negotiation message types,business documents and signing]
This is the issue raised or clarified by Hima related to Negotiation. You can only have one document part for requests. I will make sure this is properly represented. Hima, if you have any more to add to this, could you please advise? Thanks. -------- Original Message -------- Subject: Re: [ebxml-cppa-negot] Re: Negotiation message types, business documents and signing Date: Fri, 17 Oct 2003 13:29:15 -0700 From: Himagiri.Mukkamala@sybase.com To: Martin Sachs <msachs@cyclonecommerce.com> CC: ebxml-cppa-negot <ebxml-cppa-negot@lists.oasis-open.org>, "Vetter, Michael" <Michael.Vetter@iao.fhg.de> >In section 12.1.7 there are CPA_Final_Response_Doc and >CPA_Final_Response_Doc_Signed documents. Why is there only a >CPA_Final_Doc and no "CPA_Final_Doc_Signed"? > MWS: I have asked our expert on the BPSS instance to consider the above points. <Hima> Assumption is CPA_Final_Doc may have a signature embedded by the party sending the Final Accepted CPA. Based on description in the specifcation, If two parties have agreed that they'd sign the CPA, then the signature will be embedded in the Final CPA Document. Reason I did'nt have a CPA_Final_Doc_Signed for the sending part is cause there can be only one documentpart for requests and there can be multiple for responses. Hence, possible options are shown for the RespondingBusinessActivity "CPA_Final_Doc", CPA_Final_Response_Doc_Signed, CPA_Final_Response_Reject_Doc" and cannot be shown for RequestingBusinessActivity. Or else I'd have to create a new BusinessTransaction which sends the "CPA_Final_DOc_Signed" with a transition from "CPA Counter Offer 1" or "CPA Counter Offer 2" if the two conditions were met <Transition fromBusinessState="CPA Counter Offer 1 BTA" toBusinessState="CPA Final BTA Init Responder"> <ConditionExpression expressionLanguage="DocumentEnvelopeLanguage" expression="CPA Accept Offer Doc"/> </Transition> and a new ConditionExpression which only indicates that they have agreed that they'd sign the CPA. This is not enforceable with bpss specification right now. Side note, all the different Business Documents may end up using the same schema. These are here just for clarity in the interactions as shown in bpss.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]