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

Specification Overview:

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.1
Committee Specification Draft 01 / Public Review Draft 01
20 December 2018

Editable source (Authoritative):
https://docs.oasis-open.org/virtio/virtio/v1.1/csprd01/tex/
HTML:
https://docs.oasis-open.org/virtio/virtio/v1.1/csprd01/virtio-v1.1-csprd01.html
PDF:
https://docs.oasis-open.org/virtio/virtio/v1.1/csprd01/virtio-v1.1-csprd01.pdf

Example driver listing:
https://docs.oasis-open.org/virtio/virtio/v1.1/csprd01/listings/

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.1/csprd01/virtio-v1.1-csprd01.zip

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 23 January 2019 at 00:00 UTC and ends 21 February 2019 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://www.oasis-open.org/committees/virtio/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode
Non-Assertion Mode

OASIS is pleased to announce that TOSCA Simple Profile in YAML Version 1.2 has been approved by the membership as an OASIS Standard [1].

The ballot was held under the OASIS call for consent procedure [2]. 15 OASIS Member Organizations indicated affirmative consent and no objections were received. Therefore the standard is approved.

To find out more about what TOSCA Simple Profile in YAML Version 1.2 is and why it might matter to you, see the introduction to the specification at https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/cos01/TOSCA-Simple-Profile-YAML-v1.2-cos01.html#_Toc528072899

TC Administration will now prepare and publish the final OASIS Standard and notify members when it is available.

Our congratulations to the members of the TC and to the community of implementers, developers, and users who have brought the work successfully to this milestone

=== Additional information

[1] Ballot:
https://www.oasis-open.org/committees/ballot.php?id=3291

[2] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent

[3] URLs to the latest published version:

TOSCA Simple Profile in YAML Version 1.2
Candidate OASIS Standard 01
10 October 2018

PDF (Authoritative):
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/cos01/TOSCA-Simple-Profile-YAML-v1.2-cos01.pdf

HTML:
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/cos01/TOSCA-Simple-Profile-YAML-v1.2-cos01.html

Editable source:
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/cos01/TOSCA-Simple-Profile-YAML-v1.2-cos01.docx

The Classification of Everyday Living (COEL) TC members [1] have approved submitting the following Candidate OASIS Standard to the OASIS Membership in a call for consent for OASIS Standard:

Classification of Everyday Living Version 1.0
Candidate OASIS Standard 01
18 October 2018

This is a call to the primary or alternate representatives of OASIS Organizational Members to consent or object to this approval. You are welcome to register your consent explicitly on the ballot; however, your consent is assumed unless you register an objection [2]. To register an objection, you must:

1. Indicate your objection on this ballot, and

2. Provide a reason for your objection and/or a proposed remedy to the TC.

You may provide the reason in the comment box or by email to the Technical Committee on its comment mailing list or, if you are a member of the TC, to the TC’s mailing list [2]. If you provide your reason by email, please indicate in the subject line that this is in regard to the Call for Consent.

This Committee Specification was approved by the Technical Committee and was submitted for the required 60-day public review [3]. All requirements of the OASIS TC Process having been met [4], the Candidate OASIS Standard is now submitted to the voting representatives of OASIS Organizational Members.

— Details —

The Call for Consent opens at 10 January 2019 00:00 UTC and closes on 23 January 2019 at 23:59 UTC. You can access the ballot at:

Internal link for voting members: https://www.oasis-open.org/apps/org/workgroup/voting/ballot.php?id=3292

Publicly visible link: https://www.oasis-open.org/committees/ballot.php?id=3292

OASIS members should ensure that their organization’s voting representative responds according to the organization’s wishes. If you do not know the name of your organization’s voting representative is, go to the My Account page at

http://www.oasis-open.org/members/user_tools

then click the link for your Company (at the top of the page) and review the list of users for the name designated as “Primary”.

— Information about the Candidate OASIS Standard and the COEL TC —

The OASIS COEL specification provides a privacy-by-design framework for the collection and processing of behavioral data. It is uniquely suited to the transparent use of dynamic data for personalized digital services, IoT applications where devices are collecting information about identifiable individuals and the coding of behavioral data in identity solutions.

