Overview BPSS Contract Formation Pattern ECommerce Patterns 1'0 ebXML Negotiation Subteam F2F Januar

1
OverviewBPSS Contract Formation
PatternE-Commerce Patterns 1.0ebXML
Negotiation Subteam F2FJanuary 30, 2002

• Heiko Ludwig

2
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

3
Elements and Requirement forLegally 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

4
Proposed Simple Process
Time out
Query / Response (seek information)
Terminate
Seek more info
Reject inquiry
Ready to talk
Proposal (nonbinding)
Time out
Ready to deal
Terminate
Counterproposals (but in a new transaction)
Reject proposal
Ready to deal
Time out
Offer (binding)
Terminate
Counteroffers (but in a new transaction)
Rejection
Acceptance (binding)
Binding
Contract
5
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.