ebXML Architecture Registries/ Repositories Core Components Business Documents CP Agreement Design Time Business Process Collaboration Protocol Profile Transport Package Business Service Interface Business Services/App’s Runtime Business Service Interface Business Services/App’s XML based: XMI, Specification Schema, Document Schemas Register & Discover

Business Transaction Binary Collaboration Business Document Multi Party Collaboration Overview: ebXML SpecificationSchema Choreography Sequence Rules Role Business Scenario For an industry/geography Interaction between Two partners Legal/Commercial Transaction

Business Transaction Requesting Activity Responding Activity Request Document Response Document SuccessFailure Unit of Work Non- Repudi ation Time-Outs Legally Binding (Signed)Receipt Acceptance (Signed)Receipt

BusinessTransaction

BinaryCollaboration

MultiPartyCollaboration

What to override / When is it ‘New’ Skip/Insert BusinessTransactions Override transition or transition rules GuaranteedDelivery Transaction Documents Signals: Receipt/Acceptance/+TimeTo Time-Outs – Collaboration, BTActivity, DocumentSecurity: Confidential/Tamperproof/Auntenticated

Substitution

Other Issues Explicit CPP –One-sided only (BPSS is two- or multi-sided) –Only the supported roles Explicit CPA –True intersection of two CPP’s (BPSS wise) –Functional CPA separate from technical CPA Role linking –Link to MultiParty Service/Action linking Namespaces

Futures Relation to WebServices standards Put the Lawyers out of work – Electronic Judge The whole collaboration stack –REA – Lifecycle of contractual relationships –Collaboration State Management or Monitoring MultiParty