Invitation to comment on OSLC PROMCODE v1.0 Errata 02

OASIS and the OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery (OSLC PROMCODE) TC are pleased to announce that OSLC PROMCODE v1.0 Errata 02 is now available for public review and comment.

This document lists errata for the OASIS Standard “OSLC PROMCODE Version 1.0.”

As described in the document:
– There are changes to the published OASIS Standard documents for Part 1: Specification and Part 3: Constraints.
– There are no changes to the published OASIS Standard documents for Part 2: Vocabulary.
– Changes have also been made to the two OASIS Standard machine-readable “turtle” files (promcode-vocab.ttl and promcode-shapes.ttl). – The modified “turtle” files are included in this publication.

The documents and related files are available here:

OSLC PROMCODE Version 1.0 Errata 02
Committee Specification Draft 01
11 November 2022

HTML:
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/errata02/csd01/promcode-v1.0-errata02-csd01.html (Authoritative)
PDF:
https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/errata02/csd01/promcode-v1.0-errata02-csd01.pdf

Machine-readable files
Vocabulary terms: https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/errata02/csd01/promcode-vocab.ttl
Constraints: https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/errata02/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/errata02/csd01/promcode-v1.0-errata02-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.

This 15-day public review starts 23 November 2022 at 00:00 UTC and ends 07 December 2022 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/errata02/csd01/promcode-v1.0-errata02-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

STIX™ Best Practices Guide Version 1.0.0 published by CTI TC

OASIS is pleased to announce publication of “STIX™ Best Practices Guide Version 1.0.0”, a Committee Note from the members of the OASIS Cyber Threat Intelligence (CTI) TC [1].

This guide suggests best practices to use for STIX content, considering both the normative statements in the specification, as well as considerations beyond the specification.

The Committee Note is available here:

STIX™ Best Practices Guide Version 1.0.0
Committee Note 01
15 September 2022

Editable source (Authoritative):
https://docs.oasis-open.org/cti/stix-bp/v1.0.0/cn01/stix-bp-v1.0.0-cn01.docx

HTML:
https://docs.oasis-open.org/cti/stix-bp/v1.0.0/cn01/stix-bp-v1.0.0-cn01.html

PDF:
https://docs.oasis-open.org/cti/stix-bp/v1.0.0/cn01/stix-bp-v1.0.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/cti/stix-bp/v1.0.0/cn01/stix-bp-v1.0.0-cn01.zip

Members of the CTI TC approved this Committee Note by a Full Majority vote on 15 September 2022 as documented in the TC minutes [2].

Our congratulations to all the members of the TC.

Additional references

[1] OASIS Cyber Threat Intelligence (CTI) TC
https://www.oasis-open.org/committees/cti/

[2] Approval
https://www.oasis-open.org/committees/download.php/70342/09.2022%20-%20Session%201%20-%20OASIS-CTI-TC_Monthly_Meeting.docx.pdf

Open Command and Control (OpenC2) Architecture v1.0 approved as a Committee Specification

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

Cyberattacks are increasingly sophisticated, less expensive to execute, dynamic and automated. The provision of cyber defense via statically configured products operating in isolation is untenable. Standardized interfaces, protocols and data models will facilitate the integration of the functional blocks within a system and between systems. Open Command and Control (OpenC2) is 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.

The OpenC2 Architecture Specification describes the abstract architecture of OpenC2 to define a common understanding of the messages and interactions for all bindings and serializations.

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:

Open Command and Control (OpenC2) Architecture Specification Version 1.0
Committee Specification 01
30 September 2022

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

The non-material changes since the most recent public review are documented in:
https://docs.oasis-open.org/openc2/oc2arch/v1.0/cs01/oc2arch-v1.0-cs01-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/openc2/oc2arch/v1.0/cs01/oc2arch-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 with non-material changes 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/oc2arch/v1.0/csd02/oc2arch-v1.0-csd02-public-review-metadata.html
– Most recent comment resolution log:
https://docs.oasis-open.org/openc2/oc2arch/v1.0/csd02/oc2arch-v1.0-csd02-comment-resolution-log.pdf

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

PKCS #11 Specification v3.1 from PKCS 11 TC approved as a Committee Specification

OASIS is pleased to announce that PKCS #11 Specification Version 3.1 from the OASIS PKCS 11 TC [1] has been approved as an OASIS Committee Specification.

