Invitation to comment on OSLC PROMCODE v1.0 Errata 01

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 01 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 no changes to the published textual documents of the OASIS Standard (Part 1: Specification, Part 2: Vocabulary, and Part 3: Constraints). Changes have been made only to the two 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 01
Committee Specification Draft 01
13 May 2022

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

Machine-readable files
Vocabulary terms: https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/errata01/csd01/promcode-vocab.ttl
Constraints: https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/errata01/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/errata01/csd01/promcode-v1.0-errata01-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 19 May 2022 at 00:00 UTC and ends 02 June 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/errata01/csd01/promcode-v1.0-errata01-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

Invitation to comment on Secure QR Code Authentication v1.0

OASIS and the OASIS Electronic Secure Authentication (ESAT) TC are pleased to announce that Secure QR Code Authentication Version 1.0 is now available for public review and comment. This is the first public review for this draft specification.

Specification Overview

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.

The documents and related files are available here:

Secure QR Code Authentication Version 1.0
Committee Specification Draft 01
25 April 2022

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

A public review metadata record documenting this and any previous public reviews is available at:
https://docs.oasis-open.org/esat/sqrap/v1.0/csd01/sqrap-v1.0-csd01-public-review-metadata.html

How to Provide Feedback

OASIS and the OASIS Electronic Secure Authentication (ESAT) 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 12 May 2022 at 00:00 UTC and ends 10 June 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=esat).

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/esat-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 esat TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/esat/

Additional references

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

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

Invitation to comment on Virtual I/O Device (VIRTIO) Version 1.2

OASIS and the OASIS Virtual I/O Device (VIRTIO) TC are pleased to announce that Virtual I/O Device (VIRTIO) Version 1.2 is now available for public review and comment.

Specification Overview

VIRTIO v1.2 is the largest ever release of the ‘virtio’ specification, with 9 new device types as well as significant new functionality in existing devices, and addressing comments by more than 45 individuals from more than 15 organizations. This specification is fully compatible with the previous version, VIRTIO v1.1.

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.

The documents and related files are available here:

Virtual I/O Device (VIRTIO) Version 1.2
Committee Specification Draft 01
09 May 2022

Editable source (Authoritative):
https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/tex/
HTML:
https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/virtio-v1.2-csd01.html
PDF:
https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/virtio-v1.2-csd01.pdf
Example driver listing:
https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/listings/
PDF file marked to indicate changes from Version 1.1 Committee Specification 01:
https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/virtio-v1.2-csd01-diff-from-v1.1-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/virtio/virtio/v1.2/csd01/virtio-v1.2-csd01.zip

A public review metadata record documenting this and any previous public reviews is available at:
https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/virtio-v1.2-csd01-public-review-metadata.html

How to Provide Feedback

OASIS and the OASIS Virtual I/O Device (VIRTIO) 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 10 May 2022 at 00:00 UTC and ends 08 June 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=virtio).

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/virtio-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 VIRTIO TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/virtio/

Additional references

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

[2] https://github.com/oasis-tcs/virtio-admin/blob/master/IPR.md
https://www.oasis-open.org/policies-guidelines/ipr/#Non-Assertion-Mode
Non-Assertion Mode

Invitation to comment on Energy Interoperation Common Transactive Services (CTS) v1.0

OASIS and the OASIS Energy Interoperation TC are pleased to announce that Energy Interoperation Common Transactive Services (CTS) v1.0 is now available for public review and comment. This is the second public review of this draft specification.

Common Transactive Services (CTS) permits energy consumers and producers to interact through energy markets by simplifying actor interaction with any market. CTS is a streamlined and simplified profile of the OASIS Energy Interoperation (EI) specification, which describes an information and communication model to coordinate the exchange of energy between any two Parties that consume or supply energy, such as energy suppliers and customers, markets and service providers.

The documents and related files are available here:

Energy Interoperation Common Transactive Services (CTS) Version 1.0
Committee Specification Draft 02
28 April 2022

