[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fwd: business documents and signing
Thread-Topic: business documents and signing
Thread-Index: AcOU7Y5lxUffOWdzRO6wvksVvmL7HwOBrgug
X-XWall-Bayes: 20
From: "Vetter, Michael" <Michael.Vetter@iao.fhg.de>
To: "Himagiri.Mukkamala@sybase.com" <Himagiri.Mukkamala@sybase.com>
Cc: Martin Sachs <msachs@cyclonecommerce.com> ,
"dmoberg@cyclonecommerce.com" <dmoberg@cyclonecommerce.com>
Subject: business documents and signing
Date: Tue, 4 Nov 2003 10:09:05 -0700
X-Assembled-By: XWall v3.28
X-OriginalArrivalTime: 04 Nov 2003 17:09:13.0565 (UTC) FILETIME=[5EFAB8D0:01C3A2F6]
Dear Himagiri
I understand your decision.
Have you talked to the BPSS team whether it would be possible to allow several document envelopes in a request?
I think that this makes sense and is an elegant and consistent solution.
regards
Michael
- -----Ursprüngliche Nachricht-----
- Von: Himagiri.Mukkamala@sybase.com [mailto:Himagiri.Mukkamala@sybase.com]
- Gesendet: Freitag, 17. Oktober 2003 22:29
- An: Martin Sachs
- Cc: ebxml-cppa-negot; Vetter, Michael
- Betreff: Re: [ebxml-cppa-negot] Re: Negotiation message types, business documents and signing
- >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.
- </Hima>
- >I am looking forward to your new specification draft.
- >
- >Best regards
- >
- >Michael Vetter
- >________________________________________________________________________
- >____
- >
- > Dipl.-Inform. Michael Vetter
- > CC Electronic Business Integration
- > Fraunhofer IAO (Institut fuer Arbeitswirtschaft und
- >Organisation)
- > mail: Nobelstrasse 12, D-70569 Stuttgart, Germany
- > phone: +49 (0) 711 970 2324
- > fax: +49 (0) 711 970 5111
- > email: Michael.Vetter@iao.fhg.de
- > www: www.ebi.iao.fraunhofer.de
- >________________________________________________________________________
- >____
- *************************************
- Martin Sachs
- standards architect
- Cyclone Commerce
- msachs@cyclonecommerce.com
- To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/ebxml-cppa-negot/members/leave_workgroup.php.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]