The Public Key Cryptography Standards (PKCS) are a group of public-key cryptography standards devised and published by RSA Security LLC, starting in the early 1990s. The OASIS PKCS 11 Technical Committee addresses the ongoing enhancement and maintenance of the PKCS #11 standard.

PKCS #11 Specification Version 3.1 defines a platform-independent API to cryptographic tokens, such as hardware security modules and smart cards. The API itself is named “Cryptoki” (from “cryptographic token interface” and pronounced as “crypto-key”). This specification defines data types, functions and other basic components of the PKCS #11 Cryptoki interface for devices that may hold cryptographic information and may perform cryptographic functions. It also defines mechanisms that are anticipated for use with the current version of PKCS #11.

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:

PKCS #11 Specification Version 3.1
Committee Specification 01
11 August 2022

PDF (Authoritative):
https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.1/cs01/pkcs11-spec-v3.1-cs01.pdf
HTML:
https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.1/cs01/pkcs11-spec-v3.1-cs01.html
Editable source:
https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.1/cs01/pkcs11-spec-v3.1-cs01.docx
PKCS #11 header files:
https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.1/cs01/include/pkcs11-v3.1/

The changes since the previous publication are marked in:
https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.1/cs01/pkcs11-spec-v3.1-cs01-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/pkcs11/pkcs11-spec/v3.1/cs01/pkcs11-spec-v3.1-cs01.zip

Members of the PKCS 11 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 PKCS 11 TC
https://www.oasis-open.org/committees/pkcs11/

[2] Public review timeline:
Details of the public reviews are listed in:
https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.1/csd01/pkcs11-spec-v3.1-csd01-public-review-metadata.html
Comment resolution log for most recent public review:
https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.1/csd01/pkcs11-spec-v3.1-csd01-comment-resolution-log.pdf

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

Common Security Advisory Framework v2.0 from CSAF TC approved as revised Committee Specification

OASIS is pleased to announce that Common Security Advisory Framework Version 2.0 from the OASIS Common Security Advisory Framework (CSAF) TC [1] has been approved as an OASIS Committee Specification. This is the third publication of CSAF v2.0 as a Committee Specification.

The Common Security Advisory Framework (CSAF) is 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.

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

The documents and related files are available here:

Common Security Advisory Framework Version 2.0
Committee Specification 03
01 August 2022

Editable source (Authoritative):
https://docs.oasis-open.org/csaf/csaf/v2.0/cs03/csaf-v2.0-cs03.md
HTML:
https://docs.oasis-open.org/csaf/csaf/v2.0/cs03/csaf-v2.0-cs03.html
PDF:
https://docs.oasis-open.org/csaf/csaf/v2.0/cs03/csaf-v2.0-cs03.pdf
JSON schemas:
– Aggregator: https://docs.oasis-open.org/csaf/csaf/v2.0/cs03/schemas/aggregator_json_schema.json
– CSAF: https://docs.oasis-open.org/csaf/csaf/v2.0/cs03/schemas/csaf_json_schema.json
– Provider: https://docs.oasis-open.org/csaf/csaf/v2.0/cs03/schemas/provider_json_schema.json
The changes since the previous publication are marked in:
https://docs.oasis-open.org/csaf/csaf/v2.0/cs03/csaf-v2.0-cs03-DIFF.pdf
Issues resolved after previous publication (CS02) are individually tracked in:
https://docs.oasis-open.org/csaf/csaf/v2.0/cs02/csaf-v2.0-cs02-comment-resolution-log.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/csaf/csaf/v2.0/cs03/csaf-v2.0-cs03.zip

Members of the CSAF 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 Common Security Advisory Framework (CSAF) TC
https://www.oasis-open.org/committees/csaf/

[2] Public reviews:
Details of the previous public reviews are listed in:
https://docs.oasis-open.org/csaf/csaf/v2.0/csd02/csaf-v2.0-csd02-public-review-metadata.html

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

Invitation to comment on Open Command and Control (OpenC2) Architecture Specification v1.0

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

Cyberattacks are increasingly sophisticated, less expensive to execute, dynamic and automated. The provision of cyber defense via statically configured products operating in isolation is untenable. Standardized interfaces, protocols and data models will facilitate the integration of the functional blocks within a system and between systems. Open Command and Control (OpenC2) is 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. A high level overview of OpenC2 featuring insights from the Technical Director of NSA’s Capabilities Directorate can be viewed at https://www.youtube.com/watch?v=kCooyNJoOrU.