The specification anonymizes personal data at source and maintains a separation of different data types with clearly defined roles & responsibilities for all actors. All behavioral data are defined as event-based packets. Every packet is connected directly to an individual and can contain a summary of the consent they provided for the processing of the data. A combination of a taxonomy of all human behaviors (the COEL model) and the event-based protocol provide a universal template for data portability. Simple interface specifications enforce the separation of roles and provide system-level interoperability.

The TC received 5 Statements of Use from Activinsights, Coelition, Fujitsu, OpenConsent, and University of Exeter [5].

More information about the COEL TC and its work can be found at the TC’s webpage at https://www.oasis-open.org/committees/coel/

URIs
The prose specification document and related files are available here:

Editable source (Authoritative):
http://docs.oasis-open.org/coel/COEL/v1.0/cos01/COEL-v1.0-cos01.docx

HTML:
http://docs.oasis-open.org/coel/COEL/v1.0/cos01/COEL-v1.0-cos01.html

PDF:
http://docs.oasis-open.org/coel/COEL/v1.0/cos01/COEL-v1.0-cos01.pdf

COEL model v1.0:
http://docs.oasis-open.org/coel/COEL/v1.0/cos01/model/coel.json

Schemas for Behavioural Atom Specification and Public Query Interface (PQI):
http://docs.oasis-open.org/coel/COEL/v1.0/cos01/schemas/

Distribution ZIP files:

For your convenience, OASIS provides a complete package of the prose specifications and related files in a ZIP distribution file. You can download the ZIP file here:

http://docs.oasis-open.org/coel/COEL/v1.0/cos01/COEL-v1.0-cos01.zip

— Additional information —

[1] Classification of Everyday Living (COEL) TC
https://www.oasis-open.org/committees/coel/

TC IPR page
https://www.oasis-open.org/committees/coel/ipr.php

[2] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent

COEL TC comment mailing list: coel-comment@lists.oasis-open.org (You must be subscribed to send to this list. To subscribe, see https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=coel.)

COEL main mailing list: coel@lists.oasis-open.org

[3] Public reviews:

– 60-day public review, 10 November 2018:
https://lists.oasis-open.org/archives/members/201811/msg00001.html
– No comments received

– 15-day public review, 09 May 2018:
https://lists.oasis-open.org/archives/members/201805/msg00004.html
– Comment resolution log:
http://docs-staging.oasis-open.org/ztest/coel/COEL/v1.0/csprd03/COEL-v1.0-csprd03-comment-resolution-log.txt

– 15-day public review, 11 December 2017:
https://lists.oasis-open.org/archives/members/201712/msg00002.html
– Comment resolution log:
http://docs.oasis-open.org/coel/COEL/v1.0/csprd02/COEL-v1.0-csprd02-comment-resolution-log.xlsx

– 30-day public review, 10 November 2016:
https://lists.oasis-open.org/archives/members/201611/msg00000.html
– Comment resolution log:
http://docs.oasis-open.org/coel/COEL/v1.0/csprd01/COEL-v1.0-csprd01-comment-resolution-log.xlsx

[4] Candidate OASIS Standard Special Majority Vote:
https://www.oasis-open.org/committees/ballot.php?id=3262

[5] Statements of use

Coelition: https://www.oasis-open.org/apps/org/workgroup/coel/email/archives/201808/msg00002.html

Activinsights: https://www.oasis-open.org/apps/org/workgroup/coel/email/archives/201807/msg00008.html

Fujitsu: https://www.oasis-open.org/apps/org/workgroup/coel/email/archives/201808/msg00010.html

University of Exeter: https://www.oasis-open.org/apps/org/workgroup/coel/email/archives/201808/msg00004.html

OpenConsent: https://www.oasis-open.org/apps/org/workgroup/coel/email/archives/201808/msg00003.html

OASIS and the OASIS OSLC Lifecycle Integration Core (OSLC Core) TC are pleased to announce that OSLC Query Version 3.0 is now available for public review and comment.

