RE: [ebxml-cppa] Groups - Agreement Formation Descriptor Document (Agreement Formation Description Documents v0_1.doc) uploaded

["Pim van der Eijk" <pvde@sonnenglanz.net>]

Here is a first draft of a proper technical specification of AFDD. 
Apologies it took ages to finally get round to writing this up. 
A predecessor format of AFDD is being used to generate all CPAs (test and
production) in several ebXML deployments. 

We need to discuss this in the context of transition to ebCore also. 

Season's greetings to everyone ! 

Pim  

-----Original Message-----
From: pvde@sonnenglanz.net [mailto:pvde@sonnenglanz.net] 
Sent: 23 December 2008 19:27
To: ebxml-cppa@lists.oasis-open.org
Subject: [ebxml-cppa] Groups - Agreement Formation Descriptor Document
(Agreement Formation Description Documents v0_1.doc) uploaded

The document revision named Agreement Formation Descriptor Document
(Agreement Formation Description Documents v0_1.doc) has been submitted by
Mr. Pim van der Eijk to the OASIS ebXML Collaboration Protocol Profile and
Agreement (CPPA) TC document repository.  This document is revision #1 of
CPAdist.zip.

Document Description:
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.

View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=30474

Download Document:  
http://www.oasis-open.org/committees/download.php/30474/Agreement%20Formatio
n%20Description%20Documents%20v0_1.doc

Revision:
This document is revision #1 of CPAdist.zip.  The document details page
referenced above will show the complete revision history.


PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy and paste
the entire link address into the address field of your web browser.

-OASIS Open Administration