This specification describes the abstract architecture of OpenC2 to define a common understanding of the messages and interactions for all bindings and serializations.

The documents and related files are available here:

Open Command and Control (OpenC2) Architecture Specification Version 1.0
Committee Specification Draft 02
20 July 2022

Editable source (Authoritative):
https://docs.oasis-open.org/openc2/oc2arch/v1.0/csd02/oc2arch-v1.0-csd02.md

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

PDF:
https://docs.oasis-open.org/openc2/oc2arch/v1.0/csd02/oc2arch-v1.0-csd02.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/oc2arch/v1.0/csd02/oc2arch-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 July 2022 at 00:00 UTC and ends 27 August 2022 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=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 any 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/oc2arch/v1.0/csd02/oc2arch-v1.0-csd02-public-review-metadata.html

PKCS #11 Profiles v3.1 from PKCS 11 TC approved as a Committee Specification

OASIS is pleased to announce that PKCS #11 Profiles Version 3.1 from the OASIS PKCS 11 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 conform to the PKCS #11 Cryptographic Token Interface specification, which documents an API for devices that may hold cryptographic information and may perform cryptographic functions.

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:

PKCS #11 Profiles Version 3.1
Committee Specification 01
14 July 2022

PDF (Authoritative):
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/cs01/pkcs11-profiles-v3.1-cs01.pdf
HTML:
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/cs01/pkcs11-profiles-v3.1-cs01.html
Editable source:
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/cs01/pkcs11-profiles-v3.1-cs01.docx

PKCS #11 test cases:
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/cs01/test-cases/

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/pkcs11/pkcs11-profiles/v3.1/cs01/pkcs11-profiles-v3.1-cs01.zip

Members of the PKCS 11 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 PKCS 11 TC
https://www.oasis-open.org/committees/pkcs11/

[2] Public review timeline:
Details of the public reviews are listed in:
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/csd02/pkcs11-profiles-v3.1-csd02-public-review-metadata.html
Comment resolution log for most recent public review:
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/csd02/pkcs11-profiles-v3.1-csd02-comment-resolution-log.txt

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

Virtual I/O Device (VIRTIO) v1.2 from VIRTIO TC approved as a Committee Specification

OASIS is pleased to announce that Virtual I/O Device (VIRTIO) Version 1.2 from the OASIS Virtual I/O Device (VIRTIO) TC [1] has been approved as an OASIS Committee Specification.

This document 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.

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:

Virtual I/O Device (VIRTIO) Version 1.2
Committee Specification 01
01 July 2022

Editable source (Authoritative):
https://docs.oasis-open.org/virtio/virtio/v1.2/cs01/tex/
HTML:
https://docs.oasis-open.org/virtio/virtio/v1.2/cs01/virtio-v1.2-cs01.html
PDF:
https://docs.oasis-open.org/virtio/virtio/v1.2/cs01/virtio-v1.2-cs01.pdf
Example driver listing:
https://docs.oasis-open.org/virtio/virtio/v1.2/cs01/listings/

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/virtio/virtio/v1.2/cs01/virtio-v1.2-cs01.zip

Members of the VIRTIO 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 Virtual I/O Device (VIRTIO) TC
https://www.oasis-open.org/committees/virtio/

[2] Public review:
* 30-day public review, 10 May 2022:
https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/virtio-v1.2-csd01-public-review-metadata.html
https://lists.oasis-open.org/archives/members/202205/msg00002.html
– Comment resolution log:
https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/virtio-v1.2-csd01-comment-resolution-log.txt

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

Secure QR Code Authentication v1.0 from ESAT TC approved as a Committee Specification

OASIS is pleased to announce that Secure QR Code Authentication Version 1.0 from the OASIS Electronic Secure Authentication (ESAT) TC [1] has been approved as an OASIS Committee Specification.

This document describes the use of QR Codes and a mobile phone as a replacement for a username and password in user login authentication. An alternative to passwords that includes QR Codes is described, and typical use cases are described. This document also provides an overview and context for using QR Codes for security purposes.

In addition, this document specifies a “Secure QR Code Authentication Protocol” (SQRAP) and assesses the related security threats and risks.

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

The documents and related files are available here:

Secure QR Code Authentication Version 1.0
Committee Specification 01
01 July 2022