Information Technology enterprises are constantly looking for more efficient development processes. They want integration of their software or hardware development tools regardless of vendor, but this level of integration is challenging to achieve. In order to enable integration between various tools, Open Services for Lifecycle Collaboration (OSLC) seeks to define a sufficient supporting architecture that is loosely coupled, minimal, and standardized. It is based on World Wide Web and Linked Data principles, and provides a cohesive set of specifications that can enable products, services, and other distributed network resources to interoperate successfully.

OSLC Query provides a mechanism for a client to query or search for RDF resources that match a given criteria. The response to a successful query includes the RDF of a query result container that references the member resources found by the query, and optionally includes selected properties of each member resource.

The documents and related files are available here:

OSLC Query Version 3.0
Committee Specification Draft 01 / Public Review Draft 01
29 November 2018

HTML (Authoritative):
https://docs.oasis-open.org/oslc-core/oslc-query/v3.0/csprd01/oslc-query-v3.0-csprd01.html
PDF:
https://docs.oasis-open.org/oslc-core/oslc-query/v3.0/csprd01/oslc-query-v3.0-csprd01.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/oslc-core/oslc-query/v3.0/csprd01/oslc-query-v3.0-csprd01.zip

How to Provide Feedback

OASIS and the OASIS OSLC Lifecycle Integration Core (OSLC Core) 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 09 January 2019 at 00:00 UTC and ends 07 February 2019 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=oslc-core).

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

========== Additional references:

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

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

The OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC members [1] have approved submitting the following Candidate OASIS Standard to the OASIS Membership in a call for consent for OASIS Standard:

TOSCA Simple Profile in YAML Version 1.2
Candidate OASIS Standard 01
10 October 2018

This is a call to the primary or alternate representatives of OASIS Organizational Members to consent or object to this approval. You are welcome to register your consent explicitly on the ballot; however, your consent is assumed unless you register an objection. To register an objection, you must:

1. Indicate your objection on this ballot, and

2. Provide a reason for your objection and/or a proposed remedy to the TC.

You may provide the reason in the comment box or by email to the Technical Committee on its comment mailing list or, if you are a member of the TC, to the TC’s mailing list [2]. If you provide your reason by email, please indicate in the subject line that this is in regard to the Call for Consent.

This Committee Specification was approved by the Technical Committee and was submitted for the required 60-day public review [3]. All requirements of the OASIS TC Process having been met [4][5], the Candidate OASIS Standard is now submitted to the voting representatives of OASIS Organizational Members.

— Details —

The Call for Consent opens at 04 January 2019 at 00:00 UTC and closes on 17 January 2019 at 23:59 UTC. You can access the ballot at:

Internal link for voting members: https://www.oasis-open.org/apps/org/workgroup/voting/ballot.php?id=3291

Publicly visible link: https://www.oasis-open.org/committees/ballot.php?id=3291

OASIS members should ensure that their organization’s voting representative responds according to the organization’s wishes. If you do not know the name of your organization’s voting representative is, go to the My Account page at

http://www.oasis-open.org/members/user_tools

then click the link for your Company (at the top of the page) and review the list of users for the name designated as “Primary”.

The prose specification document and related files are available here:

PDF (Authoritative):
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/cos01/TOSCA-Simple-Profile-YAML-v1.2-cos01.pdf

HTML:
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/cos01/TOSCA-Simple-Profile-YAML-v1.2-cos01.html

Editable source:
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/cos01/TOSCA-Simple-Profile-YAML-v1.2-cos01.docx

Distribution ZIP files:

For your convenience, OASIS provides a complete package of the prose specifications and related files in a ZIP distribution file. You can download the ZIP file here:

http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/cos01/TOSCA-Simple-Profile-YAML-v1.2-cos01.zip

— Additional information —

[1] OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
https://www.oasis-open.org/committees/tosca/

TC IPR page
https://www.oasis-open.org/committees/tosca/ipr.php

[2] TOSCA comment mailing list: tosca-comment@lists.oasis-open.org
(You must be subscribed to send to this list. To subscribe, see https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=tosca.)

TOSCA main mailing list: tosca@lists.oasis-open.org

[3] Candidate OASIS Standard Special Majority Vote:
https://www.oasis-open.org/committees/ballot.php?id=3260

