Members of the OASIS eXtensible Access Control Markup Language (XACML) TC [1] have recently approved Special Majority Ballots [2] to advance REST Profile of XACML v3.0 Version 1.0 and JSON Profile of XACML 3.0 Version 1.0 as Candidate OASIS Standards (COSs). These COSs now enter a 60-day public review period in preparation for the member call for consent for OASIS Standards.

The REST Profile specification defines a profile for the use of XACML in a RESTful architecture. The TC received 4 Statements of Use from Oracle, EMC, Axiomatics, and NextLabs [3].

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. The TC received 3 Statements of Use from ViewDS Identity Solutions, Axiomatics AB, and NextLabs [4].

The Candidate OASIS Standards are available at:

– REST Profile of XACML v3.0 Version 1.0
Candidate OASIS Standard 01
12 October 2017

Editable source (Authoritative):
http://docs.oasis-open.org/xacml/xacml-rest/v1.0/cos01/xacml-rest-v1.0-cos01.doc

HTML:
http://docs.oasis-open.org/xacml/xacml-rest/v1.0/cos01/xacml-rest-v1.0-cos01.html

PDF:
http://docs.oasis-open.org/xacml/xacml-rest/v1.0/cos01/xacml-rest-v1.0-cos01.pdf

– JSON Profile of XACML 3.0 Version 1.0
Candidate OASIS Standard 01
12 October 2017

Editable source (Authoritative):
http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/cos01/xacml-json-http-v1.0-cos01.doc

HTML:
http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/cos01/xacml-json-http-v1.0-cos01.html

PDF:
http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/cos01/xacml-json-http-v1.0-cos01.pdf

ZIP distribution file (complete):

For your convenience, OASIS also provides ZIP files of each of the COS. You can obtain the ZIP files at:

REST Profile of XACML 3.0:
http://docs.oasis-open.org/xacml/xacml-rest/v1.0/cos01/xacml-rest-v1.0-cos01.zip

JSON Profile of XACML 3.0:
http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/cos01/xacml-json-http-v1.0-cos01.zip

Public Review Period:

This 60-day public review starts 08 November 2017 at 00:00 UTC and ends 06 January 2017 at 23:59 UTC.

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.

Additional information about the specification and the XACML TC may be found at the TC’s public home page:

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

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=xacml

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/xacml-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 of “REST Profile of XACML 3.0 V1.0″ and “JSON Profile of XACML 3.0 V1.0,” we call your attention to the OASIS IPR Policy [5] applicable especially [6] 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 eXtensible Access Control Markup Language (XACML) TC
https://www.oasis-open.org/committees/xacml/

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

[3] Statements of Use for REST Profile of XACML 3.0

Oracle: https://lists.oasis-open.org/archives/xacml/201304/msg00009.html

EMC Corp: https://lists.oasis-open.org/archives/xacml/201304/msg00010.html

Axiomatics: https://lists.oasis-open.org/archives/xacml/201305/msg00023.html

NextLabs: https://lists.oasis-open.org/archives/xacml/201708/msg00013.html

[4] Statements of Use for JSON Profile of XACML 3.0

ViewDS Identity Solutions: https://lists.oasis-open.org/archives/xacml/201707/msg00011.html

Axiomatics AB: https://lists.oasis-open.org/archives/xacml/201707/msg00014.html

NextLabs: https://lists.oasis-open.org/archives/xacml/201708/msg00013.html

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

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

OASIS is pleased to announce that Universal Business Language Version 2.2 from the OASIS Universal Business Language TC [1] is now available for public review and comment.

The Universal Business Language (UBL) is an open library of standard electronic XML business documents for procurement and transportation such as purchase orders, invoices, transport logistics and waybills.

Version 2.2 is completely backward-compatible with UBL 2.0. This second release of V2.2 has been updated based on feedback from the previous public review. The comments received in that review and their resolution can be found at http://docs.oasis-open.org/ubl/csprd01-UBL-2.2/csprd01-UBL-2.2-comment-resolution-log.ods. UBL 2.2 updates are also described in the specification at http://docs.oasis-open.org/ubl/csprd02-UBL-2.2/UBL-2.2.html#S-MINOR-REVISION-UBL-2.2

The documents and related files are available here:

Universal Business Language Version 2.2
Committee Specification Draft 02 / Public Review Draft 02
01 November 2017

