The OASIS XML Localisation Interchange File Format (XLIFF) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

XLIFF Version 2.1
Commitee Specification Draft 02 / Public Review Draft 02
07 February 2017

What is XLIFF and why is it useful?

The XML Localisation Interchange File Format (XLIFF) is a specification for the interchange of localizable software and document based objects and related metadata. The purpose of XLIFF’s extensible XML vocabularies is to store localisable data and carry it from one step of the localization process to the other, while allowing interoperability between and among tools.

Public Review Period:

The public review starts 10 February 2017 at 00:00 UTC and ends 24 February 2017 at 11:59 UTC. The 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 the redlined PDF at http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd02/xliff-core-v2.1-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.

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

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

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

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

Schemas:
http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd02/schemas/

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:

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

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

http://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 which can be accessed via the button labeled “Send A Comment” at the top of the TC public home page, or directly at:

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

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/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 [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 XML Localisation Interchange File Format (XLIFF) TC
http://www.oasis-open.org/committees/xliff/

[2] Previous public reviews:

30-day public review, 26 October 2016:
https://lists.oasis-open.org/archives/members/201610/msg00011.html
– Comment resolution log:
http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01-comment-resolution-log.pdf

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

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

OASIS is pleased to announce the publication of its newest OASIS Standard, approved by the members on 18 January 2017:

Business Document Naming and Design Rules Version 1.0
OASIS Standard
18 January 2017

Overview:

This specification prescribes a set of naming and design rules used to create XML document model validation artefacts (W3C Schema XSD files and OASIS Context/value association files) associated with abstract information bundles formally described using the Core Component Technical Specification 2.01 [CCTS].

URIs:

The prose specifications and related files are available here:

Business Document Naming and Design Rules Version 1.0 OASIS Standard

Editable source (Authoritative):
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/os/Business-Document-NDR-v1.0-os.xml

HTML:
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/os/Business-Document-NDR-v1.0-os.html

PDF:
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/os/Business-Document-NDR-v1.0-os.pdf

Distribution ZIP files

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/ubl/Business-Document-NDR/v1.0/os/Business-Document-NDR-v1.0-os.zip

Our congratulations to the members of the UBL on achieving this milestone.

The OASIS Universal Business Language TC [1] members have recently approved two Committee Drafts and submitted them for 60 day public review:

Business Document Naming and Design Rules Version 1.1
Committee Specification Draft 01 / Public Review Draft 01
11 January 2017

and

UBL 2.1 JSON Alternative Representation Version 1.0
Committee Note Draft 01 / Public Review Draft 01
11 January 2017

Overview:

An important and powerful method to design interoperable business documents is to construct logical semantic models using concepts described in the UN/CEFACT Core Components Technical Specification (CCTS) Version 2.01. From these semantic models one can create physical syntax models with which to express the content constraints of actual business documents to be interchanged.

The OASIS Business Document Naming and Design Rules (BDNDR) Version 1.1 Draft Specification prescribes a set of naming and design rules used to create complete CCTS models of interoperable business documents. It also includes the rules needed to create validation artefacts corresponding to them. For XML syntax, the rules govern creating W3C Schema (XSD) and OASIS Context/value Association (CVA) validation artefacts. For JSON syntax, the rules govern creating JSON Schema validation artefacts.

JSON is the JavaScript Object Notation described by ISO/IEC 21778 Information technology — The JSON data interchange format, initially published at https://www.ecma-international.org/publications/standards/Ecma-404.htm as ECMA 404 The JSON data interchange format. JSON Schema is the vocabulary described at http://json-schema.org for annotating and validating JSON documents.

BDNDR Version 1.1 changes no rules for XML syntax from BDNDR Version 1.0 and only adds the new rules prescribed for JSON syntax.

The UBL 2.1 JSON Alternative Representation Version 1.0 Draft Note engages the JSON rules from BDNDR and publishes the CCTS models of UBL 2.1 as json-schema.org validation artefacts. Also included in the package is a transliteration into JSON syntax of each of the UBL 2.1 sample XML instances, all of which validate with the provided JSON schemas.

These two work products are being published simultaneously for reviewers to work with a complete implementation of the proposed new rules for JSON serialization of CCTS document models. The OASIS UBL TC welcomes formal feedback of this new approach to working with JSON syntax. Please use the https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ubl comment list to do so.

Public Review Period:

The public review starts 01 February 2017 at 00:00 UTC and ends 01 April 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:

– Business Document Naming and Design Rules Version 1.1

Editable source (Authoritative):
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/csprd01/Business-Document-NDR-v1.1-csprd01.xml

HTML:
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/csprd01/Business-Document-NDR-v1.1-csprd01.html

PDF:
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/csprd01/Business-Document-NDR-v1.1-csprd01.pdf

– UBL 2.1 JSON Alternative Representation Version 1.0

Editable source (Authoritative):
http://docs.oasis-open.org/ubl/UBL-2.1-JSON/v1.0/cnprd01/UBL-2.1-JSON-v1.0-cnprd01.xml

HTML:
http://docs.oasis-open.org/ubl/UBL-2.1-JSON/v1.0/cnprd01/UBL-2.1-JSON-v1.0-cnprd01.html

PDF:
http://docs.oasis-open.org/ubl/UBL-2.1-JSON/v1.0/cnprd01/UBL-2.1-JSON-v1.0-cnprd01.pdf

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:

– Business Document Naming and Design Rules Version 1.1:
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/csprd01/Business-Document-NDR-v1.1-csprd01.zip

– UBL 2.1 JSON Alternative Representation Version 1.0:
http://docs.oasis-open.org/ubl/UBL-2.1-JSON/v1.0/cnprd01/UBL-2.1-JSON-v1.0-cnprd01.zip

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

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

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

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/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 this public review of “Business Document Naming and Design Rules Version 1.1” and “UBL 2.1 JSON Alternative Representation 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] OASIS Universal Business Language TC
https://www.oasis-open.org/committees/ubl/

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