[4] Public reviews:

– 60-day public review, 26 October 2018:
https://lists.oasis-open.org/archives/members/201810/msg00006.html
– No comments received

– 30-day public review, 19 January 2018:
https://lists.oasis-open.org/archives/members/201801/msg00006.html
– Comment resolution log:
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/csprd01/TOSCA-Simple-Profile-YAML-v1.2-csprd01-comment-resolution-log.xlsx

[5] Statements of Use:

XLAB: https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201809/msg00014.html

AT&T: https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201808/msg00010.html

Ubicity Corp: https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201808/msg00005.html

OASIS is pleased to announce publication of “STIX/TAXII 2.0 Interoperability Test Document: Part 1 Version 1.1” and “STIX/TAXII 2.0 Interoperability Test Document: Part 2 Version 1.0”, Committee Notes from the members of the OASIS Cyber Threat Intelligence (CTI) TC [1].

These test documents provide detailed requirements on how producers of products within the threat intelligence ecosystem may demonstrate and self-certify that their software is interoperable with other systems implementing STIX/TAXII 2.0.

There are six personas detailed in Part 1 of the Interoperability Test Document, which focuses primarily on conformity with STIX 2.0. These are: Data Feed Provider (DFP), Threat Intelligence Platform (TIP), Threat Mitigation System (TMS), Threat Detection System (TDS), Security Incident and Event Management (SIEM), and Threat Intelligence Sink (TIS). Part 1 defines tests of the following test cases: indicator sharing, sighting sharing, versioning, data markings, custom objects and properties, and course of action sharing.

There are eight personas detailed in Part 2 of the Interoperability Test Document. These include the six listed for Part 1, plus TAXII Feed (TXF) and TAXII Server (TXS). Part 2 defines tests of the following test cases: common connection, basic data sharing, and basic threat intelligence collaboration.

The Committee Notes are available here:

STIX/TAXII 2.0 Interoperability Test Document: Part 1 Version 1.1
Committee Note 01
16 August 2018

Editable source (Authoritative):
https://docs.oasis-open.org/cti/stix-taxii-2-interop-p1/v1.1/cn01/stix-taxii-2-interop-p1-v1.1-cn01.docx
HTML:
https://docs.oasis-open.org/cti/stix-taxii-2-interop-p1/v1.1/cn01/stix-taxii-2-interop-p1-v1.1-cn01.html
PDF:
https://docs.oasis-open.org/cti/stix-taxii-2-interop-p1/v1.1/cn01/stix-taxii-2-interop-p1-v1.1-cn01.pdf
ZIP (complete package of the Committee Note):
https://docs.oasis-open.org/cti/stix-taxii-2-interop-p1/v1.1/cn01/stix-taxii-2-interop-p1-v1.1-cn01.zip

STIX/TAXII 2.0 Interoperability Test Document: Part 2 Version 1.0
Committee Note 01
05 November 2018

Editable source (Authoritative):
https://docs.oasis-open.org/cti/stix-taxii-2-interop-p2/v1.0/cn01/stix-taxii-2-interop-p2-v1.0-cn01.docx
HTML:
https://docs.oasis-open.org/cti/stix-taxii-2-interop-p2/v1.0/cn01/stix-taxii-2-interop-p2-v1.0-cn01.html
PDF:
https://docs.oasis-open.org/cti/stix-taxii-2-interop-p2/v1.0/cn01/stix-taxii-2-interop-p2-v1.0-cn01.pdf
ZIP:
https://docs.oasis-open.org/cti/stix-taxii-2-interop-p2/v1.0/cn01/stix-taxii-2-interop-p2-v1.0-cn01.zip

