Invitation to comment on Specification for Transfer of OpenC2 Messages via MQTT v1.0

OASIS and the OASIS Open Command and Control (OpenC2) TC are pleased to announce that Specification for Transfer of OpenC2 Messages via MQTT Version 1.0 is now available for public review and comment. This is the first public review for this specification.

Open Command and Control (OpenC2) is 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. Message Queuing Telemetry Transport (MQTT) is a widely-used publish / subscribe (pub/sub) transfer protocol. This specification describes the use of MQTT Version 5.0 as a transfer mechanism for OpenC2 messages.

The documents and related files are available here:

Specification for Transfer of OpenC2 Messages via MQTT Version 1.0
Committee Specification Draft 04
18 August 2021

Editable source (Authoritative):
https://docs.oasis-open.org/openc2/transf-mqtt/v1.0/csd04/transf-mqtt-v1.0-csd04.md

HTML:
https://docs.oasis-open.org/openc2/transf-mqtt/v1.0/csd04/transf-mqtt-v1.0-csd04.html

PDF:
https://docs.oasis-open.org/openc2/transf-mqtt/v1.0/csd04/transf-mqtt-v1.0-csd04.pdf

For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files. You can download the ZIP file at:
https://docs.oasis-open.org/openc2/transf-mqtt/v1.0/csd04/transf-mqtt-v1.0-csd04.zip

How to Provide Feedback

OASIS and the OpenC2 TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of our technical work.

The public review starts 31 August 2021 at 00:00 UTC and ends 29 September 2021 23:59 UTC.

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility, which can be used by following the instructions on the TC’s “Send A Comment” page (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=openc2).

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/openc2-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review, we call your attention to the OASIS IPR Policy [1] applicable especially [2] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

Additional information about the specification and the OpenC2 TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/openc2/

Additional information related to this public review can be found in the public review metadata document [3].

Additional references

[1] https://www.oasis-open.org/policies-guidelines/ipr

[2] https://www.oasis-open.org/committees/openc2/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode
Non-Assertion Mode

[3] Public review metadata document:
– https://docs.oasis-open.org/openc2/transf-mqtt/v1.0/csd04/transf-mqtt-v1.0-csd04-public-review-metadata.html

SAM Threshold Sharing Schemes v1.0 from SAM TC approved as a Committee Specification

OASIS is pleased to announce that SAM Threshold Sharing Schemes Version 1.0 from the OASIS Security Algorithms and Methods (SAM) TC [1] has been approved as an OASIS Committee Specification.

This document is intended for developers and architects who wish to design systems and applications that utilize threshold sharing schemes in an interoperable manner. Committee Specification 02 (CS02) clarifies that the implementation examples in Appendix E are non-normative.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

SAM Threshold Sharing Schemes Version 1.0
Committee Specification 02
19 August 2021

Editable source:
https://docs.oasis-open.org/sam/sam-tss/v1.0/cs02/sam-tss-v1.0-cs02.docx (Authoritative)
HTML:
https://docs.oasis-open.org/sam/sam-tss/v1.0/cs02/sam-tss-v1.0-cs02.html
PDF:
https://docs.oasis-open.org/sam/sam-tss/v1.0/cs02/sam-tss-v1.0-cs02.pdf
Non-material changes between CS01 and this CS02 are marked in:
https://docs.oasis-open.org/sam/sam-tss/v1.0/cs02/sam-tss-v1.0-cs02-DIFF.pdf

Distribution ZIP file
For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:
https://docs.oasis-open.org/sam/sam-tss/v1.0/cs02/sam-tss-v1.0-cs02.zip

Members of the SAM TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

Additional references:

[1] OASIS Security Algorithms and Methods (SAM) TC
https://www.oasis-open.org/committees/sam/

[2] Public review:
* 30-day public review, 02 June 2021:
https://lists.oasis-open.org/archives/members/202106/msg00002.html
https://lists.oasis-open.org/archives/members/202106/msg00003.html
– Review metadata:
https://docs.oasis-open.org/sam/sam-tss/v1.0/csd01/sam-tss-v1.0-csd01-public-review-metadata.html
– Comment resolution log:
https://docs.oasis-open.org/sam/sam-tss/v1.0/csd01/sam-tss-v1.0-csd01-comment-resolution-log.txt

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3639

