Electronic, XML-based agreements between trading partners is a key part of the ebXML family of standards developed jointly by OASIS and the United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT).
OASIS is pleased to announce that Collaboration Protocol Profile and Agreement Version 3.0 from the OASIS ebXML Core (ebCore) TC [1] has been approved as an OASIS Committee Specification.
Electronic Business using eXtensible Markup Language (ebXML) is a family of standards developed through a joint initiative of OASIS and the United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT). Five of these ebXML standards, including Collaboration Protocol Profile and Agreement, have been approved by the International Organization for Standardization (ISO) as the ISO 15000 standard. ebXML provides an open, XML-based infrastructure that enables the global use of electronic business information in an interoperable, secure, and consistent manner by all trading partners.
Collaborative Partner Profile Agreements are XML-based documents specifying a trading agreement between trading partners. Each trading partner will have their own Collaboration Protocol Profile (CPP) document that describes their abilities in an XML format. This can include the messaging protocols they support, or the security capabilities they support. A CPA (Collaboration Protocol Agreement) document is the intersection of two CPP documents, and describes the formal relationship between two parties.
CPPA Version 3.0 (CPPA3) specifies several improvements and innovations since the previous Version 2.0 (CPPA2). A CPPA3 document is much easier to read and to create and update manually or using automated tooling than a corresponding CPPA2 document. The same information can be expressed in a significantly smaller CPPA3 CPA document than in a CPPA2 CPA document. CPPA3 adds support for AMQP, WebSocket transport and the SFTP subsystem of SSH2, in addition to the HTTP, SMTP, FTP transports already covered in CPPA2.
The specification text is complemented by the normative CPPA3 XML schema, the agreement registration Exception XML schema, documentation embedded in those schemas, and sample documents.
This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.
OASIS is pleased to announce that Collaboration Protocol Profile and Agreement Version 3.0 from the OASIS ebXML Core (ebCore) TC [1] has been approved as an OASIS Committee Specification.
Electronic Business using eXtensible Markup Language (ebXML) is a family of standards developed through a joint initiative of OASIS and the United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT). Five of these ebXML standards, including Collaboration Protocol Profile and Agreement, have been approved by the International Organization for Standardization (ISO) as the ISO 15000 standard. ebXML provides an open, XML-based infrastructure that enables the global use of electronic business information in an interoperable, secure, and consistent manner by all trading partners.
Collaborative Partner Profile Agreements are XML-based documents specifying a trading agreement between trading partners. Each trading partner will have their own Collaboration Protocol Profile (CPP) document that describes their abilities in an XML format. This can include the messaging protocols they support, or the security capabilities they support. A CPA (Collaboration Protocol Agreement) document is the intersection of two CPP documents, and describes the formal relationship between two parties.
CPPA Version 3.0 (CPPA3) specifies several improvements and innovations since the previous Version 2.0 (CPPA2). A CPPA3 document is much easier to read and to create and update manually or using automated tooling than a corresponding CPPA2 document. The same information can be expressed in a significantly smaller CPPA3 CPA document than in a CPPA2 CPA document. CPPA3 adds support for AMQP, WebSocket transport and the SFTP subsystem of SSH2, in addition to the HTTP, SMTP, FTP transports already covered in CPPA2.
The specification text is complemented by the normative CPPA3 XML schema, the agreement registration Exception XML schema, documentation embedded in those schemas, and sample documents.
This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.
