Business Document Exchange (BDXR)
BDXR
Defining a federated document transport infrastructure for business document exchange
e-Business
Classification of Everyday Living (COEL)
COEL
Providing a privacy-by-design framework for behavioral data collection and processing
Code List Representation
Defining an XML format for interchange, documentation and management of code lists (a.k.a. controlled vocabularies or coded value enumerations) in any processing context
Invitation to comment on Exchange Header Envelope (XHE) v1.0 from the BDXR TC – ends November 17th
Collaboration Protocol Profile and Agreement v3.0 from ebCore TC approved as a Committee Specification
Invitation to comment on Service Metadata Publishing (SMP) v2.0 – ends 18 December
StandardCollaboration Protocol Profile and Agreement Version 3.0
Defines XML-based trading agreements between trading partners as part of the ebXML family of standards.
Collaboration Protocol Profile and Agreement Version 3.0
Defines XML-based trading agreements between trading partners as part of the ebXML family of standards.
Produced by:
OASIS ebXML Core (ebCore) TCVoting history:
September 2020
OASIS Standard:
Committee Specification 01
Cite as:
Cite as:
[CPPA3]
Collaboration Protocol Profile and Agreement Version 3.0. Edited by Pim van der Eijk. 24 September 2020. OASIS Committee Specification 01.
https://docs.oasis-open.org/ebcore/cppa/v3.0/cs01/cppa-v3.0-cs01.html.
Latest version: https://docs.oasis-open.org/ebcore/cppa/v3.0/cppa-v3.0.html.
StandardService Metadata Publishing (SMP) Version 2.0
Describes a protocol for publishing service metadata within a 4-corner network. In a 4-corner network, entities are exchanging business documents through intermediary gateway services (sometimes called Access Points). To successfully send a business document in a 4-corner network, an entity must be able to discover critical metadata about the recipient of the business document, such as types of documents the recipient is capable of receiving and methods of transport supported. The recipient makes this metadata available to other entities in the network through a Service Metadata Publisher service. This specification describes the request/response exchanges between a Service Metadata Publisher and a client wishing to discover endpoint information. A client can either be an end-user business application or a gateway/access point in the 4-corner network. It also defines the request processing that must happen at the client.
Service Metadata Publishing (SMP) Version 2.0
Describes a protocol for publishing service metadata within a 4-corner network. In a 4-corner network, entities are exchanging business documents through intermediary gateway services (sometimes called Access Points). To successfully send a business document in a 4-corner network, an entity must be able to discover critical metadata about the recipient of the business document, such as types of documents the recipient is capable of receiving and methods of transport supported. The recipient makes this metadata available to other entities in the network through a Service Metadata Publisher service. This specification describes the request/response exchanges between a Service Metadata Publisher and a client wishing to discover endpoint information. A client can either be an end-user business application or a gateway/access point in the 4-corner network. It also defines the request processing that must happen at the client.
Produced by:
OASIS Business Document Exchange (BDXR) TCVoting history:
January 2020
OASIS Standard:
Committee Specification 02
XML schema
XML schema
Model documentation
Namespaces:
http://docs.oasis-open.org/bdxr/ns/SMP/2/ServiceGroup
http://docs.oasis-open.org/bdxr/ns/SMP/2/ServiceMetadata
http://docs.oasis-open.org/bdxr/ns/SMP/2/AggregateComponents
http://docs.oasis-open.org/bdxr/ns/SMP/2/BasicComponents
http://docs.oasis-open.org/bdxr/ns/SMP/2/ExtensionComponents
http://docs.oasis-open.org/bdxr/ns/SMP/2/QualifiedDataTypes
http://docs.oasis-open.org/bdxr/ns/SMP/2/UnqualifiedDataTypes
Cite as:
Cite as:
[BDX-SMP-v2.0] Service Metadata Publishing (SMP) Version 2.0.
Edited by Kenneth Bengtsson, Erlend Klakegg Bergheim, Sander Fieten, and G. Ken Holman. 16 January 2020.
OASIS Committee Specification 02.
https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html.
Latest version: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/bdx-smp-v2.0.html.
StandardCustomer Data Platform Version 1.0
Aims to standardize exchange of customer data across systems and silos by defining a web-based API using GraphQL. The GraphQL api is a self-documented and strongly typed interface. It is designed to be dynamically extended, and allows extensive implementation specific customization.
Customer Data Platform Version 1.0
Aims to standardize exchange of customer data across systems and silos by defining a web-based API using GraphQL. The GraphQL api is a self-documented and strongly typed interface. It is designed to be dynamically extended, and allows extensive implementation specific customization.
Produced by:
OASIS Context Server (CXS) TCVoting history:
October 2019
OASIS Standard:
Cite as:
Cite as:
[CDP-v1.0]
Customer Data Platform Version 1.0. Edited by Thomas Lund Sigdestad and Serge Huber. 04 October 2019. OASIS Committee Specification 01.
https://docs.oasis-open.org/cxs/cdp/v1.0/cs01/cdp-v1.0-cs01.html.
Latest version: https://docs.oasis-open.org/cxs/cdp/v1.0/cdp-v1.0.html.
StandardExchange Header Envelope (XHE) Version 1.0
Defines a business-oriented artefact either referencing (as a header) or containing (as an envelope) a payload of one or more business documents or other artefacts with supplemental semantic information about the collection of payloads as a whole. This is distinct from any transport-layer infrastructure header or envelope that may be required to propagate documents from one system to another. An exchange header envelope describes contextual information important to the sender and receiver about the payloads, without having to modify the payloads in any fashion.
Exchange Header Envelope (XHE) Version 1.0
Defines a business-oriented artefact either referencing (as a header) or containing (as an envelope) a payload of one or more business documents or other artefacts with supplemental semantic information about the collection of payloads as a whole. This is distinct from any transport-layer infrastructure header or envelope that may be required to propagate documents from one system to another. An exchange header envelope describes contextual information important to the sender and receiver about the payloads, without having to modify the payloads in any fashion.
Produced by:
OASIS Business Document Exchange (BDXR) TCVoting history:
September 2019
OASIS Standard:
Cite as:
Cite as:
[XHE-V1.0] Exchange Header Envelope (XHE) Version 1.0. Edited by G. Ken Holman. 05 September 2019.
OASIS Committee Specification 02. https://docs.oasis-open.org/bdxr/xhe/v1.0/cs02/xhe-v1.0-cs02-oasis.html.
Latest version: https://docs.oasis-open.org/bdxr/xhe/v1.0/xhe-v1.0-oasis.html.
StandardService Metadata Publishing (SMP) Version 2.0
Describes a protocol for publishing service metadata within a 4-corner network. In a 4-corner network, entities are exchanging business documents through intermediary gateway services (sometimes called Access Points). To successfully send a business document in a 4-corner network, an entity must be able to discover critical metadata about the recipient of the business document, such as types of documents the recipient is capable of receiving and methods of transport supported. The recipient makes this metadata available to other entities in the network through a Service Metadata Publisher service. This specification describes the request/response exchanges between a Service Metadata Publisher and a client wishing to discover endpoint information. A client can either be an end-user business application or a gateway/access point in the 4-corner network. It also defines the request processing that must happen at the client.
Service Metadata Publishing (SMP) Version 2.0
Describes a protocol for publishing service metadata within a 4-corner network. In a 4-corner network, entities are exchanging business documents through intermediary gateway services (sometimes called Access Points). To successfully send a business document in a 4-corner network, an entity must be able to discover critical metadata about the recipient of the business document, such as types of documents the recipient is capable of receiving and methods of transport supported. The recipient makes this metadata available to other entities in the network through a Service Metadata Publisher service. This specification describes the request/response exchanges between a Service Metadata Publisher and a client wishing to discover endpoint information. A client can either be an end-user business application or a gateway/access point in the 4-corner network. It also defines the request processing that must happen at the client.
Produced by:
OASIS Business Document Exchange (BDXR) TCVoting history:
May 2019
OASIS Standard:
Committee Specification 01
XML schema
XML schema
Model documentation
Namespaces:
http://docs.oasis-open.org/bdxr/ns/SMP/2/ServiceGroup
http://docs.oasis-open.org/bdxr/ns/SMP/2/ServiceMetadata
http://docs.oasis-open.org/bdxr/ns/SMP/2/AggregateComponents
http://docs.oasis-open.org/bdxr/ns/SMP/2/BasicComponents
http://docs.oasis-open.org/bdxr/ns/SMP/2/ExtensionComponents
http://docs.oasis-open.org/bdxr/ns/SMP/2/QualifiedDataTypes
http://docs.oasis-open.org/bdxr/ns/SMP/2/UnqualifiedDataTypes
Cite as:
Cite as:
[BDX-SMP-v2.0] Service Metadata Publishing (SMP) Version 2.0. Edited by Kenneth Bengtsson, Erlend Klakegg Bergheim, Sander Fieten, and G. Ken Holman. 20 May 2019. OASIS Committee Specification 01. https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs01/bdx-smp-v2.0-cs01.html. Latest version: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/bdx-smp-v2.0.html.
StandardExchange Header Envelope (XHE) Version 1.0
Defines a business-oriented artefact either referencing (as a header) or containing (as an envelope) a payload of one or more business documents or other artefacts with supplemental semantic information about the collection of payloads as a whole. This is distinct from any transport-layer infrastructure header or envelope that may be required to propagate documents from one system to another. An exchange header envelope describes contextual information important to the sender and receiver about the payloads, without having to modify the payloads in any fashion.
Exchange Header Envelope (XHE) Version 1.0
Defines a business-oriented artefact either referencing (as a header) or containing (as an envelope) a payload of one or more business documents or other artefacts with supplemental semantic information about the collection of payloads as a whole. This is distinct from any transport-layer infrastructure header or envelope that may be required to propagate documents from one system to another. An exchange header envelope describes contextual information important to the sender and receiver about the payloads, without having to modify the payloads in any fashion.
Produced by:
OASIS Business Document Exchange (BDXR) TCVoting history:
March 2019
OASIS Standard:
Cite as:
Cite as:
[XHE-V1.0] Exchange Header Envelope (XHE) Version 1.0. Edited by G. Ken Holman. 21 March 2019. OASIS Committee Specification 01. https://docs.oasis-open.org/bdxr/xhe/v1.0/cs01/xhe-v1.0-cs01-oasis.html. Latest version: https://docs.oasis-open.org/bdxr/xhe/v1.0/xhe-v1.0-oasis.html.
No results with the selected filters