JSON Abstract Data Notation v1.0 from OpenC2 TC approved as a Committee Specification

OASIS is pleased to announce that Specification for JSON Abstract Data Notation Version 1.0 from the OASIS Open Command and Control (OpenC2) TC [1] has been approved as an OASIS Committee Specification.

JSON Abstract Data Notation (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. JADN specifications consist of two parts: abstract type definitions that are independent of data format, and serialization rules that define how to represent type instances using specific data formats. A JADN schema is itself a structured information object that can be serialized and transferred between applications, documented in multiple formats such as text-based interface definition languages, property tables or diagrams, and translated into concrete schemas used to validate specific data formats.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

Specification for JSON Abstract Data Notation Version 1.0
Committee Specification 01
17 August 2021

Editable source:
https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.md (Authoritative)
HTML:
https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.html
PDF:
https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.pdf

Distribution ZIP file
For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:
https://docs.oasis-open.org/openc2/jadn/v1.0/cs01/jadn-v1.0-cs01.zip

Members of the OpenC2 TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

Additional references

[1] OASIS Open Command and Control (OpenC2) TC
https://www.oasis-open.org/committees/openc2/

[2] Public review and comment resolution timeline:
https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02-public-review-metadata.html
– Most recent comment resolution log:
https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02-comment-resolution-log.pdf

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3638

Invitation to comment on Common Security Advisory Framework v2.0

OASIS and the OASIS Common Security Advisory Framework (CSAF) TC are pleased to announce that Common Security Advisory Framework Version 2.0 is now available for public review and comment.

The Common Security Advisory Framework (CSAF) Version 2.0 is the definitive reference for the CSAF 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.

The OASIS CSAF Technical Committee is chartered to make a major revision to the widely-adopted Common Vulnerability Reporting Framework (CVRF) specification, originally developed by the Industry Consortium for Advancement of Security on the Internet (ICASI). ICASI has contributed CVRF to the TC. The revision is being developed under the name Common Security Advisory Framework (CSAF). TC deliverables are designed to standardize existing practice in structured machine-readable vulnerability-related advisories and further refine those standards over time.

The documents and related files are available here:

Common Security Advisory Framework Version 2.0
Committee Specification Draft 01
05 August 2021

Editable source (Authoritative):
https://docs.oasis-open.org/csaf/csaf/v2.0/csd01/csaf-v2.0-csd01.md

HTML:
https://docs.oasis-open.org/csaf/csaf/v2.0/csd01/csaf-v2.0-csd01.html

PDF:
https://docs.oasis-open.org/csaf/csaf/v2.0/csd01/csaf-v2.0-csd01.pdf

JSON schemas:
Aggregator JSON schema:
https://docs.oasis-open.org/csaf/csaf/v2.0/csd01/schemas/aggregator_json_schema.json
CSAF JSON schema:
https://docs.oasis-open.org/csaf/csaf/v2.0/csd01/schemas/csaf_json_schema.json
Provider JSON schema:
https://docs.oasis-open.org/csaf/csaf/v2.0/csd01/schemas/provider_json_schema.json

For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files. You can download the ZIP file at:
https://docs.oasis-open.org/csaf/csaf/v2.0/csd01/csaf-v2.0-csd01.zip

A public review announcement metadata record [3] is published along with the specification files.

How to Provide Feedback

OASIS and the CSAF TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of our technical work.

The public review starts 14 August 2021 at 00:00 UTC and ends 12 September 2021 at 23:59 UTC.

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=csaf).

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/csaf-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review, we call your attention to the OASIS IPR Policy [1] applicable especially [2] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

Additional information about the specification and the CSAF TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/csaf/

Additional references

[1] https://www.oasis-open.org/policies-guidelines/ipr

[2] https://www.oasis-open.org/committees/csaf/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode

[3] Public review announcement metadata:
https://docs.oasis-open.org/csaf/csaf/v2.0/csd01/csaf-v2.0-csd01-public-review-metadata.html

SAM Threshold Sharing Schemes v1.0 from SAM TC approved as a Committee Specification

OASIS is pleased to announce that SAM Threshold Sharing Schemes Version 1.0 from the OASIS Security Algorithms and Methods (SAM) TC [1] has been approved as an OASIS Committee Specification.

This document is intended for developers and architects who wish to design systems and applications that utilize threshold sharing schemes in an interoperable manner.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

SAM Threshold Sharing Schemes Version 1.0
Committee Specification 01
04 August 2021

Editable source:
https://docs.oasis-open.org/sam/sam-tss/v1.0/cs01/sam-tss-v1.0-cs01.docx (Authoritative)
HTML:
https://docs.oasis-open.org/sam/sam-tss/v1.0/cs01/sam-tss-v1.0-cs01.html
PDF:
https://docs.oasis-open.org/sam/sam-tss/v1.0/cs01/sam-tss-v1.0-cs01.pdf

Distribution ZIP file
For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:
https://docs.oasis-open.org/sam/sam-tss/v1.0/cs01/sam-tss-v1.0-cs01.zip

Members of the SAM TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

Additional references

[1] OASIS Security Algorithms and Methods (SAM) TC
https://www.oasis-open.org/committees/sam/

[2] Public review:
* 30-day public review, 02 June 2021:
https://lists.oasis-open.org/archives/members/202106/msg00002.html
https://lists.oasis-open.org/archives/members/202106/msg00003.html
– Review metadata:
https://docs.oasis-open.org/sam/sam-tss/v1.0/csd01/sam-tss-v1.0-csd01-public-review-metadata.html
– Comment resolution log:
https://docs.oasis-open.org/sam/sam-tss/v1.0/csd01/sam-tss-v1.0-csd01-comment-resolution-log.txt

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3634

Invitation to comment on OData Extension for Temporal Data v4.0

OASIS and the OASIS Open Data Protocol (OData) TC are pleased to announce that OData Extension for Temporal Data Version 4.0 is now available for public review and comment.

This specification defines how to represent and interact with time-dependent data using the Open Data Protocol (OData). It defines semantics and a representation for temporal data, including operations for querying and modifying temporal data along with vocabulary terms to annotate which data depends on time, and how.

The documents and related files are available here:

OData Extension for Temporal Data Version 4.0
Committee Specification Draft 01
29 July 2021

Editable source (Authoritative):
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/csd01/odata-temporal-ext-v4.0-csd01.docx
HTML:
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/csd01/odata-temporal-ext-v4.0-csd01.html
PDF:
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/csd01/odata-temporal-ext-v4.0-csd01.pdf

OData Temporal ABNF Construction Rules Version 4.0:
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/csd01/abnf/odata-temporal-abnf.txt
OData Temporal ABNF Test Cases:
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/csd01/abnf/odata-temporal-testcases.xml
OData Temporal Vocabulary:
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/csd01/vocabularies/Org.OData.Temporal.V1.xml

For your convenience, OASIS provides a complete package of the specification document and any related files in a ZIP distribution file. You can download the ZIP file at:
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/csd01/odata-temporal-ext-v4.0-csd01.zip

How to Provide Feedback

OASIS and the OASIS Open Data Protocol (OData) TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

The public review starts 05 August 2021 at 00:00 UTC and ends 03 September 2021 at 23:59 UTC.

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=odata).

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/odata-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review, we call your attention to the OASIS IPR Policy [1] applicable especially [2] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

Additional information about this review and any previous public reviews is published with the specification documents at:
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/csd01/odata-temporal-ext-v4.0-csd01-public-review-metadata.html.

Additional information about the specification and the OData TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/odata/

Additional references

[1] https://www.oasis-open.org/policies-guidelines/ipr

[2] https://www.oasis-open.org/committees/odata/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-RAND-Mode

OSLC PROMCODE Use Cases v1.0 published