Members of the CTI TC approved these Committee Notes by Full Majority electronic ballots on 16 August and 05 November 2018 [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/ballot.php?id=3230
https://www.oasis-open.org/committees/ballot.php?id=3263

OASIS and the OASIS Cyber Threat Intelligence TC are pleased to announce that TAXII™ Version 2.1 is now available for public review and comment.

Trusted Automated Exchange of Intelligence Information (TAXII) is an application layer protocol used to exchange cyber threat intelligence (CTI) over HTTPS. It enables organizations to share CTI by defining an API that aligns with common sharing models.

TAXII is specifically designed to support the exchange of CTI represented in STIX. As such, the examples and some features in the specification are intended to align with STIX. This does not mean TAXII cannot be used to share data in other formats; it is designed for STIX, but is not limited to STIX.

The documents and related files are available here:

TAXII™ Version 2.1
Committee Specification Draft 02 / Public Review Draft 01
15 December 2018

Editable source (Authoritative):
http://docs.oasis-open.org/cti/taxii/v2.1/csprd01/taxii-v2.1-csprd01.docx
HTML:
http://docs.oasis-open.org/cti/taxii/v2.1/csprd01/taxii-v2.1-csprd01.html
PDF:
http://docs.oasis-open.org/cti/taxii/v2.1/csprd01/taxii-v2.1-csprd01.pdf

For your convenience, OASIS provides a complete package of the prose document and any related files in ZIP distribution files. You can download the ZIP file at:
http://docs.oasis-open.org/cti/taxii/v2.1/csprd01/taxii-v2.1-csprd01.zip

How to Provide Feedback

OASIS and the OASIS Cyber Threat Intelligence (CTI) 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 22 December 2018 at 00:00 UTC and ends 21 January 2019 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=cti).

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/cti-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 CTI TC can be found at the TC’s public home page:

https://www.oasis-open.org/committees/cti/

========== Additional references:

[1] http://www.oasis-open.org/who/intellectualproperty.php

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

OASIS is pleased to announce that “XACML REST Profile Version 1.1” and “JSON Profile of XACML 3.0 Version 1.1” from the OASIS eXtensible Access Control Markup Language (XACML) TC have been approved as OASIS Committee Specifications.

XACML is an OASIS Standard which describes both a policy language and an access control decision request/response language (both defined in XML). The policy language is used to describe general access control requirements, and has standard extension points for defining new functions, data types, combining logic, etc. The request/response language lets you form a query to ask whether or not a given action should be allowed, and interpret the result. XACML v3.0 is an international standard (ITU-T X.1144), approved by the International Telecommunications Union – Telecommunication Standardization Sector (ITU-T).

The REST Profile specification defines a profile for the use of XACML in a RESTful architecture.

The JSON profile proposes a standardized interface between a policy enforcement point and a policy decision point using JSON, leveraging the decision request and response structure specified in the core XACML standard.

These Committee Specifications are OASIS deliverables, completed and approved by the TC and fully ready for testing and implementation.
The prose specifications and related files are available here:

XACML REST Profile Version 1.1
Committee Specification 01
05 December 2018

Editable source: (Authoritative)
https://docs.oasis-open.org/xacml/xacml-rest/v1.1/cs01/xacml-rest-v1.1-cs01.doc
HTML:
https://docs.oasis-open.org/xacml/xacml-rest/v1.1/cs01/xacml-rest-v1.1-cs01.html
PDF:
https://docs.oasis-open.org/xacml/xacml-rest/v1.1/cs01/xacml-rest-v1.1-cs01.pdf
ZIP: (complete package of the specification documents and any related files)
https://docs.oasis-open.org/xacml/xacml-rest/v1.1/cs01/xacml-rest-v1.1-cs01.zip

JSON Profile of XACML 3.0 Version 1.1
Committee Specification 01
05 December 2018

Editable source: (Authoritative)
https://docs.oasis-open.org/xacml/xacml-json-http/v1.1/cs01/xacml-json-http-v1.1-cs01.doc
HTML:
https://docs.oasis-open.org/xacml/xacml-json-http/v1.1/cs01/xacml-json-http-v1.1-cs01.html
PDF:
https://docs.oasis-open.org/xacml/xacml-json-http/v1.1/cs01/xacml-json-http-v1.1-cs01.pdf
ZIP: (complete package of the specification documents and any related files)
https://docs.oasis-open.org/xacml/xacml-json-http/v1.1/cs01/xacml-json-http-v1.1-cs01.zip

