We are pleased to announce that from the OASIS DocBook TC [1] is now available for public review and comment. This document lists errata for the OASIS Standard The DocBook Schema Version 5.0.

The documents and related files are available here:

Editable source (Authoritative):
http://docs.oasis-open.org/docbook/specs/docbook-5.0-spec-errata01-csprd01.docx

HTML:
http://docs.oasis-open.org/docbook/specs/docbook-5.0-spec-errata01-csprd01.html

PDF:
http://docs.oasis-open.org/docbook/specs/docbook-5.0-spec-errata01-csprd01.pdf

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:

http://docs.oasis-open.org/docbook/specs/docbook-5.0-spec-errata01-csprd01.zip

How to Provide Feedback

OASIS and the DocBook 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 21 February 2018 at 00:00 UTC and ends 07 March 2018 at 11:59 UTC.

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

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/docbook-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 [2] applicable especially [3] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

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

Additional information about this specification and the DocBook TC may be found on the TC’s public home page.

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

[1] OASIS DocBook TC
http://www.oasis-open.org/committees/docbook/

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

[3] http://www.oasis-open.org/committees/docbook/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 newest OASIS Standard, approved by the members on 13 February 2018:

XLIFF Version 2.1
OASIS Standard
13 February 2018

Overview:

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.

The prose specifications and related files are available here:

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

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

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

Declarative validation artifacts:
http://docs.oasis-open.org/xliff/xliff-core/v2.1/os/schemas

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/xliff/xliff-core/v2.1/os/xliff-core-v2.1-os.zip

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

OASIS is pleased to announce that OData Version 4.01, OData Common Schema Definition Language (CSDL) XML Representation Version 4.01, OData Common Schema Definition Language (CSDL) JSON Representation Version 4.01, and OData JSON Format Version 4.01 from the OASIS Open Data Protocol (OData) TC [1] have been approved as OASIS Committee Specifications.

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 Committee Specifications announced today are:

– OData Version 4.01

This document defines the core semantics and
facilities of the protocol.

– 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.

– OData JSON Format Version 4.01

This document extends the core specification by defining representations for OData requests and responses using a JSON format.

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

The prose specifications and related files are available here:

– OData Version 4.01
Committee Specification 01
30 January 2018

OData Version 4.01. Part 1: Protocol

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

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

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

OData Version 4.01. Part 2: URL Conventions

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

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

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

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

—

OData Common Schema Definition Language (CSDL) XML Representation Version 4.01
Committee Specification 01
30 January 2018

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

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

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

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

—

OData Common Schema Definition Language (CSDL) JSON Representation Version 4.01
Committee Specification 01
30 January 2018

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

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

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

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

—

OData JSON Format Version 4.01
Committee Specification 01
30 January 2018

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

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

PDF:
http://docs.oasis-open.org/odata/odata-json-format/v4.01/cs01/odata-json-format-v4.01-cs01.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 files here:

– OData Version 4.01:
http://docs.oasis-open.org/odata/odata/v4.01/cs01/odata-v4.01-cs01.zip

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

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

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

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

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

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

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

[2] Public reviews:

– 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

* 15-day public review, 18 October, 2017:
https://lists.oasis-open.org/archives/members/201710/msg00000.html
– Comment resolution log:
http://docs.oasis-open.org/odata/odata/v4.01/csprd03/odata-v4.01-csprd03-comment-resolution-log.xlsx

* 15-day public review, 04 December 2017:
https://lists.oasis-open.org/archives/members/201712/msg00000.html
– Comment resolution log:
http://docs.oasis-open.org/odata/odata/v4.01/csprd04/odata-v4.01-csprd04-comment-resolution-log.txt

– 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

* 15-day public review, 18 October, 2017:
https://lists.oasis-open.org/archives/members/201710/msg00000.html
– Comment resolution log:
http://docs.oasis-open.org/odata/odata-json-format/v4.01/csprd03/odata-json-format-v4.01-csprd03-comment-resolution-log.xlsx

* 15-day public review, 04 December 2017:
https://lists.oasis-open.org/archives/members/201712/msg00000.html
– Comment resolution log:
http://docs.oasis-open.org/odata/odata-json-format/v4.01/csprd04/odata-json-format-v4.01-csprd04-comment-resolution-log.txt

– 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

* 15-day public review, 18 October, 2017:
https://lists.oasis-open.org/archives/members/201710/msg00000.html
– Comment resolution log:
http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/csprd03/odata-csdl-xml-v4.01-csprd03-comment-resolution-log.xlsx

* 15-day public review, 04 December 2017:
https://lists.oasis-open.org/archives/members/201712/msg00000.html
– Comment resolution log:
http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/csprd04/odata-csdl-xml-v4.01-csprd04-comment-resolution-log.txt

– 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

* 15-day public review, 18 October, 2017:
https://lists.oasis-open.org/archives/members/201710/msg00000.html
– Comment resolution log:
http://docs.oasis-open.org/odata/odata-csdl-json/v4.01/csprd02/odata-csdl-json-v4.01-csprd02-comment-resolution-log.xlsx

* 15-day public review, 04 December 2017:
https://lists.oasis-open.org/archives/members/201712/msg00000.html
– Comment resolution log:
http://docs.oasis-open.org/odata/odata-csdl-json/v4.01/csprd03/odata-csdl-json-v4.01-csprd03-comment-resolution-log.txt

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

OASIS is pleased to announce that XLIFF Version 2.1 has been approved by the membership as an OASIS Standard [1].

The ballot was held under the OASIS call for consent procedure [2]. Under this procedure, consent is assumed unless eligible voters register valid objections. On the ballot, XLIFF Version 2.1 received 19 affirmative consents and no objections. Therefore the standard is approved.