OASIS is pleased to announce publication of “OSLC PROMCODE Use Cases Version 1.0,” a Committee Note from the members of the OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery (OSLC PROMCODE) TC [1].

This document describes use cases, scenarios and flows of detailed activities of some real situations of project management in contracted software delivery which are modeled by the PROMCODE specification. That three-part specification defines the overall approach to PROMCODE (PROject Management of COntracted DElivery), and is based on the Open Services for Lifecycle Collaboration (OSLC) framework for integration of software development.

The Committee Note is available here:

OSLC PROMCODE Use Cases Version 1.0
Committee Note 01
24 June 2021

HTML (Authoritative):
https://docs.oasis-open.org/oslc-promcode/usecase/v1.0/cn01/usecase-v1.0-cn01.html

PDF:
https://docs.oasis-open.org/oslc-promcode/usecase/v1.0/cn01/usecase-v1.0-cn01.pdf

For your convenience, OASIS provides a complete package of the Committee Note that you can download here:
https://docs.oasis-open.org/oslc-promcode/usecase/v1.0/cn01/usecase-v1.0-cn01.zip

Members of the OSLC PROMCODE TC approved this Committee Note by a Full Majority vote on 24 June 2021 as documented in the TC minutes [2].

Our congratulations to all the members of the TC.

Additional references

[1] OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery (OSLC PROMCODE) TC
https://www.oasis-open.org/committees/oslc-promcode/

[2] Approval
https://wiki.oasis-open.org/oslc-promcode/telecon%20June%2024th%2C%202021

Invitation to comment on The DocBook Schema v5.1.1

OASIS and the OASIS DocBook TC are pleased to announce that The DocBook Schema Version 5.1.1 is now available for public review and comment.

Schematron tools do not work with DocBook 5.1. This DocBook 5.1.1 specification is updated with the new Schematron rules so users can continue using DocBook 5.1 if they need to use newer Schematron tools.

The documents and related files are available here:

The DocBook Schema Version 5.1.1
Committee Specification Draft 01
09 June 2021

Editable source (Authoritative):
https://docs.oasis-open.org/docbook/docbook/v5.1.1/csd01/docbook-v5.1.1-csd01.docx

HTML:
https://docs.oasis-open.org/docbook/docbook/v5.1.1/csd01/docbook-v5.1.1-csd01.html

PDF:
https://docs.oasis-open.org/docbook/docbook/v5.1.1/csd01/docbook-v5.1.1-csd01.pdf

Relax NG schemas: https://docs.oasis-open.org/docbook/docbook/v5.1.1/csd01/schemas/rng/
Schematron schema: https://docs.oasis-open.org/docbook/docbook/v5.1.1/csd01/schemas/sch/
https://docs.oasis-open.org/docbook/docbook/v5.1.1/csd01/schemas/catalog.xml
https://docs.oasis-open.org/docbook/docbook/v5.1.1/csd01/schemas/docbook.nvdl

For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files. You can download the ZIP file at:
https://docs.oasis-open.org/docbook/docbook/v5.1.1/csd01/docbook-v5.1.1-csd01.zip

How to Provide Feedback

OASIS and the OASIS DocBook TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

The public review starts 31 July 2021 at 00:00 UTC and ends 29 August 2021 at 23:59 UTC.

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=docbook).

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/docbook-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review, we call your attention to the OASIS IPR Policy [1] applicable especially [2] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

Additional information about this review and any previous public reviews is published with the specification documents at:
https://docs.oasis-open.org/docbook/docbook/v5.1.1/csd01/docbook-v5.1.1-csd01-public-review-metadata.html.

Additional information about the specification and the DocBook TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/docbook/

Additional references

[1] https://www.oasis-open.org/policies-guidelines/ipr

[2] https://www.oasis-open.org/committees/docbook/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-Limited-Mode
RF on Limited Terms Mode

Invitation to comment on OSLC PROMCODE v1.0

OASIS and the OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery (OSLC PROMCODE) TC are pleased to announce that OSLC PROMCODE Version 1.0 is now available for public review and comment. This is the first public review for this draft specification.