Members of the XACML TC [1] approved these specifications by Special Majority Votes. The specifications had been released for public review as required by the TC Process [2]. The vote to approve as Committee Specifications passed [3], and the documents are 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 eXtensible Access Control Markup Language (XACML) TC
https://www.oasis-open.org/committees/xacml/

[2] Public reviews:

* 30-day public reviews, 20 September 2018:
https://lists.oasis-open.org/archives/xacml/201809/msg00013.html
– Comment resolution logs:
http://docs.oasis-open.org/xacml/xacml-rest/v1.1/csprd01/xacml-rest-v1.1-csprd01-comment-resolution-log.txt
http://docs.oasis-open.org/xacml/xacml-json-http/v1.1/csprd01/xacml-json-http-v1.1-csprd01-comment-resolution-log.txt

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

We are pleased to announce that Electronic Court Filing Version 5.0 from the LegalXML Electronic Court Filing TC [1] is now available for public review and comment. This is the third public review for ECF v5.0.

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. Version 5.0 provides a number of enhancements including:
– Support for scheduling of court hearings using WS-Calendar
– Limited electronic service of process to process servers and registered agents
– New Document Stamp and operations support retrieval of case information required for stamping
– New Court Policy MDE to better support electronic filing systems with multiple FilingReview MDEs
– Support for cancellation of filings
– Conformance with the 4.0 version of the National Information Exchange Model (NIEM), a national standard for information sharing, new NIEM domains including Biometrics and Human Services
– Conformance with the NIEM Code Lists specification version 1.0 and the representation of all ECF code lists in Genericode format.
– Conformance with the 2.2 version of the Universal Business Language (UBL).
– Better management of extensions through NIEM augmentations.
– Deprecated content references (e.g. referring to related entities with common identifiers) in favor or element references (e.g. referring to related elements with structures:ref attributes) as described in Reference Rules.
– Clarifications and improvements throughout the specification based on feedback from implementers of the ECF 4.0 and 4.01 specifications.

Version 5.0 does not assume that prior versions will be deprecated. However, it is not backward-compatible and applications using the ECF 3.0, 3.01 and 3.1, 4.0 and 4.01 specifications will not interoperate successfully with applications using this version.

The documents and related files are available here:

Electronic Court Filing Version 5.0
Committee Specification Draft 03 / Public Review Draft 03
03 December 2018

Editable source (Authoritative):
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd03/ecf-v5.0-csprd03.docx
HTML:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd03/ecf-v5.0-csprd03.html
PDF:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd03/ecf-v5.0-csprd03.pdf
XML schemas and Genericode code lists:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd03/schema/
XML example messages:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd03/examples/
Model and documentation:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd03/model/
Change Log of ECF Version 4.0 and Version 5.0:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd03/Change-Log.doc
ECF Version 5.0 UML model artifacts:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd03/uml/

For your convenience, OASIS provides a complete package of the prose document and any related files in ZIP distribution files. You can download the ZIP file at:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd03/ecf-v5.0-csprd03.zip

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 review starts 13 December 2018 at 00:00 UTC and ends 27 December 2018 at 23:59 UTC.

This specification was previously submitted for public review [2]. This 15-day review is limited in scope to changes made from the previous review. Changes are highlighted in red-lined file included in the package [3].

Comments may be submitted to the TC by by following the instructions located at:
https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=legalxml-courtfiling.

Feedback submitted by TC non-members for this work 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 [4] applicable especially [5] 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] Previous public reviews:
– 60-day public review:
https://lists.oasis-open.org/archives/legalxml-courtfiling/201709/msg00018.html
– Comment resolution log:
http://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd01/ecf-v5.0-csprd01-comment-resolution-log.xlsx
– 15-day public review:
https://lists.oasis-open.org/archives/legalxml-courtfiling/201810/msg00014.html
– Comment resolution log:
http://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd02/ecf-v5.0-csprd02-comment-resolution-log.xlsx
[3] Red-lined version:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd03/ecf-v5.0-csprd03-DIFF.pdf
[4] https://www.oasis-open.org/policies-guidelines/ipr
[5] 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

OASIS is pleased to announce the publication of “Lightweight DITA: An Introduction,” a Committee Note from the members of the OASIS Darwin Information Typing Architecture (DITA) TC [1].