Editable source (Authoritative):
http://docs.oasis-open.org/ubl/csprd02-UBL-2.2/UBL-2.2.xml

HTML:
http://docs.oasis-open.org/ubl/csprd02-UBL-2.2/UBL-2.2.html

PDF:
http://docs.oasis-open.org/ubl/csprd02-UBL-2.2/UBL-2.2.pdf

Code lists for constraint validation:
http://docs.oasis-open.org/ubl/csprd02-UBL-2.2/cl/

Context/value Association files for constraint validation:
http://docs.oasis-open.org/ubl/csprd02-UBL-2.2/cva/

Document models of information bundles:
http://docs.oasis-open.org/ubl/csprd02-UBL-2.2/mod/

Default validation test environment:
http://docs.oasis-open.org/ubl/csprd02-UBL-2.2/val/

XML examples:
http://docs.oasis-open.org/ubl/csprd02-UBL-2.2/xml/

Annotated XSD schemas:
http://docs.oasis-open.org/ubl/csprd02-UBL-2.2/xsd/

Runtime XSD schemas:
http://docs.oasis-open.org/ubl/csprd02-UBL-2.2/xsdrt/

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

http://docs.oasis-open.org/ubl/csprd02-UBL-2.2/UBL-2.2.zip

How to Provide Feedback

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

This public review starts 08 November 2017 at 00:00 UTC and ends 07 December 2017 at 11:59 UTC.

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

Comments on the work may be submitted to the TC by following the instructions located at:

http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=ubl

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

http://lists.oasis-open.org/archives/ubl-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 the public review of these works, 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 UBL TC may be found on the TC’s public home page.

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

[1] OASIS Universal Business Language TC
http://www.oasis-open.org/committees/ubl/

Approval: https://lists.oasis-open.org/archives/ubl/201710/msg00001.html

[2] Previous public reviews:

– 45-day public review, 01 February 2017:
https://lists.oasis-open.org/archives/members/201701/msg00002.html
– Comment resolution log:
http://docs.oasis-open.org/ubl/csprd01-UBL-2.2/csprd01-UBL-2.2-comment-resolution-log.ods

[3] Red-lined copy of the specification:

http://docs.oasis-open.org/ubl/csprd02-UBL-2.2/UBL-2.2-csprd02-DIFF.pdf

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

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

OASIS and the Cyber Threat Intelligence (CTI) Technical Committee are pleased to announce the publication of STIX Version 2.0 and TAXII Version 2.0 as Committee Specifications.

The Cyber Threat Intelligence (CTI) TC is developing information representations and protocols to help industries, organizations, and governments model, analyze, and share cyber threat intelligence.

STIX – Structured Threat Information Expression – is a language and serialization format used to exchange cyber threat intelligence (CTI). STIX enables organizations to share CTI with one another in a consistent and machine readable manner, allowing security communities to better understand what computer-based attacks they are most likely to see and to anticipate and/or respond to those attacks faster and more effectively. STIX is designed to improve many different capabilities, such as collaborative threat analysis, automated threat exchange, automated detection and response, and more.

STIX Version 2.0 has been significantly redesigned and, as a result, omits some of the objects and properties defined in STIX 1.2.1. The objects chosen for inclusion in STIX V2.0 represent a minimally viable product (MVP) that fulfills basic consumer and producer requirements for CTI sharing. Objects and properties not included in STIX 2.0, but deemed necessary by the community, will be included in future releases.

TAXII – Trusted Automated Exchange of Intelligence Information – 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.

These Committee Specifications are OASIS deliverables, completed and approved by the TC and fully ready for testing and implementation.

The specifications and related files are available here:

– STIX Version 2.0
Committee Specification 01
19 July 2017

* Part 1: STIX Core Concepts
Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v2.0/cs01/part1-stix-core/stix-v2.0-cs01-part1-stix-core.docx

HTML:
http://docs.oasis-open.org/cti/stix/v2.0/cs01/part1-stix-core/stix-v2.0-cs01-part1-stix-core.html

PDF:
http://docs.oasis-open.org/cti/stix/v2.0/cs01/part1-stix-core/stix-v2.0-cs01-part1-stix-core.pdf

* Part 2: STIX Objects
Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v2.0/cs01/part2-stix-objects/stix-v2.0-cs01-part2-stix-objects.docx

HTML:
http://docs.oasis-open.org/cti/stix/v2.0/cs01/part2-stix-objects/stix-v2.0-cs01-part2-stix-objects.html

