OASIS Committee/Project Specification
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.
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.
Open Document Format for Office Applications (OpenDocument) Version 1.3
Part 1 of the Open Document Format for Office Applications (OpenDocument) Version 1.3 specification.
Open Document Format for Office Applications (OpenDocument) Version 1.3
Part 1 of the Open Document Format for Office Applications (OpenDocument) Version 1.3 specification.
Produced by:
OASIS Open Document Format for Office Applications (OpenDocument) TCVoting history:
December 2019
OASIS Standard:
Committee Specification 01
Part 1: Introduction
ODT
HTML
PDF
Part 3: OpenDocument Schema
ODT
HTML
PDF
Part 4: Recalculated Formula (OpenFormula) Format
ODT
HTML
PDF
XML/RNG schemas and OWL ontologies
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs01/schemas/
Distribution ZIP file
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs01/OpenDocument-v1.3-cs01.zip
Cite as:
Cite as:
[OpenDocument-v1.3-part1] Open Document Format for Office Applications (OpenDocument) Version 1.3. Part 1: Introduction.
Edited by Patrick Durusau. 25 December 2019. OASIS Committee Specification 01
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs01/part1-introduction/OpenDocument-v1.3-cs01-part1-introduction.html.
Latest stage: https://docs.oasis-open.org/office/OpenDocument/v1.3/OpenDocument-v1.3-part1-introduction.html.
[OpenDocument-v1.3-part2] Open Document Format for Office Applications (OpenDocument) Version 1.3. Part 2: Packages.
Edited by Patrick Durusau. 25 December 2019. OASIS Committee Specification 01.
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs01/part2-packages/OpenDocument-v1.3-cs01-part2-packages.html.
Latest stage: https://docs.oasis-open.org/office/OpenDocument/v1.3/OpenDocument-v1.3-part2-packages.html.
[OpenDocument-v1.3-part3] Open Document Format for Office Applications (OpenDocument) Version 1.3. Part 3: OpenDocument Schema. Edited by Patrick Durusau. 25 December 2019. OASIS Committee Specification 01.
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs01/part3-schema/OpenDocument-v1.3-cs01-part3-schema.html.
Latest stage: https://docs.oasis-open.org/office/OpenDocument/v1.3/OpenDocument-v1.3-part3-schema.html.
[OpenDocument-v1.3-part4] Open Document Format for Office Applications (OpenDocument) Version 1.3. Part 4: Recalculated Formula (OpenFormula) Format.
Edited by Patrick Durusau. 25 December 2019. OASIS Committee Specification 01.
https://docs.oasis-open.org/office/OpenDocument/v1.3/cs01/part4-formula/OpenDocument-v1.3-cs01-part4-formula.html.
Latest stage: https://docs.oasis-open.org/office/OpenDocument/v1.3/OpenDocument-v1.3-part4-formula.html.
Digital Signature Service Core Protocols, Elements, and Bindings Version 2.0
Defines JSON and XML based request/response protocols for signing and verifying documents and other data. It also defines a timestamp format, and a signature property for use with these protocols. Finally, it defines transport and security bindings for the protocols.
Digital Signature Service Core Protocols, Elements, and Bindings Version 2.0
Defines JSON and XML based request/response protocols for signing and verifying documents and other data. It also defines a timestamp format, and a signature property for use with these protocols. Finally, it defines transport and security bindings for the protocols.
Produced by:
OASIS Digital Signature Services eXtended (DSS-X) TCVoting history:
July 2019
OASIS Standard:
Cite as:
Cite as:
[DSS-v2.0]
Digital Signature Service Core Protocols, Elements, and Bindings Version 2.0. Edited by Andreas Kuehne and Stefan Hagen. 11 December 2019. OASIS Committee Specification 02. https://docs.oasis-open.org/dss-x/dss-core/v2.0/cs02/dss-core-v2.0-cs02.html. Latest version: https://docs.oasis-open.org/dss-x/dss-core/v2.0/dss-core-v2.0.html.
Digital Signature Service Metadata Version 1.0
Defines JSON and XML structures and discovery mechanisms for metadata related to digital signature services.
Digital Signature Service Metadata Version 1.0
Defines JSON and XML structures and discovery mechanisms for metadata related to digital signature services.
Produced by:
OASIS Digital Signature Services eXtended (DSS-X) TCVoting history:
July 2019
OASIS Standard:
Cite as:
Cite as:
[DSS-MD-v1.0]
Digital Signature Service Metadata Version 1.0. Edited by Detlef Hühnlein and Andreas Kuehne. 11 December 2019. OASIS Committee Specification 02.
https://docs.oasis-open.org/dss-x/dss-md/v1.0/cs02/dss-md-v1.0-cs02.html.
Latest version: https://docs.oasis-open.org/dss-x/dss-md/v1.0/dss-md-v1.0.html.
Open Command and Control (OpenC2) Language Specification Version 1.0
A concise and extensible language to enable machine-to-machine communications for purposes of command and control of cyber defense components, subsystems and/or systems in a manner that is agnostic of the underlying products, technologies, transport mechanisms or other aspects of the implementation. It should be understood that a language such as OpenC2 is necessary but insufficient to enable coordinated cyber responses that occur within cyber relevant time. Other aspects of coordinated cyber response such as sensing, analytics, and selecting appropriate courses of action are beyond the scope of OpenC2.
Open Command and Control (OpenC2) Language Specification Version 1.0
A concise and extensible language to enable machine-to-machine communications for purposes of command and control of cyber defense components, subsystems and/or systems in a manner that is agnostic of the underlying products, technologies, transport mechanisms or other aspects of the implementation. It should be understood that a language such as OpenC2 is necessary but insufficient to enable coordinated cyber responses that occur within cyber relevant time. Other aspects of coordinated cyber response such as sensing, analytics, and selecting appropriate courses of action are beyond the scope of OpenC2.
Produced by:
OASIS Open Command and Control (OpenC2) TCVoting history:
November 2019
OASIS Standard:
Cite as:
Cite as:
[OpenC2-Lang-v1.0] Open Command and Control (OpenC2) Language Specification Version 1.0.
Edited by Jason Romano and Duncan Sparrell. 24 November 2019. OASIS Committee Specification 02.
https://docs.oasis-open.org/openc2/oc2ls/v1.0/cs02/oc2ls-v1.0-cs02.html.
Latest version: https://docs.oasis-open.org/openc2/oc2ls/v1.0/oc2ls-v1.0.html.
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.
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.
TOSCA Simple Profile in YAML Version 1.3
Defines a simplified profile of the TOSCA version 1.0 specification in a YAML rendering which is intended to simplify the authoring of TOSCA service templates. This profile defines a less verbose and more human-readable YAML rendering, reduced level of indirection between different modeling artifacts as well as the assumption of a base type system.
TOSCA Simple Profile in YAML Version 1.3
Defines a simplified profile of the TOSCA version 1.0 specification in a YAML rendering which is intended to simplify the authoring of TOSCA service templates. This profile defines a less verbose and more human-readable YAML rendering, reduced level of indirection between different modeling artifacts as well as the assumption of a base type system.
Produced by:
OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TCVoting history:
September 2019
OASIS Standard:
Cite as:
Cite as:
[TOSCA-Simple-Profile-YAML-v1.3]
TOSCA Simple Profile in YAML Version 1.3. Edited by Matt Rutkowski, Chris Lauwers,
Claude Noshpitz, and Calin Curescu. 18 September 2019. OASIS Committee Specification 01.
https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/cs01/TOSCA-Simple-Profile-YAML-v1.3-cs01.html.
Latest version: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/TOSCA-Simple-Profile-YAML-v1.3.html.
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.
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.
Static Analysis Results Interchange Format (SARIF) Version 2.1.0
Defines a standard format for the output of static analysis tools. The format is referred to as the “Static Analysis Results Interchange Format” and is abbreviated as SARIF.
Static Analysis Results Interchange Format (SARIF) Version 2.1.0
Defines a standard format for the output of static analysis tools. The format is referred to as the “Static Analysis Results Interchange Format” and is abbreviated as SARIF.
Produced by:
OASIS Static Analysis Results Interchange Format (SARIF) TCVoting history:
July 2019
OASIS Standard:
Cite as:
Cite as:
[SARIF-v2.1.0] Static Analysis Results Interchange Format (SARIF) Version 2.1.0. Edited by Michael C. Fanning and Laurence J. Golding. 23 July 2019. OASIS Committee Specification 01. https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html. Latest version: https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html.
Open Command and Control (OpenC2) Language Specification Version 1.0
A concise and extensible language to enable machine-to-machine communications for purposes of command and control of cyber defense components, subsystems and/or systems in a manner that is agnostic of the underlying products, technologies, transport mechanisms or other aspects of the implementation. It should be understood that a language such as OpenC2 is necessary but insufficient to enable coordinated cyber responses that occur within cyber relevant time. Other aspects of coordinated cyber response such as sensing, analytics, and selecting appropriate courses of action are beyond the scope of OpenC2.
Open Command and Control (OpenC2) Language Specification Version 1.0
A concise and extensible language to enable machine-to-machine communications for purposes of command and control of cyber defense components, subsystems and/or systems in a manner that is agnostic of the underlying products, technologies, transport mechanisms or other aspects of the implementation. It should be understood that a language such as OpenC2 is necessary but insufficient to enable coordinated cyber responses that occur within cyber relevant time. Other aspects of coordinated cyber response such as sensing, analytics, and selecting appropriate courses of action are beyond the scope of OpenC2.
Produced by:
OASIS Open Command and Control (OpenC2) TCVoting history:
July 2019
OASIS Standard:
Cite as:
Cite as:
[OpenC2-Lang-v1.0] Open Command and Control (OpenC2) Language Specification Version 1.0. Edited by Jason Romano and Duncan Sparrell. 11 July 2019. OASIS Committee Specification 01. https://docs.oasis-open.org/openc2/oc2ls/v1.0/cs01/oc2ls-v1.0-cs01.html. Latest version: https://docs.oasis-open.org/openc2/oc2ls/v1.0/oc2ls-v1.0.html.
Open Command and Control (OpenC2) Profile for Stateless Packet Filtering Version 1.0
A concise and extensible language to enable the command and control of cyber defense components, subsystems and/or systems in a manner that is agnostic of the underlying products, technologies, transport mechanisms or other aspects of the implementation. Stateless packet filtering is a cyber defense mechanism that denies or allows traffic based on static properties of the traffic, such as address, port, protocol, etc. This profile defines the Actions, Targets, Specifiers and Options that are consistent with the version 1.0 of the OpenC2 Language Specification ([OpenC2-Lang-v1.0]) in the context of stateless packet filtering (SLPF).
Open Command and Control (OpenC2) Profile for Stateless Packet Filtering Version 1.0
A concise and extensible language to enable the command and control of cyber defense components, subsystems and/or systems in a manner that is agnostic of the underlying products, technologies, transport mechanisms or other aspects of the implementation. Stateless packet filtering is a cyber defense mechanism that denies or allows traffic based on static properties of the traffic, such as address, port, protocol, etc. This profile defines the Actions, Targets, Specifiers and Options that are consistent with the version 1.0 of the OpenC2 Language Specification ([OpenC2-Lang-v1.0]) in the context of stateless packet filtering (SLPF).
Produced by:
OASIS Open Command and Control (OpenC2) TCVoting history:
July 2019
OASIS Standard:
Cite as:
Cite as:
[OpenC2-SLPF-v1.0] Open Command and Control (OpenC2) Profile for Stateless Packet Filtering Version 1.0. Edited by Joe Brule, Duncan Sparrell and Alex Everett. 11 July 2019. Committee Specification 01. https://docs.oasis-open.org/openc2/oc2slpf/v1.0/cs01/oc2slpf-v1.0-cs01.html. Latest version: https://docs.oasis-open.org/openc2/oc2slpf/v1.0/oc2slpf-v1.0.html.
Specification for Transfer of OpenC2 Messages via HTTPS Version 1.0d
Specifies the use of HTTP over TLS as a transfer mechanism for OpenC2 Messages.
Specification for Transfer of OpenC2 Messages via HTTPS Version 1.0d
Specifies the use of HTTP over TLS as a transfer mechanism for OpenC2 Messages.
Produced by:
OASIS Open Command and Control (OpenC2) TCVoting history:
July 2019
OASIS Standard:
Cite as:
Cite as:
[OpenC2-HTTPS-v1.0] Specification for Transfer of OpenC2 Messages via HTTPS Version 1.0. Edited by David Lemire. 11 July 2019. OASIS Committee Specification 01. https://docs.oasis-open.org/openc2/open-impl-https/v1.0/cs01/open-impl-https-v1.0-cs01.html. Latest version: https://docs.oasis-open.org/openc2/open-impl-https/v1.0/open-impl-https-v1.0.html.
No results with the selected filters