Agreement Formation Description Documents v0_2.doc Details

Document Details     TC Member Document View
Title Agreement Formation Descriptor Document
Name * Agreement Formation Descriptor Document (390K)
Description V0.2 Updated C.1 (and made it consistent with C.2); minor textual improvements and enhancements. Removed some redundancy from the example in C.2 and added more introductory text to annex C.

//

The concept Agreement Formation Descriptor Document (AFDD) is a proposal for a document that describes how business partners establish business agreement documents.

It recognizes:
- multiple types of agreement documents, such as XML schemas, WSDLs and ebXML Collaboration Protocol Agreements.
- multiple ways of establishing those documents, including transformation of templates with particular variable parts (using values provided by business partners), intersection of ebXML Collaboration Protocol Profile documents, or combinations.
- the need to have multiple agreement documents, such as a CPA or WSDL and an XML Schema referenced in that CPA or WSDL.

The attached ZIP file provides
- an XML schema for AFDD documents
- a compiler that generates XSLT stylesheets to perform document transformations (XSLT and Python driver)
- a script to evaluate the generated XSLT scripts (Python driver)

AFDD documents can specify CPP intersection, but the compiler does not support this formation method.

Sample documents are included:
- bias.afdd: simple CPA template, where one partner acts as server (setting start, end and CPA id) and the other provides communication details.
- cppintersection.afdd: CPA formed on the basis of two supplied CPPs
- multidoc.afdd: two partners agree on a specialized business document schema (a UBL invoice where the optional "OrderReference" element has been made required) and a CPA that references this schema.
- multiparty.afdd: three business partners form two CPAs based on three CPPs.
- secured.afdd: real-life, complex CPA using XML digital signatures, XML encryption and TLS authentication, reliable messaging. Two partner need to supply four certificates each, their party identification parameters. Optionally, reliable messaging parameters can be adjusted.
- ubl.afdd: the XSD specialization also used in multidoc.afdd
- wsdl.afdd: an organization requires a business partner to implement a particular web service, where only the SOAP address is variable.
Group OASIS ebXML Collaboration Protocol Profile and Agreement (CPPA) TC
Folder working_drafts
Submitter Mr. Pim van der Eijk
Date Submitted Sunday, 28 December 2008 04:08am
Document State Draft (A preliminary unapproved sketch, outline, or version.)
Access This document is visible to OASIS ebXML Collaboration Protocol Profile and Agreement (CPPA) TC and shared with:
  • OASIS Open (General Membership)
  • General Public

Document Revisions
Name # State Submitter Date Action
2
Draft
Mr. Pim van der Eijk
2008-12-28
This doc
1
Draft
Mr. Pim van der Eijk
2008-12-23
0
Draft
Mr. Pim van der Eijk
2008-03-18