PDF (Authoritative):
https://docs.oasis-open.org/energyinterop/ei-cts/v1.0/csd02/ei-cts-v1.0-csd02.pdf
Editable source:
https://docs.oasis-open.org/energyinterop/ei-cts/v1.0/csd02/ei-cts-v1.0-csd02.docx
HTML:
https://docs.oasis-open.org/energyinterop/ei-cts/v1.0/csd02/ei-cts-v1.0-csd02.html
PDF marked with changes since previous publication:
https://docs.oasis-open.org/energyinterop/ei-cts/v1.0/csd02/ei-cts-v1.0-csd02-DIFF.pdf
Comment resolution log for previous public review:
https://docs.oasis-open.org/energyinterop/ei-cts/v1.0/csd01/ei-cts-v1.0-csd01-comment-resolution-log.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/energyinterop/ei-cts/v1.0/csd02/ei-cts-v1.0-csd02.zip

A public review metadata record documenting this and any previous public reviews is available at:
https://docs.oasis-open.org/energyinterop/ei-cts/v1.0/csd02/ei-cts-v1.0-csd02-public-review-metadata.html

How to Provide Feedback

OASIS and the Energy Interoperation 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 30 April 2022 at 00:00 UTC and ends 01 June 2022 at 23:59 UTC.

The TC requests that comments should cite the line numbers from the PDF formatted version for clarity.

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=energyinterop).

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/energyinterop-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 Energy Interoperation TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/energyinterop/

Additional references

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

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

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. This 15-day review is the second public review for this draft specification.

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 02
30 March 2022

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

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

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

PDF marked with changes since previous publication:
https://docs.oasis-open.org/csaf/csaf/v2.0/csd02/csaf-v2.0-csd02-DIFF.pdf

JSON schemas:
Aggregator JSON schema:
https://docs.oasis-open.org/csaf/csaf/v2.0/csd02/schemas/aggregator_json_schema.json
CSAF JSON schema:
https://docs.oasis-open.org/csaf/csaf/v2.0/csd02/schemas/csaf_json_schema.json
Provider JSON schema:
https://docs.oasis-open.org/csaf/csaf/v2.0/csd02/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/csd02/csaf-v2.0-csd02.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 15 April 2022 at 00:00 UTC and ends 29 April 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=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/csd02/csaf-v2.0-csd02-public-review-metadata.html

Code List Representation (genericode) v1.0 approved as a Committee Specification

OASIS is pleased to announce the approval and publication of an updated Committee Specification by the members of the OASIS Code List Representation TC [1]:

Code List Representation (genericode) Version 1.0
Committee Specification 02
06 April 2022

Overview

Code lists can be defined as controlled vocabularies or coded value enumerations. Examples of standardized code lists include country abbreviations, currency abbreviations, shipping container descriptors, and airport codes. Examples of non-standardized code lists used between trading partners include financial account types, workflow status indicators, and any set of values representing the semantics of related concepts known between the parties involved in information interchange. Code lists have been used for many years, and they have often been published and disseminated in manners that have not been IT-enabled for ease of computer processing.

The Code List Representation format, known as genericode, is a single semantic model of code lists and accompanying XML serialization (supported by a W3C XML Schema) that can encode a broad range of code list information. The serialization is designed to IT-enable the interchange or distribution of machine-readable code list information between systems. Note that genericode is not designed as a run-time format for accessing code list information, and is not optimized for such usage. Rather, it is designed as an interchange format that can be transformed into formats suitable for run-time usage, or loaded into systems that perform run-time processing using code list information.

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:

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

JSON examples:
https://docs.oasis-open.org/codelist/genericode/v1.0/cs02/json-example/
Schematron constraints:
https://docs.oasis-open.org/codelist/genericode/v1.0/cs02/sch/
XML examples:
https://docs.oasis-open.org/codelist/genericode/v1.0/cs02/xml/
XML constraints:
https://docs.oasis-open.org/codelist/genericode/v1.0/cs02/xsd/
JSON translation in XSLT:
https://docs.oasis-open.org/codelist/genericode/v1.0/cs02/xslt/

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/codelist/genericode/v1.0/cs02/genericode-v1.0-cs02.zip

Members of the OASIS Code List Representation 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.

This Committee Specification 02 incorporates changes since the previous public review [4].

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 Code List Representation TC
https://www.oasis-open.org/committees/codelist/

[2] Details of public review:
https://docs.oasis-open.org/codelist/genericode/v1.0/csd04/genericode-v1.0-csd04-public-review-metadata.html

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