Editable source (Authoritative):
https://docs.oasis-open.org/esat/sqrap/v1.0/cs01/sqrap-v1.0-cs01.docx
HTML:
https://docs.oasis-open.org/esat/sqrap/v1.0/cs01/sqrap-v1.0-cs01.html
PDF:
https://docs.oasis-open.org/esat/sqrap/v1.0/cs01/sqrap-v1.0-cs01.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/esat/sqrap/v1.0/cs01/sqrap-v1.0-cs01.zip

Members of the ESAT 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 Electronic Secure Authentication (ESAT) TC
https://www.oasis-open.org/committees/esat/

[2] Public reviews:
– 30-day public review, 12 May 2022:
https://docs.oasis-open.org/esat/sqrap/v1.0/csd01/sqrap-v1.0-csd01-public-review-metadata.html
https://lists.oasis-open.org/archives/members/202205/msg00003.html
– Comment resolution log:
https://docs.oasis-open.org/esat/sqrap/v1.0/csd01/sqrap-v1.0-csd01-comment-resolution-log.docx

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

Common Security Advisory Framework v2.0 from CSAF TC approved as a Committee Specification

OASIS is pleased to announce that Common Security Advisory Framework Version 2.0 from the OASIS Common Security Advisory Framework (CSAF) TC [1] has been approved as an OASIS Committee Specification. This is the second publication of CSAF v2.0 as a Committee Specification.

The Common Security Advisory Framework (CSAF) is 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.

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

The documents and related files are available here:

Common Security Advisory Framework Version 2.0
Committee Specification 02
29 June 2022

Editable source (Authoritative):
https://docs.oasis-open.org/csaf/csaf/v2.0/cs02/csaf-v2.0-cs02.md
HTML:
https://docs.oasis-open.org/csaf/csaf/v2.0/cs02/csaf-v2.0-cs02.html
PDF:
https://docs.oasis-open.org/csaf/csaf/v2.0/cs02/csaf-v2.0-cs02.pdf
JSON schemas:
– Aggregator: https://docs.oasis-open.org/csaf/csaf/v2.0/cs02/schemas/aggregator_json_schema.json
– CSAF: https://docs.oasis-open.org/csaf/csaf/v2.0/cs02/schemas/csaf_json_schema.json
– Provider: https://docs.oasis-open.org/csaf/csaf/v2.0/cs02/schemas/provider_json_schema.json

The changes since the previous publication are marked in:
https://docs.oasis-open.org/csaf/csaf/v2.0/cs02/csaf-v2.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/csaf/csaf/v2.0/cs02/csaf-v2.0-cs02.zip

Members of the CSAF 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 Common Security Advisory Framework (CSAF) TC
https://www.oasis-open.org/committees/csaf/

[2] Public reviews:
Details of the previous public reviews are listed in:
https://docs.oasis-open.org/csaf/csaf/v2.0/csd02/csaf-v2.0-csd02-public-review-metadata.html
Comment resolution log for most recent public review:
https://docs.oasis-open.org/csaf/csaf/v2.0/csd02/csaf-v2.0-csd02-comment-resolution-log.md
https://docs.oasis-open.org/csaf/csaf/v2.0/csd02/csaf-v2.0-csd02-comment-resolution-log.pdf

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

Invitation to comment on Electronic Court Filing v5.01 and ECF Web Services SIP v5.01

We are pleased to announce that Electronic Court Filing Version 5.01 and Electronic Court Filing Web Services Service Interaction Profile Version 5.01 from the LegalXML Electronic Court Filing TC [1] are now available for public review and comment. This is the first public review for Version 5.01 of these specifications.

ECF defines a technical architecture and a set of components, operations and message structures for an electronic court filing system, and sets forth rules governing its implementation.

Electronic Court Filing Version 5.01 (ECF v5.01) consists of a set of non-proprietary XML and Web Services specifications developed to promote interoperability among electronic court filing vendors and systems. ECF v5.01 is a minor release that adds new functionality and capabilities beyond the scope of the ECF 5,0, 4.0 and 4.01 specifications that it supersedes.

Electronic Court Filing Web Services Service Interaction Profile defines a Service Interaction Profile, as defined in section 7 of the ECF v5.01 specification. The Web Services Service Interaction Profile may be used to transmit ECF 5.01 messages between Internet-connected systems.

The documents and related files are available here:

Electronic Court Filing Version 5.01
Committee Specification Draft 01
23 May 2022

