Overview BPSS Contract Formation Pattern E-Commerce Patterns 1.0 ebXML Negotiation Subteam F2F January 30, 2002 Heiko Ludwig

Objective Facilitate formation of a legally binding contract –Define the required elements of BPSS –Define constraints on the use of those BPSS elements –Define a sample process –Illustrate use for CPA negotiation

Elements and Requirement for Legally Enforceable Contracts Basic (explicit) messages –Offer –Acceptance Semantics in document content, not envelope attribute. Business Transaction –Offer must be sent within requesting business activity. –Acceptance must be part of responding business activity. Leads to transaction success –Rejection must be part of responding business activity. Leads to transaction failure. Also by time out. –Counter offer is rejection + new offer Use of business signal parameters, e.g., isLegallyBinding

Proposed Simple Process Query / Response (seek information) Proposal (nonbinding ) Offer (binding) Contract Ready to deal Reject inquiry Seek more info Ready to deal Reject proposal Time out Ready to talk Counterproposals (but in a new transaction) Rejection Time out Counteroffers (but in a new transaction) Acceptance (binding) Binding Terminate

Use for CPA Negotiation Requirements and Specification Requirements –Potentially update of requirement document with respect to legal bindings. Starting point for specification proposal –Good initial process –Mapping of CPA template and CPP based interaction to the proposed process.