OASIS Committee/Project Specification
Specification for Transfer of OpenC2 Messages via MQTT Version 1.0 – Committee Specification 01
Describes the use of MQTT Version 5.0 as a transfer mechanism for OpenC2 messages.
Specification for Transfer of OpenC2 Messages via MQTT Version 1.0 – Committee Specification 01
Describes the use of MQTT Version 5.0 as a transfer mechanism for OpenC2 messages.
Produced by:
OASIS Open Command and Control (OpenC2) TCVoting history:
November 2021
OASIS Standard:
Cite as:
[OpenC2-MQTT-v1.0]
Specification for Transfer of OpenC2 Messages via MQTT Version 1.0. Edited by David Lemire. 19 November 2021. OASIS Committee Specification 01. https://docs.oasis-open.org/openc2/transf-mqtt/v1.0/cs01/transf-mqtt-v1.0-cs01.html. Latest stage: https://docs.oasis-open.org/openc2/transf-mqtt/v1.0/transf-mqtt-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.
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:
OASIS Common Security Advisory Framework (CSAF) TCVoting history:
November 2021
OASIS Standard:
Committee Specification 01
Cite as:
[csaf-v2.0]
Common Security Advisory Framework Version 2.0. Edited by Langley Rock, Stefan Hagen, and Thomas Schmidt. 12 November 2021. OASIS Committee Specification 01. https://docs.oasis-open.org/csaf/csaf/v2.0/cs01/csaf-v2.0-cs01.html. Latest stage: https://docs.oasis-open.org/csaf/csaf/v2.0/csaf-v2.0.html.
AS4 Interoperability Profile for Four-Corner Networks Version 1.0
Defines an interoperability profile of the AS4 Profile of ebMS 3.0 for use in four-corner networks where entities exchange business documents through intermediary gateway services.
AS4 Interoperability Profile for Four-Corner Networks Version 1.0
Defines an interoperability profile of the AS4 Profile of ebMS 3.0 for use in four-corner networks where entities exchange business documents through intermediary gateway services.
Produced by:
OASIS Business Document Exchange (BDXR) TCVoting history:
November 2021
OASIS Standard:
Cite as:
[BDX-AS4-v1.0]
AS4 Interoperability Profile for Four-Corner Networks Version 1.0. Edited by Todd Albers, Kenneth Bengtsson, Sander Fieten, Philip Helger, Levine Naidoo, and Dennis Weddig. 12 November 2021. OASIS Committee Specification 01. https://docs.oasis-open.org/bdxr/bdx-as4/v1.0/cs01/bdx-as4-v1.0-cs01.html. Latest stage: https://docs.oasis-open.org/bdxr/bdx-as4/v1.0/bdx-as4-v1.0.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:
November 2021
OASIS Standard:
Committee Specification 02
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. 10 November 2021. OASIS Committee Specification 02. https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs02/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. 10 November 2021. OASIS Committee Specification 02. https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs02/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. 10 November 2021. OASIS Committee Specification 02. https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs02/promcode-shapes.html. Latest stage: https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/promcode-shapes.html.
Business Document Naming and Design Rules (BDNDR) Version 1.1
Prescribes a set of naming and design rules used to create complete CCTS models of interoperable business documents.
Business Document Naming and Design Rules (BDNDR) Version 1.1
Prescribes a set of naming and design rules used to create complete CCTS models of interoperable business documents.
Produced by:
OASIS Universal Business Language (UBL) TCVoting history:
November 2021
OASIS Standard:
Cite as:
[Business-Document-NDR-v1.1] Business Document Naming and Design Rules (BDNDR) Version 1.1. Edited by Kenneth Bengtsson, Erlend Klakegg Bergheim and G. Ken Holman. 08 November 2021. OASIS Committee Specification 01. https://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/cs01/Business-Document-NDR-v1.1-cs01.html. Latest stage: https://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/Business-Document-NDR-v1.1.html.
SAM Threshold Sharing Schemes Version 1.0
Intended for developers and architects who wish to design systems and applications that utilize threshold sharing schemes in an interoperable manner.
SAM Threshold Sharing Schemes Version 1.0
Intended for developers and architects who wish to design systems and applications that utilize threshold sharing schemes in an interoperable manner.
Produced by:
OASIS Security Algorithms and Methods (SAM) TCVoting history:
OASIS Standard:
Cite as:
[SAM-TSS-v1.0]
SAM Threshold Sharing Schemes Version 1.0. Edited by Tim Chevalier and Tim Hudson. 14 October 2021. OASIS Committee Specification 03. https://docs.oasis-open.org/sam/sam-tss/v1.0/cs03/sam-tss-v1.0-cs03.html. Latest stage: https://docs.oasis-open.org/sam/sam-tss/v1.0/sam-tss-v1.0.html.
OSLC Architecture Management Version 3.0
Defines the OSLC Architecture Management domain, a RESTful web services interface for the management of architectural resources and relationships between those and related resources such as product change requests, activities, tasks, requirements or test cases. To support these scenarios, this specification defines a set of HTTP-based RESTful interfaces in terms of HTTP methods: GET, POST, PUT and DELETE, as well as HTTP response codes, content type handling and resource formats.
OSLC Architecture Management Version 3.0
Defines the OSLC Architecture Management domain, a RESTful web services interface for the management of architectural resources and relationships between those and related resources such as product change requests, activities, tasks, requirements or test cases. To support these scenarios, this specification defines a set of HTTP-based RESTful interfaces in terms of HTTP methods: GET, POST, PUT and DELETE, as well as HTTP response codes, content type handling and resource formats.
Produced by:
OASIS Open Services for Lifecycle Collaboration (OSLC) OPVoting history:
OASIS Standard:
Project Specification 01
Part 1: Specification
Part 2: Vocabulary
Part 3: Constraints
Cite as:
[OSLC-AM-3.0-Part1]
OSLC Architecture Management Version 3.0. Part 1: Specification. Edited by Jim Amsden. 30 September 2021. OASIS Project Specification 01. https://docs.oasis-open-projects.org/oslc-op/am/v3.0/ps01/architecture-management-spec.html. Latest stage: https://docs.oasis-open-projects.org/oslc-op/am/v3.0/architecture-management-spec.html.
[OSLC-AM-3.0-Part2]
OSLC Architecture Management Version 3.0. Part 2: Vocabulary. Edited by Jim Amsden. 30 September 2021. OASIS Project Specification 01. https://docs.oasis-open-projects.org/oslc-op/am/v3.0/ps01/architecture-management-vocab.html. Latest stage: https://docs.oasis-open-projects.org/oslc-op/am/v3.0/architecture-management-vocab.html.
[OSLC-AM-3.0-Part3]
OSLC Architecture Management Version 3.0. Part 3: Constraints. Edited by Jim Amsden. 30 September 2021. OASIS Project Specification 01. https://docs.oasis-open-projects.org/oslc-op/am/v3.0/ps01/architecture-management-shapes.html. Latest stage: https://docs.oasis-open-projects.org/oslc-op/am/v3.0/architecture-management-shapes.html.
Specification for JSON Abstract Data Notation (JADN) Version 1.0 – Committee Specification 01
JADN is an information modeling language. It has several purposes including defining data structures, validating data instances, informing user interfaces working with structured data, and facilitating protocol internationalization.
Specification for JSON Abstract Data Notation (JADN) Version 1.0 – Committee Specification 01
JADN is an information modeling language. It has several purposes including defining data structures, validating data instances, informing user interfaces working with structured data, and facilitating protocol internationalization.
Produced by:
OASIS Open Command and Control (OpenC2) TCVoting history:
OASIS Standard:
Committee Specification 01
JSON schema for JADN documents
JADN schema for JADN documents
Cite as:
[JADN-v1.0]
JSON Abstract Data Notation Version 1.0. Edited by David Kemp. 17 August 2021. OASIS Committee Specification 01. https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.html. Latest stage: https://docs.oasis-open.org/openc2/jadn/v1.0/jadn-v1.0.html.
SAM Threshold Sharing Schemes Version 1.0
For developers and architects who wish to design systems and applications that utilize threshold sharing schemes in an interoperable manner.
SAM Threshold Sharing Schemes Version 1.0
For developers and architects who wish to design systems and applications that utilize threshold sharing schemes in an interoperable manner.
Produced by:
OASIS Security Algorithms and Methods (SAM) TCVoting history:
OASIS Standard:
Cite as:
[SAM-TSS-v1.0]
SAM Threshold Sharing Schemes Version 1.0. Edited by Tim Chevalier and Tim Hudson. 19 August 2021. OASIS Committee Specification 02. https://docs.oasis-open.org/sam/sam-tss/v1.0/cs02/sam-tss-v1.0-cs02.html. Latest stage: https://docs.oasis-open.org/sam/sam-tss/v1.0/sam-tss-v1.0.html.
SAM Threshold Sharing Schemes Version 1.0
For developers and architects who wish to design secure systems that use threshold sharing schemes in an interoperable manner
SAM Threshold Sharing Schemes Version 1.0
For developers and architects who wish to design secure systems that use threshold sharing schemes in an interoperable manner
Produced by:
OASIS Security Algorithms and Methods (SAM) TCVoting history:
OASIS Standard:
Cite as:
[SAM-TSS-v1.0]
SAM Threshold Sharing Schemes Version 1.0. Edited by Tim Chevalier and Tim Hudson. 04 August 2021. OASIS Committee Specification 01. https://docs.oasis-open.org/sam/sam-tss/v1.0/cs01/sam-tss-v1.0-cs01.html. Latest stage: https://docs.oasis-open.org/sam/sam-tss/v1.0/sam-tss-v1.0.html.
OSLC Requirements Management Version 2.1
Defines the OSLC Requirements Management domain. The specification supports key RESTful web service interfaces for the management of Requirements, Requirements Collections and supporting resources defined in the OSLC Core specification. To support these scenarios, this specification defines a set of HTTP-based RESTful interfaces in terms of HTTP methods: GET, POST, PUT and DELETE, HTTP response codes, content type handling and resource formats.
OSLC Requirements Management Version 2.1
Defines the OSLC Requirements Management domain. The specification supports key RESTful web service interfaces for the management of Requirements, Requirements Collections and supporting resources defined in the OSLC Core specification. To support these scenarios, this specification defines a set of HTTP-based RESTful interfaces in terms of HTTP methods: GET, POST, PUT and DELETE, HTTP response codes, content type handling and resource formats.
Produced by:
OASIS Open Services for Lifecycle Collaboration (OSLC) OPVoting history:
https://lists.oasis-open-projects.org/g/oslc-op-pgb/message/143
OASIS Standard:
Project Specification 02
Part 1: Specification
Part 2: Vocabulary
Part 3: Constraints
Requirements Management Vocabulary definitions file
Requirements Management Resource Shape Constraints definitions file
Cite as:
OSLC-RM-2.1-Part1]
OSLC Requirements Management Version 2.1. Part 1: Specification. Edited by Mark Schulte and Jad El-khoury. 28 May 2021. OASIS Project Specification 02. https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/ps02/requirements-management-spec.html. Latest stage: https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/requirements-management-spec.html.
[OSLC-RM-2.1-Part2]
OSLC Requirements Management Version 2.1. Part 2: Vocabulary. Edited by Mark Schulte and Jad El-khoury. 28 May 2021. OASIS Project Specification 02. https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/ps02/requirements-management-vocab.html. Latest stage: https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/requirements-management-vocab.html.
OSLC-RM-2.1-Part3]
OSLC Requirements Management Version 2.1. Part 3: Constraints. Edited by Mark Schulte and Jad El-khoury. 28 May 2021. OASIS Project Specification 02. https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/ps02/requirements-management-shapes.html. Latest stage: https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/requirements-management-shapes.html.
CACAO Security Playbooks Version 1.0
Defining the schema and taxonomy for collaborative automated course of action operations (CACAO) security playbooks and how these playbooks can be created, documented, and shared in a structured and standardized way across organizational boundaries and technological solutions.
CACAO Security Playbooks Version 1.0
Defining the schema and taxonomy for collaborative automated course of action operations (CACAO) security playbooks and how these playbooks can be created, documented, and shared in a structured and standardized way across organizational boundaries and technological solutions.
Produced by:
OASIS Collaborative Automated Course of Action Operations (CACAO) for Cyber Security TCVoting history:
OASIS Standard:
Cite as:
[CACAO-Security-Playbooks-v1.0]
CACAO Security Playbooks Version 1.0. Edited by Bret Jordan and Allan Thomson. 23 June 2021. OASIS Committee Specification 02. https://docs.oasis-open.org/cacao/security-playbooks/v1.0/cs02/security-playbooks-v1.0-cs02.html. Latest stage: https://docs.oasis-open.org/cacao/security-playbooks/v1.0/security-playbooks-v1.0.html.
No results with the selected filters