PDF:
http://docs.oasis-open.org/cti/stix/v2.0/cs01/part2-stix-objects/stix-v2.0-cs01-part2-stix-objects.pdf

* Part 3: Cyber Observable Core Concepts
Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v2.0/cs01/part3-cyber-observable-core/stix-v2.0-cs01-part3-cyber-observable-core.docx

HTML:
http://docs.oasis-open.org/cti/stix/v2.0/cs01/part3-cyber-observable-core/stix-v2.0-cs01-part3-cyber-observable-core.html

PDF:
http://docs.oasis-open.org/cti/stix/v2.0/cs01/part3-cyber-observable-core/stix-v2.0-cs01-part3-cyber-observable-core.pdf

* Part 4: Cyber Observable Objects
Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v2.0/cs01/part4-cyber-observable-objects/stix-v2.0-cs01-part4-cyber-observable-objects.docx

HTML:
http://docs.oasis-open.org/cti/stix/v2.0/cs01/part4-cyber-observable-objects/stix-v2.0-cs01-part4-cyber-observable-objects.html

PDF:
http://docs.oasis-open.org/cti/stix/v2.0/cs01/part4-cyber-observable-objects/stix-v2.0-cs01-part4-cyber-observable-objects.pdf

* Part 5: Patterning
Editable source (Authoritative):
http://docs.oasis-open.org/cti/stix/v2.0/cs01/part5-stix-patterning/stix-v2.0-cs01-part5-stix-patterning.docx

HTML:
http://docs.oasis-open.org/cti/stix/v2.0/cs01/part5-stix-patterning/stix-v2.0-cs01-part5-stix-patterning.html

PDF:
http://docs.oasis-open.org/cti/stix/v2.0/cs01/part5-stix-patterning/stix-v2.0-cs01-part5-stix-patterning.pdf

– TAXII Version 2.0
Committee Specification 01
19 July 2017

Editable source (Authoritative):
http://docs.oasis-open.org/cti/taxii/v2.0/cs01/taxii-v2.0-cs01.docx

HTML:
http://docs.oasis-open.org/cti/taxii/v2.0/cs01/taxii-v2.0-cs01.html

PDF:
http://docs.oasis-open.org/cti/taxii/v2.0/cs01/taxii-v2.0-cs01.pdf

Distribution ZIP files

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

– STIX V2.0: http://docs.oasis-open.org/cti/stix/v2.0/cs01/stix-v2.0-cs01.zip

– TAXII V2.0: http://docs.oasis-open.org/cti/taxii/v2.0/cs01/taxii-v2.0-cs01.zip

Members of the CTI 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 Cyber Threat Intelligence (CTI) TC
https://www.oasis-open.org/committees/cti/

[2] Public reviews:
– STIX V2.0:
* 30-day public review, 08 March 2017:
https://lists.oasis-open.org/archives/members/201703/msg00000.html
– Comment resolution log:
http://docs.oasis-open.org/cti/stix/v2.0/csprd01/stix-v2.0-csprd01-comment-resolution-log.xlsx

* 15-day public review, 18 May 2017:
https://lists.oasis-open.org/archives/members/201705/msg00006.html
– Comment resolution log:
http://docs.oasis-open.org/cti/stix/v2.0/csprd02/stix-v2.0-csprd02-comment-resolution-log.xlsx

– TAXII v2.0:
* 30-day public review, 12 May 2017:
https://lists.oasis-open.org/archives/members/201705/msg00003.html
– Comment resolution log:
http://docs.oasis-open.org/cti/taxii/v2.0/csprd01/taxii-v2.0-csprd01-comment-resolution-log.xlsx

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

Members of the OASIS XML Localisation Interchange File Format (XLIFF) TC [1] have recently approved a Special Majority Ballot [2] to advance “XLIFF Version 2.1” as a Candidate OASIS Standard (COS). The COS now enters a 60-day public review period in preparation for a member ballot to consider its approval as an OASIS Standard.

XLIFF Version 2.1
Candidate OASIS Standard 01
12 October 2017

XLIFF is the XML Localization Interchange File Format. It has been designed by a group of multilingual content publishers, software providers, localization service providers, localization tools providers and researchers. It is intended to give any multilingual content owner a single interchange file format that can be understood by any localization provider, using any conformant localization tool.
While the primary focus is on being a lossless interchange format, usage of XLIFF as a processing format is neither encouraged nor discouraged or prohibited.
This specification replaces or supersedes XLIFF Version 2.0, which was submitted to ISO TC 37/SC 5, went through a unanimous DIS ballot and is currently under publication (60.00) as ISO 21720.