This three-part specification defines the overall approach to PROMCODE (PROject Management of COntracted DElivery) based on the Open Services for Lifecycle Collaboration (OSLC) Core v3.0 specification. OSLC Core v3.0 is currently in public review as a candidate for OASIS Standard.

The documents and related files are available here:

OSLC PROMCODE Version 1.0
Committee Specification Draft 01
28 April 2021

OSLC PROMCODE Version 1.0. Part 1: Specification
HTML:
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/csd01/promcode-spec.html (Authoritative)
PDF:
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/csd01/promcode-spec.pdf

OSLC PROMCODE Version 1.0. Part 2: Vocabulary
HTML:
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/csd01/promcode-vocab.html (Authoritative)
PDF:
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/csd01/promcode-vocab.pdf

OSLC PROMCODE Version 1.0. Part 3: Constraints
HTML:
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/csd01/promcode-shapes.html (Authoritative)
PDF:
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/csd01/promcode-shapes.pdf

Machine-readable files
Vocabulary terms: https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/csd01/promcode-vocab.ttl
Constraints: https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/csd01/promcode-shapes.ttl

For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files. You can download the ZIP file at:
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/csd01/promcode-v1.0-csd01.zip

How to Provide Feedback

OASIS and the OSLC PROMCODE TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of our technical work.

The public review starts 24 July 2021 at 00:00 UTC and ends 22 August at 23:59 UTC.

Additional information about this review and any previous public reviews is published with the specification documents at:
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/csd01/promcode-v1.0-csd01-public-review-metadata.html

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=oslc-promcode).

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/oslc-promcode-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review, we call your attention to the OASIS IPR Policy [1] applicable especially [2] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

Additional information about the specification and the OSLC PROMCODE TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/oslc-promcode/

Additional references:

[1] https://www.oasis-open.org/policies-guidelines/ipr

[2] https://www.oasis-open.org/committees/oslc-promcode/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-Limited-Mode
RF on Limited Terms Mode

CACAO Security Playbooks v1.0 from CACAO TC approved as a Committee Specification

OASIS is pleased to announce that CACAO Security Playbooks Version 1.0 from the OASIS Collaborative Automated Course of Action Operations (CACAO) for Cyber Security TC [1] has been approved as an OASIS Committee Specification.

To defend against threat actors and their tactics, techniques, and procedures, organizations need to identify, create, document, and test detection, investigation, prevention, mitigation, and remediation steps. These steps, when grouped together, form a cyber security playbook that can be used to protect organizational systems, networks, data, and users.

This specification defines the schema and taxonomy for cybersecurity playbooks and how cybersecurity playbooks can be created, documented, and shared in a structured and standardized way across organizational boundaries and technological solutions.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

CACAO Security Playbooks Version 1.0
Committee Specification 02
23 June 2021

Editable source (Authoritative):
https://docs.oasis-open.org/cacao/security-playbooks/v1.0/cs02/security-playbooks-v1.0-cs02.docx
HTML:
https://docs.oasis-open.org/cacao/security-playbooks/v1.0/cs02/security-playbooks-v1.0-cs02.html
PDF:
https://docs.oasis-open.org/cacao/security-playbooks/v1.0/cs02/security-playbooks-v1.0-cs02.pdf
PDF marked with changes since previous public review:
https://docs.oasis-open.org/cacao/security-playbooks/v1.0/cs02/security-playbooks-v1.0-cs02-DIFF.pdf

For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files. You can download the ZIP file at:
https://docs.oasis-open.org/cacao/security-playbooks/v1.0/cs02/security-playbooks-v1.0-cs02.zip

Members of the CACAO TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

Additional references:


[1] OASIS Collaborative Automated Course of Action Operations (CACAO) for Cyber Security TC
https://www.oasis-open.org/committees/cacao/