[3] 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

The OASIS Universal Business Language TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted it for 45-day public review:

Universal Business Language Version 2.2
Committee Specification Draft 01 / Public Review Draft 01
21 December 2016

Overview:

This specification defines the Universal Business Language (UBL) version 2.2, an open library of standard electronic XML business documents for procurement and transportation such as purchase orders, invoices, transport logistics and waybills.

UBL 2.2 is that it is completely backward-compatible with UBL 2.0. UBL 2.2 is technically a minor release however it does add 16 new document types for eTendering, for transportation, and for business directories and agreements. This brings the total number of UBL business documents to 81.

Public Review Period:

The public review starts 01 February 2017 at 00:00 UTC and ends 17 March 2017 at 23:59 UTC.

URIs:

The prose specification document and related files are available here:

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

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

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

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

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

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

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

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

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

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

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/ubl/csprd01-UBL-2.2/UBL-2.2.zip

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

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

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

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/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 this public review of “Universal Business Language Version 2.2”, 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] OASIS Universal Business Language TC
https://www.oasis-open.org/committees/ubl/

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

[3] 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 is pleased to announce the publication of its two newest OASIS Standards, approved by the members on 27 December 2016:

Key Management Interoperability Protocol Specification Version 1.3
OASIS Standard
27 December 2016

and

Key Management Interoperability Protocol Profiles Version 1.3
OASIS Standard
27 December 2016

Overview:

The Key Management Interoperability Protocol (KMIP) is a single, comprehensive protocol for communication between clients that request any of a wide range of encryption keys and servers that store and manage those keys. By replacing redundant, incompatible key management protocols, KMIP provides better data security while at the same time reducing expenditures on multiple products.

KMIP v1.3 enhances the KMIP v1.2 standard by:

– defining new functionality in the protocol to improve interoperability;
– defining additional Test Cases for verifying and validating the new functionality;
– providing additional information in the KMIP Usage Guide to assist in effective implementation of KMIP in key management clients and servers; and
– defining new profiles for establishing KMIP-compliant implementations.