Lightweight DITA (LwDITA) is a simplified version of the Darwin Information Typing Architecture (DITA). In comparison to DITA 1.3, it has a smaller element type and attribute set, stricter content models, and a reduced feature set. It also defines mappings between XML, HTML5, and Markdown so that authors can collaborate and publish across different markup languages.

LwDITA is a work in progress. The Committee Note outlines the current plans in order to gain design clarity and receive feedback from potential users. Details may well change between the publication of this CN and release of Lightweight DITA as an OASIS specification.

The files and associated components can be accessed at:

Lightweight DITA: An Introduction Version 1.0
Committee Note 02
30 December 2018

HTML:
http://docs.oasis-open.org/dita/LwDITA/v1.0/cn02/LwDITA-v1.0-cn02.html

PDF:
http://docs.oasis-open.org/dita/LwDITA/v1.0/cn02/LwDITA-v1.0-cn02.pdf

DITA source:
http://docs.oasis-open.org/dita/LwDITA/v1.0/cn02/LwDITA-v1.0-cn02-DITA-source.zip

Grammar files:
http://docs.oasis-open.org/dita/LwDITA/v1.0/cn02/LwDITA-v1.0-cn02-grammars.zip

Sample LwDITA document:
http://docs.oasis-open.org/dita/LwDITA/v1.0/cn02/LwDITA-v1.0-cn02-samples.zip

Distribution ZIP files

For your convenience, OASIS provides a complete package of the Committee Note that you can download here:

http://docs.oasis-open.org/dita/LwDITA/v1.0/cn02/LwDITA-v1.0-cn02.zip

Members of the DITA TC approved this Committee Note by a Full Majority vote on 30 December 2018 as documented in the TC minutes [2].

Our congratulations to all the members of the TC on this publication.

========== Additional references:

[1] OASIS Darwin Information Typing Architecture (DITA) TC
https://www.oasis-open.org/committees/dita/

[2] Approval
https://lists.oasis-open.org/archives/dita/201811/msg00002.html

OASIS and the OASIS LegalDocumentML (LegalDocML) TC [1] are pleased to announce that Akoma Ntoso Naming Convention Version 1.0 is now available for public review and comment.

For governments, makers of legal information systems, legal publishers and others in governmental and legal fields, Akoma Ntoso provides a framework for creating human and machine-readable documents such as legislation, debate records, minutes, judgments, etc. In doing so, it helps build a strong foundation for “open access” to government information.

This specification provides the naming convention for defining IRIs and ids related to the Akoma Ntoso XML standard. Identifiers are the main way Akoma Ntoso identifies fragments and parts of the document in an unambiguous form. Because any substructure in a legal document may become a destination, identifiers are useful for all parts of a document.

Akoma Ntoso Naming Convention Version 1.0 has been approved as a Candidate OASIS Standard (COS) [2]. The COS now enters a 60-day public review period in preparation for a member ballot to consider its approval as an OASIS Standard.

The TC has received 3 Statements of Use from the Food and Agriculture Organization of the United Nations (FAO), Xcential Corporation, and CIRSFID [3].

The candidate specification and related files are available here:

Akoma Ntoso Naming Convention Version 1.0
Candidate OASIS Standard 01
03 December 2018

HTML (Authoritative):
https://docs.oasis-open.org/legaldocml/akn-nc/v1.0/cos01/akn-nc-v1.0-cos01.html

PDF:
https://docs.oasis-open.org/legaldocml/akn-nc/v1.0/cos01/akn-nc-v1.0-cos01.pdf

Editable source:
https://docs.oasis-open.org/legaldocml/akn-nc/v1.0/cos01/akn-nc-v1.0-cos01.doc

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/legaldocml/akn-nc/v1.0/cos01/akn-nc-v1.0-cos01.zip

Public Review Period:

The 60-day public review starts 07 December 2018 at 00:00 UTC and ends 04 February 2019 at 23:59 UTC.

This is an open invitation to comment. OASIS solicts feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility as explained in the instructions located via the button labeled “Send A Comment” at the top of the TC public home page, or directly at:

https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=legaldocml

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