To find out more about what XLIFF and the OASIS XML Localisation Interchange File Format (XLIFF) TC, see the TC home page at https://www.oasis-open.org/committees/xliff/.

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

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

[3] Call for consent

https://lists.oasis-open.org/archives/members/201801/msg00010.html

[4] URLs to the latest published version:

XLIFF Version 2.1
Candidate OASIS Standard 02
24 January 2018

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

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

Editable source (XML):
http://docs.oasis-open.org/xliff/xliff-core/v2.1/cos02/xliff-core-v2.1-cos02.xml

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

These ballots were held under the OASIS call for consent procedure [2]. Under this procedure, consent is assumed unless eligible voters register valid objections. On the ballot, TOSCA Simple Profile in YAML Version 1.1 received 30 affirmative consents and no objections. Therefore the approval is passed.

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.

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

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

[3] Call for consent

https://lists.oasis-open.org/archives/members/201801/msg00004.html

[4] URLs to the latest published version:

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

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

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

We are pleased to announce that the OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC members have recently approved a Committee Specification Draft (CSD) and submitted it for a 30-day public review:

TOSCA Simple Profile in YAML Version 1.2
Committee Specification Draft 02 / Public Review Draft 01
07 December 2017

This is the first public review for Version 1.2. TOSCA Simple Profile in YAML Version 1.1 is currently a Candidate OASIS Standard.

Overview:

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 TOSCA TC approved this draft on 07 December 2017.

Public Review Period:

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

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

URIs:

The prose specification document and related files are available here:

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

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

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

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/tosca/TOSCA-Simple-Profile-YAML/v1.2/csprd01/TOSCA-Simple-Profile-YAML-v1.2-csprd01.zip

Additional information about the specification and the TOSCA TC can 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 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=tosca

Public Review Period:

OASIS and the TOSCA 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 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.
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/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.2”, 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 references:

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

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

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

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

This Call for Consent is taking place under the revised TC Process rules effective 01 July 2017 [2]. This is a call to the primary or alternate representatives of OASIS Organizational Members to consent or object to this approval. You are welcome to register your consent explicitly on the ballot; however, your consent is assumed unless you register an objection [3]. To register an objection, you must:

1. Indicate your objection on this ballot, and

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

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

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

— Details —

The Call for Consent opens at 17 January 2018 00:00 UTC and closes on 30 January 2018 23:59 pm timezone. You can access the ballot at:

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

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

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

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

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

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

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.

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

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

Distribution ZIP files:

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

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

— Additional information —

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

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

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

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

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

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

[5] Public reviews:

60-day public review, 19 October 2017:
https://lists.oasis-open.org/archives/members/201710/msg00003.html
– Comment resolution log:
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/cos01/TOSCA-Simple-Profile-YAML-v1.1-cos01-comment-resolution-log.txt

15-day public review, 16 February 2017:
https://lists.oasis-open.org/archives/members/201702/msg00002.html
– Comment resolution log:
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/csprd02/TOSCA-Simple-Profile-YAML-v1.1-csprd02-comment-resolution-log.xlsx

30-day public review, 18 October 2016:
https://lists.oasis-open.org/archives/members/201610/msg00005.html
– Comment resolution log:
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/csprd01/TOSCA-Simple-Profile-YAML-v1.1-csprd01-comment-resolution-log.txt

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

OASIS members and other interested parties,

We are pleased to announce that Cloud Application Management for Platforms Version 1.2 from the OASIS Cloud Application Management for Platforms (CAMP) TC [1] is now available for public review and comment. This is the second public review for Version 1.2. CAMP Version 1.1 is an OASIS Committee Specification.

Cloud Application Management for Platforms Version 1.2 defines the artifacts and APIs that need to be offered by a Platform as a Service (PaaS) cloud to manage the building, running, administration, monitoring and patching of applications in the cloud. Its purpose is to enable interoperability among self-service interfaces to PaaS clouds by defining artifacts and formats that can be used with any conforming cloud and enable independent vendors to create tools and services that interact with any conforming cloud using the defined interfaces. Cloud vendors can use these interfaces to develop new PaaS offerings that will interact with independently developed tools and components.

The documents and related files are available here:

Cloud Application Management for Platforms Version 1.2
Committee Specification Draft 02 / Public Review Draft 02
25 October 2017

PDF:
http://docs.oasis-open.org/camp/camp-spec/v1.2/csprd02/camp-spec-v1.2-csprd02.pdf (Authoritative)

HTML:
http://docs.oasis-open.org/camp/camp-spec/v1.2/csprd02/camp-spec-v1.2-csprd02.html

Editable source:
http://docs.oasis-open.org/camp/camp-spec/v1.2/csprd02/camp-spec-v1.2-csprd02.doc

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/camp/camp-spec/v1.2/csprd02/camp-spec-v1.2-csprd02.zip

Public Review Period:

OASIS and the CAMP 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.

The public review starts 11 January 2018 at 00:00 UTC and ends 25 January 2018 at 23: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 diff-marked PDF file [3].

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.

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 [1], or directly at:

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

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/camp-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 Cloud Application Management for Platforms Version 1.2, 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 CAMP TC may be found on the TC’s public home page located at:

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

========== Additional references:
[1] OASIS Cloud Application Management for Platforms (CAMP) TC
https://www.oasis-open.org/committees/camp/
[2] Previous public review:
30-day public review: https://lists.oasis-open.org/archives/camp/201705/msg00011.html
[3] diff-marked PDF: http://docs.oasis-open.org/camp/camp-spec/v1.2/csprd02/camp-spec-v1.2-csprd02-DIFF.pdf
[4] http://www.oasis-open.org/who/intellectualproperty.php
[5] http://www.oasis-open.org/committees/camp/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode
Non-Assertion Mode