The KMIP Specification describes the protocol used for the communication between clients and servers to perform management operations on objects stored and maintained by a key management system. This includes symmetric and asymmetric cryptographic keys, digital certificates, and templates used to simplify the creation of objects and control their use.

The KMIP Profiles provide a selected set of base level conformance profiles and authentication suites; additional KMIP Profiles define specific sets of KMIP functionality for conformance purposes.

URIs:

The prose specifications and related files are available here:

– Key Management Interoperability Protocol Specification Version 1.3

Editable source (Authoritative):
http://docs.oasis-open.org/kmip/spec/v1.3/os/kmip-spec-v1.3-os.docx

HTML:
http://docs.oasis-open.org/kmip/spec/v1.3/os/kmip-spec-v1.3-os.html

PDF:
http://docs.oasis-open.org/kmip/spec/v1.3/os/kmip-spec-v1.3-os.pdf

– Key Management Interoperability Protocol Profiles Version 1.3

Editable source (Authoritative):
http://docs.oasis-open.org/kmip/profiles/v1.3/os/kmip-profiles-v1.3-os.doc

HTML:
http://docs.oasis-open.org/kmip/profiles/v1.3/os/kmip-profiles-v1.3-os.html

PDF:
http://docs.oasis-open.org/kmip/profiles/v1.3/os/kmip-profiles-v1.3-os.pdf

Test cases:
http://docs.oasis-open.org/kmip/profiles/v1.3/os/test-cases/kmip-v1.3/mandatory/ and http://docs.oasis-open.org/kmip/profiles/v1.3/os/test-cases/kmip-v1.3/optional/

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:

– Key Management Interoperability Protocol Specification Version 1.3:
http://docs.oasis-open.org/kmip/spec/v1.3/os/kmip-spec-v1.3-os.zip

– Key Management Interoperability Protocol Profiles Version 1.3:
http://docs.oasis-open.org/kmip/profiles/v1.3/os/kmip-profiles-v1.3-os.zip

Our congratulations to the members of the KMIP TC on achieving this milestone.

OASIS is pleased to announce that Business Document Naming and Design Rules Version 1.0 from the OASIS Universal Business Language (UBL) TC has been approved by the membership as an OASIS Standard [1].

The call to vote was made on 05 January 2017 [2] and the ballot closed on 18 January 2017. A minimum of 43 affirmative votes was needed in order to win approval. The finally vote tally was 52 with 1 abstention.

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

[2] Call to vote
https://www.oasis-open.org/apps/org/workgroup/voting/email/archives/201701/msg00000.html

[3] URLs to the latest published version:

Business Document Naming and Design Rules Version 1.0
Candidate OASIS Standard 01
06 October 2016

http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/cos01/Business-Document-NDR-v1.0-cos01.xml (Authoritative)
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/cos01/Business-Document-NDR-v1.0-cos01.html
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/cos01/Business-Document-NDR-v1.0-cos01.pdf

The OASIS Open Data Protocol (OData) TC [1] members have recently approved 4 Committee Specification Drafts (CSD) and 1 Committee Note and submitted these for 30-day public review:

OData Version 4.01
Committee Specification Draft 01 / Public Review Draft 01
08 December 2016

OData Vocabularies Version 4.0
Committee Specification Draft 01 / Public Review Draft 01
08 December 2016

OData JSON Format Version 4.01
Committee Specification Draft 01 / Public Review Draft 01
08 December 2016

OData Common Schema Definition Language (CSDL) XML Representation Version 4.01
Committee Specification Draft 01 / Public Review Draft 01
08 December 2016

OData to OpenAPI Mapping Version 1.0
Committee Note Draft 01 / Public Review Draft 01
15 December 2016

What are these new OData documents and why are they useful?

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.

– OData V4.01 is a 3-part specification that defines the core semantics and facilities of the protocol.

– OData Vocabularies V4.0 is a new specification that describes the evolving set of OData vocabularies maintained by the Technical Committee at https://github.com/oasis-tcs/odata-vocabularies.

– OData JSON Format V4.01 extends the core specification by defining representations for OData requests and responses using a JSON format.