[2] Public review metadata document:
https://docs.oasis-open.org/cacao/security-playbooks/v1.0/csd03/security-playbooks-v1.0-csd03-public-review-metadata.html
– Comment resolution log:
https://docs.oasis-open.org/cacao/security-playbooks/v1.0/csd03/security-playbooks-v1.0-csd03-comment-resolution-log.txt

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3631

Invitation to comment on Specification for JSON Abstract Data Notation v1.0

OASIS and the OASIS Open Command and Control (OpenC2) TC are pleased to announce that Specification for JSON Abstract Data Notation Version 1.0 is now available for public review and comment. This is the second public review for this specification.

JSON Abstract Data Notation (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. JADN specifications consist of two parts: abstract type definitions that are independent of data format, and serialization rules that define how to represent type instances using specific data formats. A JADN schema is itself a structured information object that can be serialized and transferred between applications, documented in multiple formats such as text-based interface definition languages, property tables or diagrams, and translated into concrete schemas used to validate specific data formats.

The documents and related files are available here:

Specification for JSON Abstract Data Notation Version 1.0
Committee Specification Draft 02
16 June 2021

Editable source:
https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.md

HTML:
https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.html

PDF (Authoritative):
https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.pdf

JADN and JSON schemas:
https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/schemas/

For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files. You can download the ZIP file at:
https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02.zip

How to Provide Feedback

OASIS and the OpenC2 TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of our technical work.

The public review starts 29 June 2021 at 00:00 UTC and ends 18 July 2021 23:59 UTC.

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility, which can be used by following the instructions on the TC’s “Send A Comment” page (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=openc2).

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/openc2-comment/.

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review, we call your attention to the OASIS IPR Policy [1] applicable especially [2] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

Additional information about the specification and the OpenC2 TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/openc2/

Additional information related to this and previous public reviews can be found in the public review metadata document [3].

Additional references:

[1] https://www.oasis-open.org/policies-guidelines/ipr

[2] https://www.oasis-open.org/committees/openc2/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode
Non-Assertion Mode

[3] Public review metadata document:
– https://docs.oasis-open.org/openc2/jadn/v1.0/csd02/jadn-v1.0-csd02-public-review-metadata.html

Invitation to comment on AS4 Interoperability Profile for Four-Corner Networks v1.0

We are pleased to announce that AS4 Interoperability Profile for Four-Corner Networks v1.0 from the BDXR TC [1] is now available for public review and comment. This is its first public review.

This specification defines an interoperability profile of the AS4 Profile of ebMS 3.0 for use in four-corner networks. In a four-corner network, entities are exchanging business documents through intermediary gateway services (sometimes called Access Points).

The documents and related files are available here:

AS4 Interoperability Profile for Four-Corner Networks Version 1.0
Committee Specification Draft 01
02 June 2021

Editable source (Authoritative):
https://docs.oasis-open.org/bdxr/bdx-as4/v1.0/csd01/bdx-as4-v1.0-csd01.docx
HTML:
https://docs.oasis-open.org/bdxr/bdx-as4/v1.0/csd01/bdx-as4-v1.0-csd01.html
PDF:
https://docs.oasis-open.org/bdxr/bdx-as4/v1.0/csd01/bdx-as4-v1.0-csd01.pdf

For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files. You can download the ZIP file at:

https://docs.oasis-open.org/bdxr/bdx-as4/v1.0/csd01/bdx-as4-v1.0-csd01.zip

How to Provide Feedback

OASIS and the OASIS Business Document Exchange (BDXR) TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of our technical work.

The public review starts 24 June 2021 at 00:00 UTC and ends 23 July at 23:59 UTC.

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=bdxr).

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:

https://lists.oasis-open.org/archives/bdxr-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review, we call your attention to the OASIS IPR Policy [2] applicable especially [3] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

Additional information about the specification and the BDXR TC can be found at the TC’s public home page [1].

Additional references

[1] OASIS Business Document Exchange (BDXR) TC
http://www.oasis-open.org/committees/bdxr/

[2] http://www.oasis-open.org/policies-guidelines/ipr

[3] http://www.oasis-open.org/committees/bdxr/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode
Non-Assertion Mode

No results with the selected filters