Editable source (Authoritative):
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.01/csd01/ecf-v5.01-csd01.docx
HTML:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.01/csd01/ecf-v5.01-csd01.html
PDF:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.01/csd01/ecf-v5.01-csd01.pdf
XML schemas and Genericode code lists:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.01/csd01/schema/
XML example messages:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.01/csd01/examples/
Model and documentation:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.01/csd01/model/
UML model artifacts:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.01/csd01/uml/
Complete package in ZIP file:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.01/csd01/ecf-v5.01-csd01.zip
Public review metadata record:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.01/csd01/ecf-v5.01-csd01-public-review-metadata.html
************************

Electronic Court Filing Web Services Service Interaction Profile Version 5.01
Committee Specification Draft 01
31 May 2022

Editable source (Authoritative):
https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.01/csd01/ecf-webservices-v5.01-csd01.docx
HTML:
https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.01/csd01/ecf-webservices-v5.01-csd01.html
PDF:
https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.01/csd01/ecf-webservices-v5.01-csd01.pdf
WSDL schemas:
https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.01/csd01/schema/
XML WSDL examples:
https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.01/csd01/examples/
Complete package in ZIP file:
https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.01/csd01/ecf-webservices-v5.01-csd01.zip
Public review metadata record:
https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.01/csd01/ecf-webservices-v5.01-csd01-public-review-metadata.html
***************************

How to Provide Feedback

OASIS and the LegalXML Electronic Court Filing 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 reviews start 17 June 2022 at 00:00 UTC and end 16 July 2022 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=legalxml-courtfiling).

Comments should clearly identify which of these two specifications they address.

Feedback submitted by TC non-members for these works and for other work of this TC is publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/legalxml-courtfiling-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 this specification and the ECF TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/legalxml-courtfiling/

Additional references


[1] OASIS LegalXML Electronic Court Filing TC
https://www.oasis-open.org/committees/legalxml-courtfiling/
[2] https://www.oasis-open.org/policies-guidelines/ipr/
[3] https://www.oasis-open.org/committees/legalxml-courtfiling/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr/#RF-on-Limited-Mode
RF on Limited Terms Mode

OSLC Configuration Management v1.0 Project Specification 01 approved by the OSLC Open Project

OASIS is pleased to announce that OSLC Configuration Management Version 1.0 from the Open Services for Lifecycle Collaboration Open Project [1] has been approved as an OASIS Project Specification.

Managing change and configuration in a complex systems development lifecycle is very difficult, especially in heterogeneous environments that include homegrown tools, open source projects, and commercial tools from different vendors. The OSLC initiative applies World Wide Web and Linked Data principles to enable interoperation of change, configuration, and asset management processes across a product’s entire application and product lifecycle.

OSLC Configuration Management defines an RDF vocabulary and a set of REST APIs for managing versions and configurations of linked data resources from multiple domains.

This Project Specification is an OASIS deliverable, completed and approved by the OP’s Project Governing Board and fully ready for testing and implementation. The applicable open source licenses can be found in the project’s administrative repository at https://github.com/oslc-op/oslc-admin/blob/master/LICENSE.md.

The specification and related files are available at:

OSLC Configuration Management Version 1.0
Project Specification 01
30 May 2022

– OSLC Configuration Management Version 1.0. Part 1: Overview
https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/oslc-config-mgt.html
https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/oslc-config-mgt.pdf

– OSLC Configuration Management Version 1.0. Part 2: Versioned Resources
https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/versioned-resources.html
https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/versioned-resources.pdf

– OSLC Configuration Management Version 1.0. Part 3: Configuration Specification
https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/config-resources.html
https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/config-resources.pdf

– OSLC Configuration Management Version 1.0. Part 4: RDF Vocabulary
https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/config-vocab.html
https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/config-vocab.pdf

– OSLC Configuration Management machine readable “turtle” files:
Vocabulary Terms: https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/config-vocab.ttl
Vocabulary Constraints: https://docs.oasis-open-projects.org/oslc-op/config/v1.0/ps01/config-shapes.ttl

Distribution ZIP file

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

Members of the OSLC OP Project Governing Board approved this specification by Special Majority Vote [2] as required by the Open Project rules [3].

Our congratulations to the participants and contributors in the Open Services for Lifecycle Collaboration Open Project on their achieving this milestone.

Additional references

[1] Open Services for Lifecycle Collaboration Open Project
https://open-services.net/

[2] Approval ballot:
– https://lists.oasis-open-projects.org/g/oslc-op-pgb/message/239

[3] https://www.oasis-open.org/policies-guidelines/open-projects-process

No results with the selected filters