– 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. OData Common Schema Definition Language (CSDL) XML Representation V4.01 specifically defines the XML representation of the entity data model.

– The OpenAPI Specification (OAS) is a standard, language-agnostic interface to REST APIs which allows both humans and computers to discover and understand the capabilities of the service. OData to OpenAPI Mapping Version 1.0 describes a possible mapping of OData service descriptions to OAS documents.

Public Review Period:

The public review starts 19 January 2017 at 00:00 UTC and ends 16 February 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:

– OData Version 4.01

— OData Version 4.01. Part 1: Protocol

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

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

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

— OData Version 4.01. Part 2: URL Conventions

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

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

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

— OData Version 4.01. Part 3: Common Schema Definition Language (CSDL)

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

HTML:
http://docs.oasis-open.org/odata/odata/v4.01/csprd01/part3-csdl/odata-v4.01-csprd01-part3-csdl.html

PDF:
http://docs.oasis-open.org/odata/odata/v4.01/csprd01/part3-csdl/odata-v4.01-csprd01-part3-csdl.pdf

— ABNF components:
http://docs.oasis-open.org/odata/odata/v4.01/csprd01/abnf/

– OData Vocabularies Version 4.0

Editable source (Authoritative):
http://docs.oasis-open.org/odata/odata-vocabularies/v4.0/csprd01/odata-vocabularies-v4.0-csprd01.docx

HTML:
http://docs.oasis-open.org/odata/odata-vocabularies/v4.0/csprd01/odata-vocabularies-v4.0-csprd01.html

PDF:
http://docs.oasis-open.org/odata/odata-vocabularies/v4.0/csprd01/odata-vocabularies-v4.0-csprd01.pdf

– OData JSON Format Version 4.01

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

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

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

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

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

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

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

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

– OData to OpenAPI Mapping Version 1.0

Editable source (Authoritative):
http://docs.oasis-open.org/odata/odata-openapi/v1.0/cnprd01/odata-openapi-v1.0-cnprd01.docx

HTML:
http://docs.oasis-open.org/odata/odata-openapi/v1.0/cnprd01/odata-openapi-v1.0-cnprd01.html

PDF:
http://docs.oasis-open.org/odata/odata-openapi/v1.0/cnprd01/odata-openapi-v1.0-cnprd01.pdf

ZIP distribution file (complete):

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

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

– OData Vocabularies Version 4.0: http://docs.oasis-open.org/odata/odata-vocabularies/v4.0/csprd01/odata-vocabularies-v4.0-csprd01.zip

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

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

– OData to OpenAPI Mapping Version 1.0: http://docs.oasis-open.org/odata/odata-openapi/v1.0/cnprd01/odata-openapi-v1.0-cnprd01.zip

Additional information about the specifications and the OData TC can be found at the TC’s public home page:

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

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

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

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

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of these OData specifications, 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] OASIS Open Data Protocol (OData) TC
https://www.oasis-open.org/committees/odata/

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

[3] 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

OASIS is pleased to announce the approval and publication of a new Committee Specification by the members of the OASIS Electronic Identity Credential Trust Elevation Methods (Trust Elevation) TC:

Authentication Step-Up Protocol and Metadata Version 1.0
Committee Specification 01
15 December 2016

What is the Authentication Step-Up Protocol and why is it useful?

Electronic Identity Credential Trust Elevation Methods are used to increase assurance in entity identification using authentication events and related entity information for the purpose of risk mitigation when making access control policy decisions.

The goals of the Authentication Step-Up Protocol are:

· To propose simple Trust Elevation architectural patterns demonstrating the use of Trust Elevation in modern Access Control architectures.

· To describe a common metadata set, mechanisms and protocol elements for Trust Elevation information exchanges.

· To promote the use of Trust Elevation elements to facilitate standardization among the many technologies and approaches currently in use for credential & authentication risk mitigation.

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

About the TC:

The OASIS Trust Elevation TC works to define a set of standardized protocols that service providers may use to elevate the trust in an electronic identity credential presented to them for authentication. The Trust Elevation TC is intended to respond to suggestions from the public sector, including the U.S. National Strategy for Trusted Identities in Cyberspace (NSTIC). The Trust Elevation TC promotes interoperability among multiple identity providers–and among multiple identity federations and frameworks–by facilitating clear communication about common and comparable operations to present, evaluate and apply identity [data/assertions] to sets of declared authorization levels.

URIs:
The prose specifications and related files are available here:

Editable source (Authoritative):
http://docs.oasis-open.org/trust-el/trust-el-protocol/v1.0/cs01/trust-el-protocol-v1.0-cs01.docx

HTML:
http://docs.oasis-open.org/trust-el/trust-el-protocol/v1.0/cs01/trust-el-protocol-v1.0-cs01.html

PDF:
http://docs.oasis-open.org/trust-el/trust-el-protocol/v1.0/cs01/trust-el-protocol-v1.0-cs01.pdf

Distribution ZIP file

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

http://docs.oasis-open.org/trust-el/trust-el-protocol/v1.0/cs01/trust-el-protocol-v1.0-cs01.zip

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

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

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

[1] OASIS Electronic Identity Credential Trust Elevation Methods (Trust Elevation) TC
https://www.oasis-open.org/committees/trust-el/

[2] Public reviews:
– 15-day public review, 17 November 2016:
https://lists.oasis-open.org/archives/members/201611/msg00005.html
– Comment resolution log:
http://docs.oasis-open.org/trust-el/trust-el-protocol/v1.0/csprd02/trust-el-protocol-v1.0-csprd02-comment-resolution-log.txt

– 30-day public review, 22 December 2015:
https://lists.oasis-open.org/archives/members/201512/msg00008.html
– Comment resolution log:
http://docs.oasis-open.org/trust-el/trust-el-protocol/v1.0/csprd01/trust-el-protocol-v1.0-csprd01-comment-resolution-log.xlsx

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

OASIS is pleased to announce the publication of its newest OASIS Standard, approved by the members on 21 December 2016:

TOSCA Simple Profile in YAML Version 1.0
OASIS Standard
21 December 2016

What is the TOSCA Simple Profile in YAML and why is it useful?

The TOSCA TC works to enhance the portability and operational management of cloud applications and services across their entire lifecycle.

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.

URIs:

The prose specifications and related files are available here:

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

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

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

Distribution ZIP files

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.0/os/TOSCA-Simple-Profile-YAML-v1.0-os.zip

Our congratulations to the members of the TOSCA TC on achieving this milestone.

The OASIS Universal Business Language (UBL) TC members [1] have approved submitting the following Candidate OASIS Standard to the membership for a vote for OASIS Standard:

Business Document Naming and Design Rules Version 1.0
Candidate OASIS Standard 01
06 October 2016

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

— Voting Details —

The ballot opens 05 January 2017 at 00:00 UTC and closes 18 January 2017 at 23:59 UTC. You can access the ballot to cast your vote at:

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

The minimum number of affirmative votes required to approve this ballot is 43 (15% of 283 organizational members).

Each OASIS organizational member has one vote. OASIS members should ensure that their organization’s voting representative votes 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”.

— What is the Business Document Naming and Design Rules and how is it useful? —

The OASIS Universal Business Language (UBL) TC works to provide a royalty-free library of standard XML business documents that allow disparate business applications and trading communities to exchange information along their supply chains.

A powerful method to design interoperable business documents is to construct logical semantic models using concepts described in the UN/CEFACT Core Components Technical Specification (CCTS) Version 2.01 and then, from these, create physical syntax models.

The Business Document Naming and Design Rules Version 1.0 (BDNDR) specification prescribes a set of rules used to create complete CCTS models of interoperable business documents. The OASIS Universal Business Language (UBL) Version 2.1 (also published as ISO/IEC 19845:2015), and the OASIS Business Document Envelope (BDE) Version 1.0 are two examples of business document vocabularies developed in conformance to OASIS BDNDR.

3 Statements of Use were received from the Business Document Exchange TC, Document Engineering Services, and the Universal Business Language TC [4].

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

Editable Source (Authoritative):
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/cos01/Business-Document-NDR-v1.0-cos01.xml

