OASIS Committee/Project Specification
Common Security Advisory Framework Version 2.0
A language to exchange Security Advisories formulated in JSON. CSAF v2.0 is the definitive reference for the language which supports creation, update, and interoperable exchange of security advisories as structured information on products, vulnerabilities and the status of impact and remediation among interested parties.
Common Security Advisory Framework Version 2.0
A language to exchange Security Advisories formulated in JSON. CSAF v2.0 is the definitive reference for the language which supports creation, update, and interoperable exchange of security advisories as structured information on products, vulnerabilities and the status of impact and remediation among interested parties.
Produced by:
Common Security Advisory Framework (CSAF) TCVoting history:
August 2022
OASIS Standard:
Cite as:
Common Security Advisory Framework Version 2.0. Edited by Langley Rock, Stefan Hagen, and Thomas Schmidt. 01 August 2022. OASIS Committee Specification 03. https://docs.oasis-open.org/csaf/csaf/v2.0/cs03/csaf-v2.0-cs03.html. Latest stage: https://docs.oasis-open.org/csaf/csaf/v2.0/csaf-v2.0.html.
PKCS #11 Profiles Version 3.1
For developers and architects who wish to design systems and applications that conform to the PKCS #11 Cryptographic Token Interface specification
PKCS #11 Profiles Version 3.1
For developers and architects who wish to design systems and applications that conform to the PKCS #11 Cryptographic Token Interface specification
Produced by:
PKCS 11 TCVoting history:
OASIS Standard:
Cite as:
PKCS #11 Profiles Version 3.1. Edited by Tim Hudson. 14 July 2022. OASIS Committee Specification 01. https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/cs01/pkcs11-profiles-v3.1-cs01.html. Latest stage: https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/pkcs11-profiles-v3.1.html.
Virtual I/O Device (VIRTIO) Version 1.2
Describes the specifications of the “virtio” family of devices. These devices are found in virtual environments, yet by design they look like physical devices to the guest within the virtual machine – and this document treats them as such. This similarity allows the guest to use standard drivers and discovery mechanisms.
The purpose of virtio and this specification is that virtual environments and guests should have a straightforward, efficient, standard and extensible mechanism for virtual devices, rather than boutique per-environment or per-OS mechanisms.
Virtual I/O Device (VIRTIO) Version 1.2
Describes the specifications of the “virtio” family of devices. These devices are found in virtual environments, yet by design they look like physical devices to the guest within the virtual machine – and this document treats them as such. This similarity allows the guest to use standard drivers and discovery mechanisms.
The purpose of virtio and this specification is that virtual environments and guests should have a straightforward, efficient, standard and extensible mechanism for virtual devices, rather than boutique per-environment or per-OS mechanisms.
Produced by:
Virtual I/O Device (VIRTIO) TCVoting history:
July 2022
OASIS Standard:
Committee Specification 01
Cite as:
Virtual I/O Device (VIRTIO) Version 1.2. Edited by Michael S. Tsirkin and Cornelia Huck. 01 July 2022. OASIS Committee Specification 01. https://docs.oasis-open.org/virtio/virtio/v1.2/cs01/virtio-v1.2-cs01.html. Latest stage: https://docs.oasis-open.org/virtio/virtio/v1.2/virtio-v1.2.html.
Secure QR Code Authentication Version 1.0
Describes the use of QR Codes and a mobile phone as a replacement for a username and password
Secure QR Code Authentication Version 1.0
Describes the use of QR Codes and a mobile phone as a replacement for a username and password
Produced by:
Electronic Secure Authentication (ESAT) TCVoting history:
July 2022
OASIS Standard:
Cite as:
Secure QR Code Authentication Version 1.0. Edited by Don Sheppard. 01 July 2022. OASIS Committee Specification 01. https://docs.oasis-open.org/esat/sqrap/v1.0/cs01/sqrap-v1.0-cs01.html. Latest stage: https://docs.oasis-open.org/esat/sqrap/v1.0/sqrap-v1.0.html.
Common Security Advisory Framework Version 2.0
A language to exchange Security Advisories formulated in JSON. CSAF v2.0 is the definitive reference for the language which supports creation, update, and interoperable exchange of security advisories as structured information on products, vulnerabilities and the status of impact and remediation among interested parties.d
Common Security Advisory Framework Version 2.0
A language to exchange Security Advisories formulated in JSON. CSAF v2.0 is the definitive reference for the language which supports creation, update, and interoperable exchange of security advisories as structured information on products, vulnerabilities and the status of impact and remediation among interested parties.d
Produced by:
OASIS Common Security Advisory Framework (CSAF) TCVoting history:
June 2022
OASIS Standard:
Committee Specification 02
JSON schemas:
Aggregator
CSAF
Provider
Cite as:
[csaf-v2.0]
Common Security Advisory Framework Version 2.0. Edited by Langley Rock, Stefan Hagen, and Thomas Schmidt. 29 June 2022. OASIS Committee Specification 02. https://docs.oasis-open.org/csaf/csaf/v2.0/cs02/csaf-v2.0-cs02.html. Latest stage: https://docs.oasis-open.org/csaf/csaf/v2.0/csaf-v2.0.html.
OSLC Configuration Management Version 1.0
Defining an RDF vocabulary and a set of REST APIs for managing versions and configurations of linked data resources from multiple domains.
OSLC Configuration Management Version 1.0
Defining an RDF vocabulary and a set of REST APIs for managing versions and configurations of linked data resources from multiple domains.
Produced by:
Open Services for Lifecycle Collaboration Open ProjectVoting history:
May 2022
OASIS Standard:
Project Specification 01
Part 1: Overview
Part 2: Versioned Resources
Part 3: Configuration Specification
Part 4: RDF Vocabulary
Cite as:
[OSLC-Config-1.0-Part1]
OSLC Configuration Management Version 1.0. Part 1: Overview. Edited by Nick Crossley. 30 May 2022. OASIS Project Specification 01. https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/oslc-config-mgt.html. Latest stage: https://docs.oasis-open-projects.org/oslc-op/config/v1.0/oslc-config-mgt.html.
[OSLC-Config-1.0-Part2]
OSLC Configuration Management Version 1.0. Part 2: Versioned Resources. Edited by Nick Crossley. 30 May 2022. OASIS Project Specification 01. https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/versioned-resources.html. Latest stage: https://docs.oasis-open-projects.org/oslc-op/config/v1.0/versioned-resources.html.
OSLC-Config-1.0-Part3]
OSLC Configuration Management Version 1.0. Part 3: Configuration Specification. Edited by Nick Crossley. 30 May 2022. OASIS Project Specification 01. https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/config-resources.html. Latest stage: https://docs.oasis-open-projects.org/oslc-op/config/v1.0/config-resources.html.
[OSLC-Config-1.0-Part4]
OSLC Configuration Management Version 1.0. Part 4: RDF Vocabulary. Edited by Nick Crossley. 30 May 2022. OASIS Project Specification 01. https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/config-vocab.html. Latest stage: https://docs.oasis-open-projects.org/oslc-op/config/v1.0/config-vocab.html.
Code List Representation (genericode) Version 1.0
Describes the OASIS Code List Representation model and W3C XML Schema, known collectively as “genericode”.
Code List Representation (genericode) Version 1.0
Describes the OASIS Code List Representation model and W3C XML Schema, known collectively as “genericode”.
Produced by:
OASIS Code List Representation TCVoting history:
April 2022
OASIS Standard:
Committee Specification 02
Editable source
HTML
PDF
PDF marked with changes since previous public review
JSON examples
Schematron constraints
XML examples
XML constraints
JSON translation in XSLT
Cite as:
[genericode-1.0]
Code List Representation (genericode) Version 1.0. Edited by G. Ken Holman. 06 April 2022. OASIS Committee Specification 02. https://docs.oasis-open.org/codelist/genericode/v1.0/cs02/genericode-v1.0-cs02.html. Latest stage: https://docs.oasis-open.org/codelist/genericode/v1.0/genericode-v1.0.html.
OSLC Tracked Resource Set Version 3.0
The Tracked Resource Set protocol allows a server to expose a set of resources in a way that allows clients to discover that set of resources, to track additions to and removals from the set, and to track state changes to the resources in the set.
OSLC Tracked Resource Set Version 3.0
The Tracked Resource Set protocol allows a server to expose a set of resources in a way that allows clients to discover that set of resources, to track additions to and removals from the set, and to track state changes to the resources in the set.
Produced by:
Open Services for Lifecycle Collaboration Open ProjectVoting history:
OASIS Standard:
Project Specification 01
Part 1: Specification
Part 2: Vocabulary
Part 3: Constraints
RDF Vocabulary definitions file
Resource Shape Constraints definitions file
Cite as:
[OSLC-TRS-v3.0]
OSLC Tracked Resource Set Version 3.0. Part 1: Specification. Edited by Nick Crossley. 07 February 2022. OASIS Project Specification 01. https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps01/tracked-resource-set.html. Latest stage: https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/tracked-resource-set.html.
[OSLC-TRS-v3.0]
OSLC Tracked Resource Set Version 3.0. Part 2: Vocabulary. Edited by Nick Crossley. 07 February 2022. OASIS Project Specification 01. https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps01/tracked-resource-set-vocab.html. Latest stage: https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/tracked-resource-set-vocab.html.
[OSLC-TRS-v3.0]
OSLC Tracked Resource Set Version 3.0. Part 3: Constraints. Edited by Nick Crossley. 07 February 2022. OASIS Project Specification 01. https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps01/tracked-resource-set-shapes.html. Latest stage: https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/tracked-resource-set-shapes.html.
OSLC PROMCODE Version 1.0
Defines standard information for managing contracted software delivery based on the OSLC framework
OSLC PROMCODE Version 1.0
Defines standard information for managing contracted software delivery based on the OSLC framework
Produced by:
OSLC Lifecycle Integration for Project Management of Contracted Delivery (OSLC PROMCODE) TCVoting history:
February 2022
OASIS Standard:
Committee Specification 03
Part 1: Specification
Part 2: Vocabulary
Part 3: Constraints
Machine-readable files
Cite as:
[OSLC-PROMCODE-v1.0-Spec]
OSLC PROMCODE Version 1.0. Part 1: Specification. Edited by Mikio Aoyama, Yoshio Horiuchi, Tom Kamimura, Shinji Matsuoka, Shigeaki Matsumoto, Masaki Wakao, Kazuo Yabuta, and Hiroyuki Yoshida. 15 February 2022. OASIS Committee Specification 03. https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-spec.html. Latest stage: https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/promcode-spec.html.
[OSLC-PROMCODE-v1.0-Vocab]
OSLC PROMCODE Version 1.0. Part 2: Vocabulary. Edited by Mikio Aoyama, Yoshio Horiuchi, Tom Kamimura, Shinji Matsuoka, Shigeaki Matsumoto, Masaki Wakao, Kazuo Yabuta, and Hiroyuki Yoshida. 15 February 2022. OASIS Committee Specification 03. https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-vocab.html. Latest stage: https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/promcode-vocab.html.
[OSLC-PROMCODE-v1.0-Shapes]
OSLC PROMCODE Version 1.0. Part 3: Constraints. Edited by Mikio Aoyama, Yoshio Horiuchi, Tom Kamimura, Shinji Matsuoka, Shigeaki Matsumoto, Masaki Wakao, Kazuo Yabuta, and Hiroyuki Yoshida. 15 February 2022. OASIS Committee Specification 03. https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-shapes.html. Latest stage: https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/promcode-shapes.html.
OData Extension for Temporal Data Version 4.0 – Committee Specification 01
Defines how to represent and interact with time-dependent data using the Open Data Protocol (OData).
OData Extension for Temporal Data Version 4.0 – Committee Specification 01
Defines how to represent and interact with time-dependent data using the Open Data Protocol (OData).
Produced by:
OASIS Open Data Protocol (OData) TCVoting history:
OASIS Standard:
Committee Specification 01
Temporal ABNF Construction Rules
Temporal ABNF Test Cases
Temporal Vocabulary
Cite as:
[OData-Temporal-v4.0]
OData Extension for Temporal Data Version 4.0. Edited by Ralf Handl, Hubert Heijkers, Gerald Krause, Michael Pizzo, Heiko Theißen, and Martin Zurmühl. 25 January 2022. OASIS Committee Specification 01. https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/cs01/odata-temporal-ext-v4.0-cs01.html. Latest stage: https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/odata-temporal-ext-v4.0.html.
XACML v3.0 Dynamic Attribute Authority Version 1.0 – Committee Specification 01
Defines a new XACML system component, the Dynamic Attribute Authority, which augments the request context of an XACML authorization request with additional attributes and attribute values that are generated on demand according to a set of rules. The rules are expressed as XACML policies, use obligations to specify the additional attributes and values, and are processed in the normal manner of a Policy Decision Point. d
XACML v3.0 Dynamic Attribute Authority Version 1.0 – Committee Specification 01
Defines a new XACML system component, the Dynamic Attribute Authority, which augments the request context of an XACML authorization request with additional attributes and attribute values that are generated on demand according to a set of rules. The rules are expressed as XACML policies, use obligations to specify the additional attributes and values, and are processed in the normal manner of a Policy Decision Point. d
Produced by:
eXtensible Access Control Markup Language (XACML) TCVoting history:
January 2022
OASIS Standard:
Cite as:
[XACML-Dyn-Attr-v3.0]
XACML v3.0 Dynamic Attribute Authority Version 1.0. Edited by Steven Legg. 25 January 2022. OASIS Committee Specification 01. https://docs.oasis-open.org/xacml/xacml-3.0-dyn-attr/v1.0/cs01/xacml-3.0-dyn-attr-v1.0-cs01.html. Latest stage: https://docs.oasis-open.org/xacml/xacml-3.0-dyn-attr/v1.0/xacml-3.0-dyn-attr-v1.0.html.
Specification for Transfer of OpenC2 Messages via HTTPS Version 1.1 – Committee Specification 01
Specifies the use of HTTP over TLS as a transfer mechanism for OpenC2 Messages. A Testing conformance target is provided to support interoperability testing without security mechanisms.
Specification for Transfer of OpenC2 Messages via HTTPS Version 1.1 – Committee Specification 01
Specifies the use of HTTP over TLS as a transfer mechanism for OpenC2 Messages. A Testing conformance target is provided to support interoperability testing without security mechanisms.
Produced by:
OASIS Open Command and Control (OpenC2) TCVoting history:
November 2021
OASIS Standard:
Cite as:
[OpenC2-HTTPS-v1.1]
Specification for Transfer of OpenC2 Messages via HTTPS Version 1.1. Edited by David Lemire. 30 November 2021. OASIS Committee Specification 01. https://docs.oasis-open.org/openc2/open-impl-https/v1.1/cs01/open-impl-https-v1.1-cs01.html. Latest stage: https://docs.oasis-open.org/openc2/open-impl-https/v1.1/open-impl-https-v1.1.html.
No results with the selected filters