Part A operates a B2B mail server that implements EDIINT AS2. By binding ActionBinding elements to AS2Channel configurations, A expresses its ability to send and receive UBL documents in the OrderingBilling service using signed EDIINT AS2 messages. Note that message exchange is linked to channels at the action level. This means that A can only use AS2 for a subset of its exchange and another protocol for other exchanges, or use different AS2 configurations (which may differ, for example, whether features such as signature or encryption are used or not) for different exchanges. The CPPA3 schema provides an abstract SAMLToken element and a SAMLKeyConfirmedSubjectToken replacement element. This supports configuring ebMS3 messaging systems for use with the ebMS3 SAML Conformance Clause [ebMS-saml-conformance] specification, which profiles the use of ebMS3 and AS4 with the SAML WS-Security token profile [WSS-SAML-Token-Profile-V1.1.1]. This specification supports the use of WS-Security using symmetric or asymmetric SAML tokens for key holders to authenticate ebMS3 senders to recipients. Collaboration profiles are one of the key elements of ebXML that allow users to quickly configure their interactions and relationships with partners, detailing communication methods, endpoints, partner IDs, security and reliability options. In addition, profiles add the ability to define message transactions and their send/receive linkages so that ebMS can validate message exchange with partners. Partner profile information is also used in ebXML mail envelopes to review and identify exchange details. The payload profile referenced in the first action binding displayed indicates that the exchange contains a business document payload portion with the application/xml MIME content type. This part has a required property called EDIGASDocumentType with a fixed value of AL3. In the referenced usage profile, Business Services uses party role values defined in an industry-specific code list.
The following excerpt shows that a party can run the ZSH role to exchange messages with parties that execute the ZSO role. Service values are also retrieved from a list of service codes that contains the value A09. The usage profile prescribes a fixed edigas.org/service value of the service type attribute. In services, in this case, all exchanges are profiled to use the default AS4 value for the action. This is a decision taken for the Community. Alternatively, the action can be set to a value that reflects a specific business action. In the examples, the different trades are distinguished by references to different payload profiles. A packaging element specifies a physical packaging. The CPPA3 schema supports SOAP, MIME, SOAP-with-Attachments, and MTOM, and is extensible to other types of packages. The element MUST NOT be used with protocols that do not have configurable packaging.
PACKAGING ELEMENTS CAN reference PayloadPart elements. It is also possible to reference a channel profile, but to override the values specified in it. In the following example, a part refers to the same channel profile, but expresses that it supports two compression algorithms for the channel. The order indicates a preference for the Application/Brotli algorithm, but application/gzip is also supported for compatibility reasons. (Note that the AS4 standard and the ENTSOG baseline usage profile only support the application/gzip. At the time of writing, any support for Brotli compression would be a proprietary extension.) Because of the way CPA training works in CPPA3, the Brotli option could only be chosen if the counterpart also supported it. The OASIS standard (ISO 15000-1) of the ebXML Profile and Collaboration Agreement (CPPA) defines how business partners collaborate through the exchange of electronic messages. The specification is driven by the OASIS ebXML CPPA technical committee, a group that remains open to new investments. CPP and CPA documents CAN be signed by including an XML signature wrapped in the document. In the case of a CPP, the certificate used to sign the document should identify the natural or legal person to whom the CPP refers.
Alternatively, the certificate can identify a third party who is authorized to publish profile information about the cooperation protocol on the party. B2B messaging protocols supported by this release of CPPA include the ebMS3 Core [EBMS3CORE] specification, the ebMS3 Part 2 Advanced Features [EBMS3PART2] specification, the AS4 [AS4] profile, and the SAML compliance clause for AS4/ebMS [ebMS-saml compliance]. Rpc and CPA, as well as this version of the CSLA specification, refer to the ebMS3 concept of « processing mode » or mode P as follows: To share and deploy a new agreement, the parties may use the CPA registration service described in section 5.4. • A ProfileIdentifier that identifies the profile. An ActionBinding MAY reference to payload profiles using the PayloadProfileId element. As with ChannelId child elements, the relative order expresses a preference, the pairs are mapped in the deep CPP order of the first second, and the first corresponding pair (if any) is included in the CPA. This pros specification is complemented by the normative CPPA3 XML schema, the exception XML schema for contract registration, the normative documentation integrated into these schemas, and examples of non-normative documents. .