The TC received 5 Statements of Use from ENLASO Corporation, Felix Sasaki, Soroush Saadatafar, SDL Trados Studio, and Umbraco [3].

Public Review Period:

The 60-day public review starts 21 October 2017 at 00:00 UTC and ends 19 December 2017 at 23:59 UTC.

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:

HTML (Authoritative):
http://docs.oasis-open.org/xliff/xliff-core/v2.1/cos01/xliff-core-v2.1-cos01.html

PDF:
http://docs.oasis-open.org/xliff/xliff-core/v2.1/cos01/xliff-core-v2.1-cos01.pdf

Editable source:
http://docs.oasis-open.org/xliff/xliff-core/v2.1/cos01/xliff-core-v2.1-cos01.xml

ZIP distribution file (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:

http://docs.oasis-open.org/xliff/xliff-core/v2.1/cos01/xliff-core-v2.1-cos01.zip

Additional information about the specification and the XLIFF TC may be found at the TC’s public home page:

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

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=xliff

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/xliff-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 “XLIFF Version 2.1,” 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 XML Localisation Interchange File Format (XLIFF) TC
https://www.oasis-open.org/committees/xliff/

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

[3] Statements of Use:

ENLASO Corporation: https://lists.oasis-open.org/archives/xliff/201709/msg00006.html

Felix Sasaki, Individual: https://lists.oasis-open.org/archives/xliff/201709/msg00007.html

Soroush Saadatafar, Individual: https://lists.oasis-open.org/archives/xliff-comment/201710/msg00005.html

SDL Trados Studio: https://lists.oasis-open.org/archives/xliff-comment/201710/msg00004.html

Umbraco: https://lists.oasis-open.org/archives/xliff-comment/201710/msg00003.html

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

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

Members of the OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC [1] have recently approved a Special Majority Ballot [2] to advance “TOSCA Simple Profile in YAML Version 1.1” as a Candidate OASIS Standard (COS). The COS now enters a 60-day public review period in preparation for a member ballot to consider its approval as an OASIS Standard.

TOSCA Simple Profile in YAML Version 1.1
Candidate OASIS Standard 01
04 October 2017

YAML is a human friendly data serialization standard with a syntax much easier to read and edit than XML. The TOSCA Simple Profile in YAML specifies a rendering of TOSCA which aims to provide a more accessible syntax as well as a more concise and incremental expressiveness of the TOSCA DSL (Domain Specific Language) in order to minimize the learning curve and speed the adoption of the use of TOSCA to portably describe cloud applications.

The TC received 7 Statements of Use from Ubicity Corp, FastConnect, Vnomic, GigaSpaces, ZTE, University of Pisa, and IBM [3].

Public Review Period:

The 60-day public review starts 19 October 2017 at 00:00 UTC and ends 17 December 2017 at 23:59 UTC.

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:

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

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

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

ZIP distribution file (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:

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

Additional information about the specification and the TOSCA TC may be found at the TC’s public home page:

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

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=tosca

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/tosca-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 “TOSCA Simple Profile in YAML Version 1.1,” 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 Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
http://www.oasis-open.org/committees/tosca/

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

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

[3] Statements of Use:

Ubicity Corp.: https://lists.oasis-open.org/archives/tosca/201708/msg00019.html

FastConnect: https://lists.oasis-open.org/archives/tosca/201708/msg00023.html

Vnomic: https://lists.oasis-open.org/archives/tosca/201708/msg00025.html

GigaSpaces: https://lists.oasis-open.org/archives/tosca/201708/msg00034.html

ZTE: https://lists.oasis-open.org/archives/tosca/201708/msg00061.html

University of Pisa: https://lists.oasis-open.org/archives/tosca/201708/msg00062.html

IBM: https://lists.oasis-open.org/archives/tosca/201708/msg00070.html

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

[5] http://www.oasis-open.org/committees/tosca/ipr.php

https://www.oasis-open.org/policies-guidelines/ipr#RF-on-Limited-Mode
RF on Limited Terms Mode

OASIS is pleased to announce publication of “What’s New in OData Version 4.01,” a Committee Note (CN) from the members of the OASIS Open Data Protocol (OData) TC [1]. The CN describes the changes and their motivation in OData Version 4.01 compared to its predecessor version 4.0.

What’s New in OData Version 4.01
Committee Note 02
28 September 2017

Editable source:
http://docs.oasis-open.org/odata/new-in-odata/v4.01/cn02/new-in-odata-v4.01-cn02.docx

HTML:
http://docs.oasis-open.org/odata/new-in-odata/v4.01/cn02/new-in-odata-v4.01-cn02.html

PDF:
http://docs.oasis-open.org/odata/new-in-odata/v4.01/cn02/new-in-odata-v4.01-cn02.pdf

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/odata/new-in-odata/v4.01/cn02/new-in-odata-v4.01-cn02.zip

Members of the OData TC approved this Committee Note by a Full Majority vote on 28 September 2017 as documented in the TC minutes [2].

Our congratulations to all the members of the TC.

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

[1] OASIS Open Data Protocol (OData) TC
https://www.oasis-open.org/committees/odata/

[2] Approval
https://www.oasis-open.org/committees/download.php/61673/odata-meeting-189_on-20170928-minutes.html

We are pleased to announce that the OASIS Open Data Protocol (OData) TC [1] has released four Committee Specification Drafts (CSDs) for public review and comment. These CSDs have been updated based on feedback from their previous public reviews.

The Open Data Protocol (OData) enables the creation of REST-based
data services, which allow resources, identified using Uniform Resource Locators (URLs) and defined in an Entity Data Model (EDM), to be published and edited by Web clients using simple HTTP messages. The public review drafts released today are:

– OData Version 4.01: This document defines the core semantics and facilities of the protocol.

– OData JSON Format Version 4.01: This document extends the core specification by defining representations for OData requests and responses using a JSON format.

– OData Common Schema Definition Language (CSDL) XML Representation Version 4.01: OData services are described by an Entity Model (EDM). The Common Schema Definition Language (CSDL) defines specific representations of the entity data model exposed by an OData service using, XML, JSON, and other formats. This document specifically defines the XML representation of CSDL.

– OData Common Schema Definition Language (CSDL) JSON Representation Version 4.01: This document specifically defines the JSON representation of CSDL.

The public review drafts and related files are available here:

– OData Version 4.01
Committee Specification Draft 03 / Public Review Draft 03
28 September 2017

* Part 1: Protocol

Editable source (Authoritative):
http://docs.oasis-open.org/odata/odata/v4.01/csprd03/part1-protocol/odata-v4.01-csprd03-part1-protocol.docx

HTML:
http://docs.oasis-open.org/odata/odata/v4.01/csprd03/part1-protocol/odata-v4.01-csprd03-part1-protocol.html

PDF:
http://docs.oasis-open.org/odata/odata/v4.01/csprd03/part1-protocol/odata-v4.01-csprd03-part1-protocol.pdf

Redlined DIFF file:
http://docs.oasis-open.org/odata/odata/v4.01/csprd03/part1-protocol/odata-v4.01-csprd03-part1-protocol-DIFF.pdf

* Part 2: URL Conventions

Editable source (Authoritative):
http://docs.oasis-open.org/odata/odata/v4.01/csprd03/part2-url-conventions/odata-v4.01-csprd03-part2-url-conventions.docx

HTML:
http://docs.oasis-open.org/odata/odata/v4.01/csprd03/part2-url-conventions/odata-v4.01-csprd03-part2-url-conventions.html

PDF:
http://docs.oasis-open.org/odata/odata/v4.01/csprd03/part2-url-conventions/odata-v4.01-csprd03-part2-url-conventions.pdf

Redlined DIFF file:
http://docs.oasis-open.org/odata/odata/v4.01/csprd03/part2-url-conventions/odata-v4.01-csprd03-part2-url-conventions-DIFF.pdf

* ABNF components:
http://docs.oasis-open.org/odata/odata/v4.01/csprd03/abnf/

– OData JSON Format Version 4.01
Committee Specification Draft 03 / Public Review Draft 03
28 September 2017

Editable source (Authoritative):
http://docs.oasis-open.org/odata/odata-json-format/v4.01/csprd03/odata-json-format-v4.01-csprd03.docx

HTML:
http://docs.oasis-open.org/odata/odata-json-format/v4.01/csprd03/odata-json-format-v4.01-csprd03.html

PDF:
http://docs.oasis-open.org/odata/odata-json-format/v4.01/csprd03/odata-json-format-v4.01-csprd03.pdf

Redlined DIFF file:
http://docs.oasis-open.org/odata/odata-json-format/v4.01/csprd03/odata-json-format-v4.01-csprd03-DIFF.pdf

– OData Common Schema Definition Language (CSDL) XML Representation Version 4.01
Committee Specification Draft 03 / Public Review Draft 03
28 September 2017

Editable source (Authoritative):
http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/csprd03/odata-csdl-xml-v4.01-csprd03.docx

HTML:
http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/csprd03/odata-csdl-xml-v4.01-csprd03.html

PDF:
http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/csprd03/odata-csdl-xml-v4.01-csprd03.pdf

Redlined DIFF file:
http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/csprd03/odata-csdl-xml-v4.01-csprd03-DIFF.pdf

XML schemas:
http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/csprd03/schemas/

– OData Common Schema Definition Language (CSDL) JSON Representation Version 4.01
Committee Specification Draft 02 / Public Review Draft 02
28 September 2017

Editable source (Authoritative):
http://docs.oasis-open.org/odata/odata-csdl-json/v4.01/csprd02/odata-csdl-json-v4.01-csprd02.docx

HTML:
http://docs.oasis-open.org/odata/odata-csdl-json/v4.01/csprd02/odata-csdl-json-v4.01-csprd02.html

PDF:
http://docs.oasis-open.org/odata/odata-csdl-json/v4.01/csprd02/odata-csdl-json-v4.01-csprd02.pdf

Redlined DIFF file:
http://docs.oasis-open.org/odata/odata-csdl-json/v4.01/csprd02/odata-csdl-json-v4.01-csprd02-DIFF.pdf

JSON schemas:
http://docs.oasis-open.org/odata/odata-csdl-json/v4.01/csprd02/schemas/

For your convenience, OASIS provides complete packages of the prose specifications and related files in ZIP distribution files. You can download the ZIP files at:

– OData v4.01: http://docs.oasis-open.org/odata/odata/v4.01/csprd03/odata-v4.01-csprd03.zip

– OData JSON Format v4.01: http://docs.oasis-open.org/odata/odata-json-format/v4.01/csprd03/odata-json-format-v4.01-csprd03.zip

– OData Common Schema Definition Language (CSDL) XML Representation v4.01: http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/csprd03/odata-csdl-xml-v4.01-csprd03.zip

– OData Common Schema Definition Language (CSDL) JSON Representation v4.01: http://docs.oasis-open.org/odata/odata-csdl-json/v4.01/csprd02/odata-csdl-json-v4.01-csprd02.zip

How to Provide Feedback

OASIS and the OData TC value your feedback. We solicit 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.

This public review starts 18 October 2017 at 00:00 UTC and ends 01 November 2017 at 11:59 UTC.

These specification drafts were previously submitted for public review [2]. Changes are highlighted in red-lined DIFF files listed above. Comments for these drafts are limited to the changes from the previous public review.

Comments on the work may be submitted to the TC by following the instructions located at:

http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=odata

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

http://lists.oasis-open.org/archives/odata-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with the public review of these works, 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 information about this specification and the OData TC may be found on the TC’s public home page.

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

[1] OASIS Open Data Protocol (OData) TC
http://www.oasis-open.org/committees/odata/

[2] Previous public reviews:

– OData Version 4.01

* 30-day public review, 19 January 2017:
https://lists.oasis-open.org/archives/members/201701/msg00003.html
– Comment resolution log:
http://docs.oasis-open.org/odata/odata/v4.01/csprd01/odata-v4.01-csprd01-comment-resolution-log.txt

* 30-day public review, 03 July 2017:
https://lists.oasis-open.org/archives/members/201707/msg00001.html – Comment resolution log:
http://docs.oasis-open.org/odata/odata/v4.01/csprd02/odata-v4.01-csprd02-comment-resolution-log.xlsx

– OData JSON Format Version 4.01

* 30-day public review, 19 January 2017:
https://lists.oasis-open.org/archives/members/201701/msg00003.html
– Comment resolution log:
http://docs.oasis-open.org/odata/odata-json-format/v4.01/csprd01/odata-json-format-v4.01-csprd01-comment-resolution-log.txt

* 30-day public review, 03 July 2017:
https://lists.oasis-open.org/archives/members/201707/msg00001.html – Comment resolution log:
http://docs.oasis-open.org/odata/odata-json-format/v4.01/csprd02/odata-json-format-v4.01-csprd02-comment-resolution-log.xlsx

– OData Common Schema Definition Language (CSDL) XML Representation Version 4.01

* 30-day public review, 19 January 2017:
https://lists.oasis-open.org/archives/members/201701/msg00003.html
– Comment resolution log:
http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/csprd01/odata-csdl-xml-v4.01-csprd01-comment-resolution-log.txt

* 30-day public review, 03 July 2017:
https://lists.oasis-open.org/archives/members/201707/msg00001.html – Comment resolution log:
http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/csprd02/odata-csdl-xml-v4.01-csprd02-comment-resolution-log.xlsx

– OData Common Schema Definition Language (CSDL) JSON Representation v4.01

* 30-day public review, 03 July 2017:
https://lists.oasis-open.org/archives/members/201707/msg00001.html – Comment resolution log:
http://docs.oasis-open.org/odata/odata-csdl-json/v4.01/csprd01/odata-csdl-json-v4.01-csprd01-comment-resolution-log.xlsx

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

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

We are pleased to announce that Electronic Court Filing Version 5.0 is now available for public review and comment.

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 01 / Public Review Draft 01
15 September 2017

Editable source (Authoritative):
http://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd01/ecf-v5.0-csprd01.docx

HTML:
http://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd01/ecf-v5.0-csprd01.html

PDF:
http://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd01/ecf-v5.0-csprd01.pdf

XML schemas and Genericode code lists:
http://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd01/schema/

XML example messages:
http://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd01/examples/

Model and documentation:
http://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd01/model/

Change Log of ECF Version 4.0 and Version 5.0:
http://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd01/Change-Log.doc

ECF Version 5.0 UML model artifacts:

http://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd01/uml/

ECF Version 5.0 UML model current github repository snapshot:
https://github.com/oasis-tcs/legalxml-courtfiling-5.0-bouml/releases/tag/wd26

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/legalxml-courtfiling/ecf/v5.0/csprd01/ecf-v5.0-csprd01.zip

Public Review Period:

OASIS and the OASIS 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 29 September 2017 at 00:00 UTC and ends 27 November 2017 at 23:59 UTC.

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

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

https://www.oasis-open.org/committees/legalxml-courtfiling/

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

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

[2] http://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

We are pleased to announce that the OASIS LegalRuleML TC members have recently approved a Committee Specification Draft (CSD) and submitted it for a 15-day public review:

LegalRuleML Core Specification Version 1.0
Committee Specification Draft 02 / Public Review Draft 02
17 May 2017

What is LegalRuleML and why is it important?

Legal texts, e.g. legislation, regulations, contracts, and case law, are the source of norms, guidelines, and rules. As text, it is difficult to exchange specific information content contained in the texts between parties, to search for and extract structured the content from the texts, or to automatically process it further. Legislators, legal practitioners, and business managers are, therefore, impeded from comparing, contrasting, integrating, and reusing the contents of the texts, since any such activities are manual. In the current web-enabled context, where innovative eGovernment and eCommerce applications are increasingly deployed, it has become essential to provide machine-readable forms (generally in XML) of the contents of the text.

The objective of the LegalRuleML Core Specification Version 1.0 is to define a standard (expressed with XML-schema and Relax NG and on the basis of Consumer RuleML 1.02) that is able to represent the particularities of the legal normative rules with a rich, articulated, and meaningful mark-up language.

LegalRuleML models:

– defeasibility of rules and defeasible logic;
– deontic operators (e.g., obligations, permissions, prohibitions, rights);
– semantic management of negation;
– temporal management of rules and temporality in rules;
– classification of norms (i.e., constitutive, prescriptive);
– jurisdiction of norms;
– isomorphism between rules and natural language normative provisions;
– identification of parts of the norms (e.g. bearer, conditions);
– authorial tracking of rules.

About the TC:

The OASIS LegalRuleML TC defines a rule interchange language for the legal domain. The work enables modeling and reasoning that allows implementers to structure, evaluate, and compare legal arguments constructed using the rule representation tools provided.

The TC is affiliated with the OASIS LegalXML Member Section. For more information on LegalRuleML, see the TC Charter at https://www.oasis-open.org/committees/legalruleml/charter.php.

Membership in the OASIS LegalRuleML TC is open to all interested persons.

Public Review Period:

The public review starts 15 September 2017 at 00:00 UTC and ends 02 October 2017 at 23:59 UTC.

This release has been updated based on feedback from the first public review [1]. The comments received in that review and their resolution can be found at:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd01/legalruleml-core-spec-v1.0-csprd01-comment-resolution-log.xls
Changes since the first public review are highlighted in:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd02/legalruleml-core-spec-v1.0-csprd02-DIFF.pdf

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.

Note that you must be subscribed to the comment mailing list before sending feedback. Instructions on how to subscribe can be found at https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=legalruleml

HTML (Authoritative):
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd02/legalruleml-core-spec-v1.0-csprd02.html

PDF:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd02/legalruleml-core-spec-v1.0-csprd02.html

Editable source:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd02/legalruleml-core-spec-v1.0-csprd02.docx

Additional artifacts:
XSD schemas: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd02/xsd-schema/
RelaxNG schemas: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd02/relaxng/
XSLT transformations: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd02/xslt/
XSD-conversion drivers: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd02/generation/
RDFS metamodel: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd02/rdfs/
Metamodel diagrams: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd02/diagrams/
Examples: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd02/examples/

ZIP distribution file (complete):
For your convenience, OASIS provides a complete package of the prose document and related files in a ZIP distribution file. You can download the ZIP file here:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd02/legalruleml-core-spec-v1.0-csprd02.zip

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

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, or directly at:
https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=legalruleml

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/legalruleml-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 “LegalRuleML Core Specification Version 1.0”, we call your attention to the OASIS IPR Policy [2] applicable especially [3] to the work of this Technical Committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

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

========== Additional references:
[1] Previous public review:
30-day public review, 10 February 2017
https://lists.oasis-open.org/archives/members/201702/msg00000.html

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

[3] http://www.oasis-open.org/committees/legalruleml/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 SAML V2.0 Protocol Extension for Requesting Attributes per Request Version 1.0 Committee Specification 01 by the members of the OASIS Security Services (SAML) TC:

SAML V2.0 Protocol Extension for Requesting Attributes per Request Version 1.0
Committee Specification 01
23 August 2017

This specification, related to Security Assertion Markup Language (SAML) v2.0, defines an extension to the core protocol that allows Service Providers to specify ad-hoc sets of attributes per request. This brings more flexibility than existing mechanisms, which are based on signaling pre-defined sets of requested attributes.

The OASIS Security Services (SAML) TC is responsible for the standard XML-based framework for creating and exchanging authentication and information. Interoperable exchange of security information between domains, including the ability to federate identities across domains, is crucial to developing solutions for business problems such as performing Web Single Sign-On, utilizing distributed authorization services, and securing e-business transactions.

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

The prose specification and related files are available here:

SAML V2.0 Protocol Extension for Requesting Attributes per Request Version 1.0

Editable source (Authoritative):
http://docs.oasis-open.org/security/saml-protoc-req-attr-req/v1.0/cs01/saml-protoc-req-attr-req-v1.0-cs01.odt

HTML:
http://docs.oasis-open.org/security/saml-protoc-req-attr-req/v1.0/cs01/saml-protoc-req-attr-req-v1.0-cs01.html

PDF:
http://docs.oasis-open.org/security/saml-protoc-req-attr-req/v1.0/cs01/saml-protoc-req-attr-req-v1.0-cs01.pdf

XML schema:
http://docs.oasis-open.org/security/saml-protoc-req-attr-req/v1.0/cs01/schema/sstc-req-attr-ext.xsd

Distribution ZIP file – For your convenience, OASIS provides a complete package of the prose specification and related files in ZIP distribution files. You can download the ZIP file here:
http://docs.oasis-open.org/security/saml-protoc-req-attr-req/v1.0/cs01/saml-protoc-req-attr-req-v1.0-cs01.zip

Members of the SAML 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.

[1] OASIS Security Services (SAML) TC
https://www.oasis-open.org/committees/security/

[2] Previous public review:

30-day public review, 26 May 2017:
https://lists.oasis-open.org/archives/security-services/201705/msg00004.html
– Comment resolution log:
http://docs.oasis-open.org/security/saml-protoc-req-attr-req/v1.0/csprd01/saml-protoc-req-attr-req-v1.0-csprd01-comment-resolution-log.ods

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