HTML:
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/cos01/Business-Document-NDR-v1.0-cos01.html

PDF:
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/cos01/Business-Document-NDR-v1.0-cos01.pdf

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/ubl/Business-Document-NDR/v1.0/cos01/Business-Document-NDR-v1.0-cos01.zip

— Additional information —

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

TC Charter
https://www.oasis-open.org/committees/ubl/charter.php

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

[3] Public reviews:

– 60 day public review, 20 October 2016:
https://lists.oasis-open.org/archives/ubl-comment/201610/msg00000.html
Comment resolution log:
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/cos01/Business-Document-NDR-v1.0-cos01-comment-resolution-log.txt

– 15-day public review, 17 June 2016:
https://lists.oasis-open.org/archives/ubl-comment/201606/msg00002.html
Comment resolution log:
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/csprd02/Business-Document-NDR-v1.0-csprd02-comment-resolution-log..txt

– 30-day public review, 05 April 2016:
https://lists.oasis-open.org/archives/ubl-comment/201604/msg00000.html
Commment resolution log:
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/csprd01/Business-Document-NDR-v1.0-csprd01-comment-resolution-log-revised.ods

[4] Statements of Use:

– UBL TC: https://lists.oasis-open.org/archives/ubl/201609/msg00053.html

– BDXR TC: https://lists.oasis-open.org/archives/ubl/201609/msg00052.html

– Document Engineering Services: https://lists.oasis-open.org/archives/ubl/201609/msg00054.html

OASIS is pleased to announce that “Key Management Interoperability Protocol Specification Version 1.3” from the OASIS Key Management Interoperability Protocol (KMIP) TC has been approved by the membership as an OASIS Standard [1].

The call to vote was made on 14 December 2016 [2] and the ballot closed on 27 December 2016. A minimum of 43 affirmative votes was needed in order to win approval. The specification received 63 affirmative votes and 2 abstentions. The ballot has thus passed and becomes an OASIS Standard.

Note that “Key Management Interoperability Protocol Profiles Version 1.3” Candidate OASIS Standard 01 was also up for voting on this ballot. The specification received 62 affirmative votes, 2 negative votes, and 1 abstention. Per section 3.4.3 (Initial Balloting for OASIS Standard approval) of the OASIS TC Process (https://www.oasis-open.org/policies-guidelines/tc-process#OASISstandard), because negative votes were received amounting to less than 25% of the votes case, the TC will need to take additional actions.

TC Administration will now prepare and publish the final “Key Management Interoperability Protocol Specification Version 1.3” OASIS Standard and notify members when it is available. We will also work with the TC on the next steps for “Key Management Interoperability Protocol Profiles Version 1.3.”

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

[2] Call to vote

https://lists.oasis-open.org/archives/voting/201612/msg00001.html

[3] URLs to the latest published version:

– Key Management Interoperability Protocol Specification Version 1.3

Editable source (Authoritative):
http://docs.oasis-open.org/kmip/spec/v1.3/cos01/kmip-spec-v1.3-cos01.docx

HTML:
http://docs.oasis-open.org/kmip/spec/v1.3/cos01/kmip-spec-v1.3-cos01.html

PDF:
http://docs.oasis-open.org/kmip/spec/v1.3/cos01/kmip-spec-v1.3-cos01.pdf

– Key Management Interoperability Protocol Profiles Version 1.3

Editable source (Authoritative):
http://docs.oasis-open.org/kmip/profiles/v1.3/cos01/kmip-profiles-v1.3-cos01.doc

HTML:
http://docs.oasis-open.org/kmip/profiles/v1.3/cos01/kmip-profiles-v1.3-cos01.html

PDF:
http://docs.oasis-open.org/kmip/profiles/v1.3/cos01/kmip-profiles-v1.3-cos01.pdf

Test cases:
http://docs.oasis-open.org/kmip/profiles/v1.3/cos01/test-cases/kmip-v1.3/mandatory/

http://docs.oasis-open.org/kmip/profiles/v1.3/cos01/test-cases/kmip-v1.3/optional/