[4] Committee Specification Draft 04, 16 October 2021
https://lists.oasis-open.org/archives/members/202111/msg00002.html
– Change description:
https://docs.oasis-open.org/codelist/genericode/v1.0/csd04/genericode-v1.0-csd04-comment-resolution-log.xlsx
https://docs.oasis-open.org/codelist/genericode/v1.0/cs02/genericode-v1.0-cs02-DIFF.pdf

Invitation to comment on PKCS #11 Specification v3.1 and PKCS #11 Profiles v3.1

OASIS and the OASIS PKCS 11 TC are pleased to announce that PKCS #11 Specification v3.1 and PKCS #11 Profiles v3.1 are now available for public review and comment. These 30-day reviews are the first public reviews for Version 3.1 of these specifications.

About the specification drafts

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 on-going enhancement and maintenance of the PKCS #11 standard.

These PKCS #11 specifications define 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”).
– “PKCS #11 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.
– “PKCS #11 Profiles” is intended for developers and architects who wish to design systems and applications that conform to the PKCS #11 Cryptoki specification as providers or consumers.

The documents and related files are available here:

PKCS #11 Specification Version 3.1
Committee Specification Draft 01
16 February 2022

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

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/pkcs11/pkcs11-spec/v3.1/csd01/pkcs11-spec-v3.1-csd01.zip

PKCS #11 Profiles Version 3.1
Committee Specification Draft 02
16 February 2022

PDF (Authoritative):
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/csd02/pkcs11-profiles-v3.1-csd02.pdf
Editable source:
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/csd02/pkcs11-profiles-v3.1-csd02.docx
HTML:
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/csd02/pkcs11-profiles-v3.1-csd02.html
PKCS #11 test cases:
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/csd02/test-cases/
ZIP file:
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/csd02/pkcs11-profiles-v3.1-csd02.zip

How to Provide Feedback

OASIS and the PKCS11 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 reviews start 18 March 2022 at 00:00 UTC and end 16 April 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=pkcs11).

Comments submitted by TC non-members for these works and for other work of this TC are publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/pkcs11-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 these public reviews, 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 specifications, so that notice of them may be posted to the notice page for this TC’s work.

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

Additional information related to these public reviews, including a complete publication and review history, can be found in the public review metadata documents [3].

Additional references

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

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

[3] Public review metadata documents:
https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.1/csd01/pkcs11-spec-v3.1-csd01-public-review-metadata.html
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/csd02/pkcs11-profiles-v3.1-csd02-public-review-metadata.html

Invitation to comment on CACAO Security Playbooks v1.1

OASIS and the OASIS Collaborative Automated Course of Action Operations (CACAO) for Cyber Security TC are pleased to announce that CACAO Security Playbooks v1.1 is now available for public review and comment. This 15-day review is the second public review for Version 1.1 of this specification.

About the specification draft

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.

The documents and related files are available here:

CACAO Security Playbooks Version 1.1
Committee Specification Draft 02
01 March 2022

Editable source (Authoritative):
https://docs.oasis-open.org/cacao/security-playbooks/v1.1/csd02/security-playbooks-v1.1-csd02.docx
HTML:
https://docs.oasis-open.org/cacao/security-playbooks/v1.1/csd02/security-playbooks-v1.1-csd02.html
PDF:
https://docs.oasis-open.org/cacao/security-playbooks/v1.1/csd02/security-playbooks-v1.1-csd02.pdf
PDF marked with changes since previous public review:
https://docs.oasis-open.org/cacao/security-playbooks/v1.1/csd02/security-playbooks-v1.1-csd02-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.1/csd02/security-playbooks-v1.1-csd02.zip

How to Provide Feedback

OASIS and the CACAO 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 10 March 2022 at 00:00 UTC and ends 24 March 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=cacao).

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/cacao-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 CACAO TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/cacao/

Additional information related to this public review, including a complete publication and review history, 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/cacao/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/cacao/security-playbooks/v1.1/csd02/security-playbooks-v1.1-csd02-public-review-metadata.html

OSLC Tracked Resource Set v3.0 Project Specification 01 approved by the OSLC Open Project

OASIS is pleased to announce that OSLC Tracked Resource Set Version 3.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.

