Collaboration-Protocol Profile and Agreement Specification http www ebxml

Collaboration-Protocol Profile and Agreement Specification http: //www. ebxml. org/specs/eb. CCP. pdf Armin Haller Digital Enterprise Research Institute armin. haller@deri. org 04 -08 -2004 dumitru. roman@deri. org

Outline • • • eb. XML Overview Collaboration Protocol Profile (CPP) Collaboration-Protocol Agreement (CPA) The potentials and use of an eb. XML formal description Leverage in WSMO armin. haller@deri. org 2

eb. XML Overview • eb. XML is a global electronic business standard • sponsored by – UN/CEFACT = international body, supported by the United Nations, that aims to simplify international trade, notably through electronic means – OASIS = international consortium of vendors and users of markup languages • first announced in September, 1999 armin. haller@deri. org 3

eb. XML Overview (cont’d) • Goals – Specifications to enable interoperability – extend e-commerce to SMEs and emerging markets – collaborate with other initiatives and standards development organizations – building on the experience and strengths of existing EDI knowledge armin. haller@deri. org 4

eb. XML Overview (cont’d) • Infrastructure elements – eb. XML Messaging Service specification (eb. MS) – Registry & Repository – Trading Partner Information – Business Process Specification Schema armin. haller@deri. org 5

eb. XML Overview (cont’d) Infrastructure elements • eb. XML Messaging Service specification (eb. MS) – extends the SOAP specification – can be used independently of other eb. XML specifications – defines both a message format and the behavior of software that exchanges eb. XML messages armin. haller@deri. org 6

eb. XML Overview (cont’d) Infrastructure elements • Registry & Repository – serves as a central repository – Repository stores data – Registry is where users can query & retrieve data – eb. XML Registry architecture is based on a clientserver architecture armin. haller@deri. org 7

eb. XML Overview (cont’d) Infrastructure elements • Business Process Specification Schema (BPSS) – provides a standard framework to describe a business process in an XML document – modeled in UML and converted to XML – does not specify the structure of Busines documents – supports the specification of Business Transactions and the choreography of Business Transactions into Business Collaborations armin. haller@deri. org 8

eb. XML Overview (cont’d) Infrastructure elements • Trading Partner Information – specifies the technical details of how to do ebusiness – Collaboration Protocol Profile (CPP) – Collaboration Protocol Agreement (CPA) armin. haller@deri. org 9

Collaboration Protocol Profile (CPP) • Formal description file that defines a party’s message exchange capabilities and the Business Collaboration that it supports • written in XML, fairly long • possible to create multiple CPPs • Can be stored in the eb. XML Registry armin. haller@deri. org 10

Collaboration Protocol Profile (CPP) (cont’d) • The CPP contains: – Collaboration. Protocol. Profile – Party. Info – Packaging – Signature – Comment armin. haller@deri. org 11

Collaboration Protocol Profile (CPP) (cont’d) - Collaboration. Protocol. Profile • Rootelement of the document • Includes as usual the namespace declarations • Three mandatory – Default ns: xmlns=„http: //www. ebxml. org/namespaces/trade. Partner“ – XML Digital Signature ns: xmlns: ds=„http: //www. w 3. org/2000/09/xmldsig#“ – XLINK ns: xmlns: xlink=„http: //www. w 3. org/1999/xlink armin. haller@deri. org 12

Collaboration Protocol Profile (CPP) (cont’d) - Party. Info • General information about the organization • more than one party. Info element possible • the Party. Info element consists of 7 child elements: – – – – Party. Id element Collaboration. Role element Certificate element Delivery. Channel element Transport element Doc. Exchange element Party. Ref element armin. haller@deri. org 13

Collaboration Protocol Profile (CPP) (cont’d) - Packaging • Includes information how the message header and the payload constituents are packaged for transmittal • Information what document-security packaging is used • Include three child elements – Required Processing. Capabilites Elemet – Required Simple. Part Element – Optional Composite. List Element armin. haller@deri. org 14

Collaboration Protocol Profile (CPP) (cont’d) - Signature • CPP can be digitally signed using technology that conforms with XML Digital Signature • Constraints on ds: Signatures – CPP must be considered invalid if any ds: Signature element fails validation as defined by XML Digital Signature – If CPP is signed, each ds: Reference element must pass reference validation and each ds: Signature must pass core validation armin. haller@deri. org 15

Collaboration Protocol Profile (CPP) (cont’d) - Comments • Optional element for textual notes • Multiple comments are possible armin. haller@deri. org 16

Collaboration Protocol Agreement (CPA) • Defines the capabilities that two Parties must agree upon to enable them to engage in electronic Business • Can be seen as interserction between the CPPs of two organizations • After agreeing on one CPA two organizations have identical CPA • Used to customize their particular systems • CPAs can be stored in eb. XML registry like the CPPs armin. haller@deri. org 17

Collaboration Protocol Agreement (CPA) (cont’d) • Structure of CPA is similar to CPP, consists of: – Status – CPA Lifetime – Conversation. Constraints – Party. Info – Signature (identical to CPP element) – Comment (identical to CPP element) armin. haller@deri. org 18

Collaboration Protocol Agreement (CPA) (cont’d) - Status • Has a required value attribute recording the current state of composition of CPA • Possible values: – Proposed – Agreed – Signed armin. haller@deri. org 19

Collaboration Protocol Agreement (CPA) (cont’d) - CPA Lifetime • The lifetime of the CPA is given by Start and Endelements • Start element specifies the starting date and time of the CPA • End element specifies the ending date and time of the CPA • Both should conform to the content model of a canonical time. Instant as defined in the XML Schema Datatypes Specification armin. haller@deri. org 20

Collaboration Protocol Agreement (CPA) (cont’d) - Conversation. Constraints • Element places limits on the number of conversations under the CPA • Two attributes: – invocation. Limit – concurrent. Conversations armin. haller@deri. org 21

Collaboration Protocol Agreement (CPA) (cont’d) - Pary. Info • Similar to CPP Party. Info • Only difference, two Party. Info elements, one for each organization armin. haller@deri. org 22

The potentials and use of an eb. XML formal description • suffices to look up the commonalities in the two CPP • software has found a match and it can configure itself for HTTP • if CPP are incompatible (e. g. one party uses only ftp, the other only http), two parties cannot establish an electronic relationship armin. haller@deri. org 23

Leverage in WSMO • eb. XML addresses more general issues – in WSMO one web service is an operation of a WSDL file – in eb. XML everything accessible through any possible network can be described in CPP • definition of protocols, channels etc. are required • other elements are part of WSMO capabilities description (Party. Info) • other elements would be part of choreography description in WSMO? (Collaboration. Role) armin. haller@deri. org 24

Collaboration-Protocol Profile and Agreement Specification Q&A 04 -08 -2004 dumitru. roman@deri. org