Agreement Formation Descriptor Documents

1
Agreement Formation Descriptor Documents

• Pim van der Eijk

2
Agenda

• Background
• CPA formation
• CPA template instantiation
• Generalization to other agreement documents and
  formation methods
• Overview of AFDD
• Status
• Plans

3
Background

• CPP/A mentions two methods of forming a CPA
• CPP intersection
• Template instantiation
• CPP/A Negotiation SC distinguishes two stages
• Composing a draft CPA
• Negotiating a final CPA using an offer/counter
  offer process

4
CPA formation

• CPP intersection
• Is defined informally in appendix E of CPA 2.0
• Few tools available, and only limited
  functionality ?
• Template instantiation
• Commonly used in ebXML deployments
• Fits the common practice of profiling ebMS,
  profiles result in predictable CPA content
• High degree of automation possible for take it
  or leave it proposals
• Some support in products, but not in a
  standardized way

5
Initial goals

• Formalize a simple (candidate standard) notation
  to define CPA formation based on templates plus
  supplied parameters
• Semantics defined by compilation to XSLT
• Stylesheet that transform the template using
  supplied parameters
• Each partner supplies a specific set of
  parameters, passed as parameters to XSLT engine

6
Extension multiple agreement document types

• Business document schemas
• XML schema, RELAX NG
• Code lists
• Service agreements
• WSDL, CPA
• Versions
• Combinations
• E.g. XSD and Schematron for business rules
• Two CPAs in a three-party collaboration

7
Extension multiple agreement methods

• Instantiating a template with variables
• Intersecting two CPPs into a CPA
• WS-Policy intersection algorithm
• CAM templates plus context parameters
• SCA Policy

8
Generalized goals

• Simple language to define
• Agreement documents to be created
• Participating partners (roles)
• Parameters each supplies
• Method used to establish agreements
• Template instantiation as one such method
• Special case XML template instantiation
• Links document to a set of ltParameter, XPathgt
  bindings

9
Sample syntax

• lt?xml version"1.0" encoding"UTF-8"?gt
• ltafddAgreementFormationDescriptorDocument
  xmlnsxsi"http//www.w3.org/2001/XMLSchema-instan
  ce"
• xmlnsafdd"http//www.oasis-open.org/committe
  es/ebxml-cppa/schema/afdd.xsd"
• xsischemaLocation"http//www.oasis-open.org/
  committees/ebxml-cppa/schema/afdd.xsd afdd.xsd
• version"0.2name"wsdl"gt
• ltafddNamespaceSetsgt
• ltafddNamespaceSet name"wsdl11"gt
• ltafddns prefix"soap"
  uri"http//schemas.xmlsoap.org/wsdl/soap/"/gt
• ltafddns prefix"wsdl"
  uri"http//schemas.xmlsoap.org/wsdl/"/gt
• lt/afddNamespaceSetgt
• lt/afddNamespaceSetsgt
• ltafddDocumentsgt
• ltafddXMLDocument id"weather"
  type"wsdl11"gt
• ltafddDocumentTransformation
  patternConflictsAllowed"false"gt
• ltafddBinding pattern"soapaddres
  s" param"SoapAddress" method"attribute"
  attribute"location"/gt
• ltafddTemplate href"weather.wsdl"
  /gt
• lt/afddDocumentTransformationgt

10
Expected input

• lt?xml version"1.0" encoding"UTF-8"?gt
• ltParametersgt
• ltParameter name"SoapAddressgthttp//myserver.com/
  Helloweatherlt/Parametergt
• lt/Parametersgt

11
Compiled output

• lt?xml version"1.0" encoding"utf-8"?gt
• ltxslstylesheet xmlnsxsl"http//www.w3.org/1999/
  XSL/Transform"
• xmlnssoap"http//schemas.xmlsoap
  .org/wsdl/soap/"
• xmlnswsdl"http//schemas.xmlsoap
  .org/wsdl/"
• version"2.0"gt
• ltxslparam name"Partner_Server"gtfile///d/CPA
  /parameters/wsdl.Server.parameters.xmllt/xslparamgt
  
• ltxslvariable name"SoapAddress"gt
• ltxslcopy-of select"document(Partner_Serve
  r)//Parameter_at_name'SoapAddress'/childnode()"/
  gt
• lt/xslvariablegt
• ltxsltemplate match"soapaddress/_at_location"gt
• ltxslvariable name"value"
  select"current()"/gt
• ltxslattribute name"location"gt
• ltxslchoosegt
• ltxslwhen test"SoapAddress !''"gt
• ltxslvalue-of select"SoapAddress"
  /gt
• lt/xslwhengt
• ltxslotherwisegt
• ltxslvalue-of select"value"/gt
• lt/xslotherwisegt

12
Extension CPP intersection

• ltafddCollaborationProtocolAgreement
  version"2.0" id"cpaab"gt
• ltafddColloborationProtocolProfileIntersectio
  ngt
• ltafddStart param"DeploymentStart"/gt
• ltafddEnd param"DeploymentEnd"/gt
• ltafddCPAId param"CpaId_AB"/gt
• ltafddCollaborationProtocolProfile
  version"2.0" param"CPP_A"gt
• ltafddProcessSpecification
  uuid"Procurement"/gt
• ltafddRole name"Seller"/gt
• lt/afddCollaborationProtocolProfilegt
• ltafddCollaborationProtocolProfile
  version"2.0" param"CPP_B"gt
• ltafddProcessSpecification
  uuid"Procurement"/gt
• ltafddRole name"Buyer"/gt
• lt/afddCollaborationProtocolProfilegt
• lt/afddColloborationProtocolProfileIntersecti
  ongt
• lt/afddCollaborationProtocolAgreementgt

13
Package

• Package available at http//www.oasis-open.org/app
  s/org/workgroup/ebxml-cppa/download.php/27623/CPAd
  ist.zip
• AFDD XML schema
• Compiler from AFDD to XSLT, in XSLT
• Python driver scripts
• Seven sample AFDD documents

14
Sample documents

• bias.afdd
• simple CPA template, where one partner acts as
  server (setting start, end and CPA id) and the
  other provides communication details for use as
  client.
• 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.

15
Status

• A predecessor of AFDD is used in Netherlands
  government projects
• Web user interface
• Reuse of uploaded parameters
• Next steps / plans
• Discuss with TC (18-04-2008)
• Document schema as TC WD spec
• Formation as a networked service
• CPP intersection
• ebBP to CPA template
• CPA lifecycle messages (issue, revoke)

16
(No Transcript)
17
Formation as a service

• Bilateral request / response protocol
• Two partners, one to supply parameters
• Request contains parameters
• Response is formed agreement document (or
  rejection)
• Hub / spoke model
• One partner requests coordinator to start
  formation process
• Coordinator contacts each participant, retrieves
  parameters
• Coordinator creates and distributes agreement
  documents
• Transport Bindings
• ebMS, Web Services Portal interface