The Tracked Resource Set protocol allows a server to expose a set of resources in a way that allows clients to discover that set of resources, to track additions to and removals from the set, and to track state changes to the resources in the set. The protocol does not assume that clients will dereference the resources, but they could do so. The protocol is suitable for dealing with sets containing a large number of resources, as well as highly active resource sets that undergo continual change. The protocol is HTTP-based and follows RESTful principles.

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 Tracked Resource Set Version 3.0
Project Specification 01
07 February 2022

– OSLC Tracked Resource Set Version 3.0. Part 1: Specification
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps01/tracked-resource-set.html
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps01/tracked-resource-set.pdf

– OSLC Tracked Resource Set Version 3.0. Part 2: Vocabulary
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps01/tracked-resource-set-vocab.html
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps01/tracked-resource-set-vocab.pdf

– OSLC Tracked Resource Set Version 3.0. Part 3: Constraints
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps01/tracked-resource-set-shapes.html
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps01/tracked-resource-set-shapes.pdf

– OSLC Tracked Resource Set RDF Vocabulary definitions file:
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps01/trs-vocab.ttl

– OSLC Tracked Resource Set Resource Shape Constraints definitions file:
https://docs.oasis-open-projects.org/oslc-op/trs/v3.0/ps01/trs-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/trs/v3.0/ps01/trs-v3.0-ps01.zip

Members of the OSLC OP Project Governing Board approved this specification by Special Majority Votes [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/220

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

XACML v3.0 Dynamic Attribute Authority v1.0 approved as a Committee Specification

OASIS is pleased to announce the approval and publication of a new Committee Specification by the members of the eXtensible Access Control Markup Language (XACML) TC [1]:

XACML v3.0 Dynamic Attribute Authority Version 1.0
Committee Specification 01
25 January 2022

Overview

This specification defines a new XACML system component, the Dynamic Attribute Authority, which augments the request context of an XACML authorization request with additional attributes and attribute values that are generated on demand according to a set of rules. The rules are expressed as XACML policies, use obligations to specify the additional attributes and values, and are processed in the normal manner of a Policy Decision Point. This means that a Dynamic Attribute Authority can be readily constructed from existing XACML system components.

A primary use case for the Dynamic Attribute Authority is role enablement, where the dynamic attribute in question is the subject role.

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:

Editable source (Authoritative):
https://docs.oasis-open.org/xacml/xacml-3.0-dyn-attr/v1.0/cs01/xacml-3.0-dyn-attr-v1.0-cs01.docx

HTML:
https://docs.oasis-open.org/xacml/xacml-3.0-dyn-attr/v1.0/cs01/xacml-3.0-dyn-attr-v1.0-cs01.html

PDF:
https://docs.oasis-open.org/xacml/xacml-3.0-dyn-attr/v1.0/cs01/xacml-3.0-dyn-attr-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/xacml/xacml-3.0-dyn-attr/v1.0/cs01/xacml-3.0-dyn-attr-v1.0-cs01.zip

Members of the eXtensible Access Control Markup Language (XACML) 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] eXtensible Access Control Markup Language (XACML) TC
https://www.oasis-open.org/committees/xacml/

[2] Details of public review:
– https://docs.oasis-open.org/xacml/xacml-3.0-dyn-attr/v1.0/csd01/xacml-3.0-dyn-attr-v1.0-csd01-public-review-metadata.html

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

OData Extension for Temporal Data v4.0 from OData TC approved as a Committee Specification

OASIS is pleased to announce that OData Extension for Temporal Data Version 4.0 from the OASIS Open Data Protocol (OData) TC [1] has been approved as an OASIS Committee Specification.

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.

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:

OData Extension for Temporal Data Version 4.0
Committee Specification 01
25 January 2022

Editable source (Authoritative):
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/cs01/odata-temporal-ext-v4.0-cs01.docx
HTML:
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/cs01/odata-temporal-ext-v4.0-cs01.html
PDF:
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/cs01/odata-temporal-ext-v4.0-cs01.pdf
PDF marked with changes since previous public review:
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/cs01/odata-temporal-ext-v4.0-cs01-DIFF.pdf

OData Temporal ABNF Construction Rules Version 4.0:
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/cs01/abnf/odata-temporal-abnf.txt
OData Temporal ABNF Test Cases:
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/cs01/abnf/odata-temporal-testcases.yaml
OData Temporal Vocabulary:
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/cs01/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/cs01/odata-temporal-ext-v4.0-cs01.zip