http://lists.oasis-open.org/archives/legaldocml-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 of “Akoma Ntoso Naming Convention Version 1.0,” we call your attention to the OASIS IPR Policy [4] applicable especially [5] 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.

==============

[1] OASIS LegalDocumentML (LegalDocML) TC
https://www.oasis-open.org/committees/legaldocml/

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

[3] Statements of Use:

– Food and Agriculture Organization of the United Nations (FAO): https://www.oasis-open.org/apps/org/workgroup/legaldocml/download.php/64234/latest/1.Statement%20of%20use%20-%20FAO_letter_20180

– Xcential Corporation: https://www.oasis-open.org/apps/org/workgroup/legaldocml/download.php/64235/latest/2.StatementOfUse-Xcential-nc.pdf

– CIRSFID, University of Bologna: https://www.oasis-open.org/apps/org/workgroup/legaldocml/download.php/64236/latest/3.StatementOfUse-CIRSFID-UNIBO-nc.pdf

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

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

The OASIS Cross-Enterprise Security and Privacy Authorization (XSPA) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

Cross-Enterprise Security and Privacy Authorization (XSPA) Profile of SAML v2.0 for Healthcare Version 2.0
Committee Specification Draft 03 / Public Review Draft 03
26 November 2018

What is the XSPA Profile of SAML and why is it important?

The XSPA profile defines a set of SAML attributes and corresponding vocabularies for healthcare information exchange applications.

The core use-cases are the cross-enterprise exchange of protected data objects from a Service Provider (SP) to a Service Consumer (SC). In the scenarios, the request includes SAML attribute assertions that vouch for the identity of the requesting Principal and other attributes that are consequential in making the access control decision at the SP’s side.

In addition to the main use-cases, the attributes name and values can be used in some other scenarios, such as including SAML Assertions to vouch for some of SP’s organizational attributes, or carrying the identity attributes of the signer of a data object.

Public Review Period:

The public review starts 04 December 2018 at 00:00 UTC and ends 18 December 2018 at 11:59 UTC. The specification was previously submitted for public review [2].

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

URIs:
The prose specification document and related files are available here:
Editable source (Authoritative):
https://docs.oasis-open.org/xspa/saml-xspa/v2.0/csprd03/saml-xspa-v2.0-csprd03.docx
HTML:
https://docs.oasis-open.org/xspa/saml-xspa/v2.0/csprd03/saml-xspa-v2.0-csprd03.html
PDF:
https://docs.oasis-open.org/xspa/saml-xspa/v2.0/csprd03/saml-xspa-v2.0-csprd03.pdf

ZIP distribution files (complete):
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/xspa/saml-xspa/v2.0/csprd03/saml-xspa-v2.0-csprd03.zip

Additional information about this specification and the XSPA TC may be found on the TC’s public home page located at:
https://www.oasis-open.org/committees/xspa/

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be accessed via the button labeled “Send A Comment” at the top of the TC public home page, or directly at:
https://www.oasis-open.org/committees/comments/form.php?wg_abbrev=xspa

Feedback submitted by TC non-members for this work and for other work of this TC is publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/xspa-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 of ‘Cross-Enterprise Security and Privacy Authorization (XSPA) Profile of SAML v2.0 for Healthcare Version 2.0’, we call your attention to the OASIS IPR Policy [3] applicable especially [4] 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 references:

[1] OASIS Cross-Enterprise Security and Privacy Authorization (XSPA) TC
https://www.oasis-open.org/committees/xspa/

[2] Previous public reviews:
– 30-day public review, 29 April 2014:
https://lists.oasis-open.org/archives/members/201404/msg00010.html
– Comment resolution log:
https://docs.oasis-open.org/xspa/saml-xspa/v2.0/csprd01/saml-xspa-v2.0-csprd01-comment-resolution-log.xls
– 15-day public review, 27 March 2017:
https://lists.oasis-open.org/archives/xspa/201703/msg00006.html
– Comment resolution log:
https://docs.oasis-open.org/xspa/saml-xspa/v2.0/csprd02/saml-xspa-v2.0-csprd02-comment-resolution-log.txt

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

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