Members of the OData 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 Data Protocol (OData) TC
https://www.oasis-open.org/committees/odata/

[2] Public reviews:
– Public review metadata record:
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/csd03/odata-temporal-ext-v4.0-csd03-public-review-metadata.html
– Most recent comment resolution log:
https://docs.oasis-open.org/odata/odata-temporal-ext/v4.0/csd03/odata-temporal-ext-v4.0-csd03-comment-resolution-log.xlsx

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

Universal Business Language (UBL) TC publishes JSON representations for UBL 2.1, UBL 2.2, and UBL 2.3

We are pleased to announce the publication of three Committee Notes providing JSON alternative representations of the XML documents included in the Universal Business Language (UBL) OASIS Standards – UBL 2.1, UBL 2.2, and UBL 2.3. These Committee Notes were developed by the members of the OASIS Universal Business Language (UBL) TC [1].

“UBL 2.1 JSON Alternative Representation Version 2.0” supplements the OASIS Universal Business Language version 2.1 release with an alternative expression of the UBL sample XML documents in JSON syntax, and two JSON schema expressions of all 65 XSD schemas in conformance to the OASIS Business Document Naming and Design Rules Version 1.1.

“UBL 2.2 JSON Alternative Representation Version 1.0” supplements the UBL 2.2 release with an alternative expression of the UBL sample XML documents in JSON syntax, and two JSON schema expressions of all of its 81 XSD schemas.

“UBL 2.3 JSON Alternative Representation Version 1.0” supplements UBL 2.3 with an alternative expression of the UBL sample XML documents in JSON syntax, and two JSON schema expressions of all of its 91 XSD schemas.

The documents and related files are available here:

UBL 2.1 JSON Alternative Representation Version 2.0
Committee Note 01
01 December 2021

Editable source (Authoritative):
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/UBL-2.1-JSON-v2.0-cn01.xml
HTML:
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/UBL-2.1-JSON-v2.0-cn01.html
PDF:
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/UBL-2.1-JSON-v2.0-cn01.pdf
JSON legacy examples:
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/json-legacy/
JSON model examples:
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/json-model/
JSON legacy schemas:
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/json-schema-legacy/
JSON model schemas:
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/json-schema-model/
Validation test environment:
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/val/
For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files.
ZIP file:
https://docs.oasis-open.org/ubl/UBL-2.1-JSON/v2.0/cn01/UBL-2.1-JSON-v2.0-cn01.zip
*********************

UBL 2.2 JSON Alternative Representation Version 1.0
Committee Note 01
01 December 2021

Editable source (Authoritative):
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/UBL-2.2-JSON-v1.0-cn01.xml
HTML:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/UBL-2.2-JSON-v1.0-cn01.html
PDF:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/UBL-2.2-JSON-v1.0-cn01.pdf
JSON legacy examples:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/json-legacy/
JSON model examples:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/json-model/
JSON legacy schemas:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/json-schema-legacy/
JSON model schemas:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/json-schema-model/
Validation test environment:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/val/
ZIP file:
https://docs.oasis-open.org/ubl/UBL-2.2-JSON/v1.0/cn01/UBL-2.2-JSON-v1.0-cn01.zip
*********************

UBL 2.3 JSON Alternative Representation Version 1.0
Committee Note 01
01 December 2021

Editable source (Authoritative):
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/UBL-2.3-JSON-v1.0-cn01.xml
HTML:
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/UBL-2.3-JSON-v1.0-cn01.html
PDF:
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/UBL-2.3-JSON-v1.0-cn01.pdf
JSON legacy examples:
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/json-legacy/
JSON model examples:
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/json-model/
JSON legacy schemas:
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/json-schema-legacy/
JSON model schemas:
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/json-schema-model/
Validation test environment:
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/val/
ZIP file:
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/cn01/UBL-2.3-JSON-v1.0-cn01.zip
*********************

Members of the UBL TC approved these Committee Notes by a Full Majority vote on 01 December 2021, as documented in the TC minutes [2].

Our congratulations to all the members of the TC.

Additional references

[1] OASIS Universal Business Language (UBL) TC
https://www.oasis-open.org/committees/ubl/

[2] Approval
https://lists.oasis-open.org/archives/ubl/202112/msg00001.html

No results with the selected filters