#XACML v3.0 Related and Nested Entities Profile Version 1.0 Committee Specification 01 is published

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

XACML v3.0 Related and Nested Entities Profile Version 1.0
Committee Specification 01
25 October 2015

Overview:

It is not unusual for access control policy to be dependent on attributes that are not naturally properties of the access subject or resource, but rather are properties of entities that are related to the access subject or resource. This profile defines the means to reference such attributes from within XACML policies for processing by a policy decision point.

Description of the TC:

The XACML Technical Committee defines a core XML schema for representing authorization and entitlement policies.

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

Editable source (Authoritative):
http://docs.oasis-open.org/xacml/xacml-3.0-related-entities/v1.0/cs01/xacml-3.0-related-entities-v1.0-cs01.doc

HTML:
http://docs.oasis-open.org/xacml/xacml-3.0-related-entities/v1.0/cs01/xacml-3.0-related-entities-v1.0-cs01.html

PDF:
http://docs.oasis-open.org/xacml/xacml-3.0-related-entities/v1.0/cs01/xacml-3.0-related-entities-v1.0-cs01.pdf

XML schemas:
http://docs.oasis-open.org/xacml/xacml-3.0-related-entities/v1.0/cs01/schemas/

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/xacml/xacml-3.0-related-entities/v1.0/cs01/xacml-3.0-related-entities-v1.0-cs01.zip

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

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

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

[1] eXtensible Access Control Markup Language (XACML) TC
https://www.oasis-open.org/committees/xacml/

[2] Public reviews:
– 30-day public review, 24 August 2015: https://lists.oasis-open.org/archives/members/201508/msg00011.html
– Comment resolution log: http://docs.oasis-open.org/xacml/xacml-3.0-related-entities/v1.0/csprd01/xacml-3.0-related-entities-v1.0-csprd01-comment-resolution-log.txt

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

Public Review for ebCore Agreement Update Specification V1.0 – ends December 9th

The OASIS ebXML Core (ebCore) TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted it for 30-day public review:

ebCore Agreement Update Specification Version 1.0
Committee Specification Draft 01 / Public Review Draft 01
20 October 2015

Overview:

The ebCore Agreement Update specification defines message exchanges and an XML schema to support the exchange of messaging service communication agreement update requests and the associated responses to such requests. The main initial application of the specification is the exchange of X.509 certificates for certificate rollover, but the schema offers extensibility for other types of updates.

The specification is based on the concept of messaging service communication agreements and the creation of new agreements as independently identified updated copies of existing agreements. The specification supports ebMS2, ebMS3 and AS4 but can also be used with other protocols that have a concept of communication agreement.

The specification is independent of storage or interchange formats for configuration information.

Public Review Period:

The public review starts 10 November 2015 at 00:00 UTC and ends 09 December 2015 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.

Reviewers may provide comments directly from the comment-tag version of document. The file

http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/csprd01/ebcore-au-v1.0-csprd01-COMMENT-TAGS.html

contains the HTML version of the draft with a “[comment?]” link next to each section heading. Clicking on this link will launch your email application and begin a message to ebcore-comment@lists.oasis-open.org with the specific section number and title in the subject line. Simply enter your comment and click send.

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=ebcore.

URIs:

The prose specification document and related files are available here:

Editable source (Authoritative):
http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/csprd01/ebcore-au-v1.0-csprd01.odt

HTML:
http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/csprd01/ebcore-au-v1.0-csprd01.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/csprd01/ebcore-au-v1.0-csprd01-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/csprd01/ebcore-au-v1.0-csprd01.pdf

XML schemas:
http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/csprd01/schema/ebcore-au-v1.0.xsd

Schema data dictionary:
http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/csprd01/documentation/index.html

XML document samples: http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/csprd01/samples/

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/ebcore/ebcore-au/v1.0/csprd01/ebcore-au-v1.0-csprd01.zip

Additional information about the specification and the OASIS ebXML Core (ebCore) TC can be found at the TC’s public home page:

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

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

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/ebcore-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 “ebCore Agreement Update 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] OASIS ebXML Core (ebCore) TC
https://www.oasis-open.org/committees/ebcore/

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

[3] http://www.oasis-open.org/committees/ebcore/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#s10.2.3
RF on Limited Terms Mode

Call for Participation: XLIFF Object Model and Other Serializations (XLIFF OMOS) TC

A new OASIS technical committee is being formed. The XLIFF Object Model and Other Serializations (XLIFF OMOS) Technical Committee (TC) has been proposed by the members of OASIS listed in the charter below. The TC name, statement of purpose, scope, list of deliverables, audience, IPR mode and language specified in this proposal will constitute the TC’s official charter. Submissions of technology for consideration by the TC, and the beginning of technical discussions, may occur no sooner than the TC’s first meeting.

The eligibility requirements for becoming a participant in the TC at the first meeting are:

(a) you must be an employee or designee of an OASIS member organization or an individual member of OASIS, and

(b) you must join the Technical Committee, which members may do by using the Roster “join group: link on the TC’s web page at [a].

To be considered a voting member at the first meeting:

(a) you must join the Technical Committee at least 7 days prior to the first meeting (on or before 01 December 2015); and

(b) you must attend the first meeting of the TC, at the time and date fixed below (08 December 2015).

Participants also may join the TC at a later time. OASIS and the TC welcomes all interested parties.

Non-OASIS members who wish to participate may contact us about joining OASIS [b]. In addition, the public may access the information resources maintained for each TC: a mail list archive, document repository and public comments facility, which will be linked from the TC’s public home page at [c].

Please feel free to forward this announcement to any other appropriate lists. OASIS is an open standards organization; we encourage your participation.

———-

[a] https://www.oasis-open.org/apps/org/workgroup/xliff-omos/

[b] See http://www.oasis-open.org/join/

[c] http://www.oasis-open.org/committees/xliff-omos/

———-

CALL FOR PARTICIPATION

OASIS XLIFF Object Model and Other Serializations (XLIFF OMOS) Technical Committee Charter

The charter for this TC is as follows.

Section 1: TC Charter

(1)(a) TC Name

XLIFF Object Model and Other Serializations (XLIFF OMOS) Technical Committee

(1)(b) Statement of Purpose

This committee’s high level purpose is to further advance standards based payload and metadata interoperability in the Globalization, Internationalization, Localization and Translation (GILT) industries. This TC will be describing and defining standard serialization independent interchange objects based predominantly on state of the art and legacy XML standards that have been successfully used in the GILT industries ever since inception of XML. Defining specific serializations, transaction models, standard interfaces and web services based on the defined objects and object models is also in scope as far as it facilitates the high level purpose set out here.

(1)(c) Scope

The following items belong to the Scope of Work and are expected to be refined as the TC gains additional insights into evolving GILT industry use cases. Members will gather insights and requirements from consultations with the wider community of industry stakeholders, annual Symposia, questionnaires, etc. and use these insights to produce concrete technical deliverables.

In particular, in case that XLIFF TC identifies the need for a major new version of the XLIFF standard and starts moving away from the XLIFF 2 family of standards, this TC will work in concert with those developments and develop a serialization independent Object Model for the major new version, non-XML serializations etc. exactly as it now works on these items for the XLIFF 2 family of standards, TMX etc.

i) Define and maintain a serialization independent Object Model for the XLIFF 2 family of standards that is being developed by the OASIS XLIFF TC.

ii) Define and maintain non-XML serializations of the said XLIFF Object Model, prominently a JSON serialization, but also any other serializations that could not be developed by the XLIFF TC for scope restriction reasons, as industry needs arise.

iii) Define specific standard Application Interfaces (API) and abstract service architectures for various XLIFF serializations and other related standards (such as TMX, TBX, ITS, SRX etc.) and their various serializations used in concert for GILT payload and metadata interchange.

iv) Host and maintain TMX 1.4b (1.4.2), develop and maintain any successor versions of the TMX standard including its serialization independent Object Model and various serializations as the need arises.

v) Define and describe lossless or nearly lossless mappings between XLIFF and related GILT standards, define those mappings in an abstract way and for specific serializations as the need arises.

vi) Define and describe informative best practices and abstract services architecture recommendations with regards to usage of the XLIFF 2 family of standards and related standards including but not limited to current and successor versions of TMX, TBX, SRX, ITS and other related standards used for data and metadata interchange in the GILT industries.

(1)(d) Deliverables

The following are high priority technical deliverables that should be developed and published in the OASIS standards track within 24 months from TC initiation:

i) Serialization independent Object Model for the XLIFF 2 family of standards

ii) JSON serialization of XLIFF 2.1

Work on the following may start during the work on the above high priority deliverables or later on given the general sense of urgency for those within the GILT industries

iii) Republishing of TMX 1.4b (1.4.2) under OASIS IPR

iv) Major new version of TMX, compatible with XLIFF 2 family of standards

(1)(e) IPR Mode

Non-Assertion

(1)(f) Audience

The expected audience for the work of the XLIFF OMOS TC includes but is not limited to:

– Multilingual content and software architects and strategists, multilingual content publishers

– GILT services architects and developers

– Content owners and managers that seek to publish their content in multiple localized versions

– Software providers for internationalization, localization, and translation tools and processes, including language technology components

– Technical communicators employing localization tools and processes for multilingual publishing of their content

– Localization service providers who need to interact seamlessly with localizable and localized content of their customers

(1)(g) Language

English (US spelling)

Section 2: Additional Information

(2)(a) Identification of Similar Work

This TC is intended as the sister committee to OASIS XLIFF TC. The Scope of Work of this TC is designed so that it complements the Scope of Work of the XLIFF TC that could not work on this TCs work items because of legacy scope restrictions. Strong and close liaison will be maintained with XLIFF TC, membership is expected to overlap to large extent.

Other related standards, standards bodies and groups are currently the following:

W3C ITS 2.0 and the W3C ITS Interest Group

ULI TC at Unicode Consortium, their contributions to CLDR (for instance natural languages segmentation behavior), hosting and maintenance work on SRX, word counting and match similarity related standards and best practices

ISO TC 37 TBX and LTAC work on TBX

This TC is also ready to receive Localization related work items from ETSI on behalf of the disbanded ETSI ISG LIS, as long as those fall under XLIFF OMOS Scope of Work and were not transferred to other more closely related standardization body or group

Other standardization work items at other groups may arise that are relevant for this TCs.

This TC will also strive to work in concert with other OASIS committees, prominently CMIS, UBL, DITA, DocBook, and ARIP.

(2)(b) First TC Meeting

08 December 2015 at 4pm GMT(Western European Time). The meeting will be sponsored by Trinity College Dublin (ADAPT).

(2)(c) Ongoing Meeting Schedule

The ongoing meetings will be held on 2nd and 4th Tuesdays each month, at 4pm GMT (Western European time with or w/o DST depending on the season). The meetings will be initially sponsored by Trinity College Dublin (ADAPT). TC members can agree to skip a regular Tuesday meeting from time to time if quorum will not likely be achieved due to holiday seasons, or a majority of voters otherwise unavailable.

(2)(d) TC Proposers

David Filip, filipd@tcd.ie, Trinity College Dublin (ADAPT)

Dave Lewis, dave.lewis@cs.tcd.ie, Trinity College Dublin (ADAPT)

Yves Savourel, ysavourel@enlaso.com, Individual

Patrik Mazanek, pmazanek@sdl.com, SDL

Lucian Podereu, lpodereu@sdl.com, SDL

Bryan Schnabel, bryan.s.schnabel@tektronix.com, Individual

Felix Sasaki, felix@sasakiatcf.com, Individual

Lucia Morado, lucia.morado@unige.ch, Individual

Loic Dufresne de Virel, loic.dufresne.de.virel@intel.com, Intel Corporation

(2)(e) Primary Representatives’ Support

I, David Lewis, dave.lewis@cs.tcd.ie, as OASIS primary representative for Trinity College Dublin (ADAPT), confirm our support for this proposed Charter and endorse our participants listed above as named co-proposers and convener.

I, Nuno Linhares, nlinhares@sdl.com, as OASIS primary representative for SDL, confirm our support for this proposed Charter and endorse our participants listed above as named co-proposers.

I, Katalin Bartfai-Walcott, katalin.kb.walcott@intel.com, as OASIS primary representative for Intel Corporation, confirm our support for this proposed Charter and endorse our participants listed above as named co-proposers.

(2)(f) TC Convener

David Filip, filipd@tcd.ie, Trinity College Dublin (ADAPT)

(2)(g) OASIS Member Section

Decision to be deferred.

(2)(h) Anticipated Contributions

TMX 1.4.2 (1.4b) from ETSI
http://www.etsi.org/deliver/etsi_gs/lis/001_099/002/01.04.02_60/gs_lis002v010402p.pdf

(2)(i) FAQ Document

Q1 [IPR Mode]: “Why did you choose the Non-Assertion mode?”
A1 [IPR Mode] “Under the Non-Assertion mode, all parties agree not to seek to enforce any patent or other intellectual property rights they may have in case usage of those is essential to implement the standards produced by that committee. This precludes the need for licensing terms altogether and makes it easier for open-source developers in particular to participate. The majority of new OASIS Technical Committees choose to work under the Non-Assertion mode.”

Q2 [Join OASIS] “How do I get involved in XLIFF OMOS TC?”
A2 [Join OASIS] “All interested parties are welcome to participate in the XLIFF OMOS TC as long as they are or are willing to become OASIS members; contact join@oasis-open.org for details.”

(2)(j) Work Product Titles and Acronyms

TBD

Borderless Cyber News

Stay current on cyber security standards

Content Management Interoperability Services (#CMIS) Version 1.1 Errata 01 published

OASIS is pleased to announce the approval and publication of a new Committee Specification by the members of the OASIS Content Management Interoperability Services (CMIS) TC:

Content Management Interoperability Services (CMIS) Version 1.1 Errata 01
OASIS Approved Errata 01
19 September 2015

Content Management Interoperability Services (CMIS) Version 1.1 Plus Errata 01
OASIS Standard Incorporating Approved Errata 01
19 September 2015

Overview:

This document lists errata for the OASIS Standard Content Management Interoperability Services (CMIS) Version 1.1. A version of the CMIS OASIS Standard with the errata applied is also published.

Description of the TC:

The CMIS TC develops interoperable interfaces for content management repositories/systems, and conducts interoperability testing among TC member implementations.

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

– Content Management Interoperability Services (CMIS) Version 1.1 Errata 01

PDF (Authoritative):
http://docs.oasis-open.org/cmis/CMIS/v1.1/errata01/os/CMIS-v1.1-errata01-os.pdf

HTML:
http://docs.oasis-open.org/cmis/CMIS/v1.1/errata01/os/CMIS-v1.1-errata01-os.html

Editable source:
http://docs.oasis-open.org/cmis/CMIS/v1.1/errata01/os/CMIS-v1.1-errata01-os.doc

– Content Management Interoperability Services (CMIS) Version 1.1 Plus Errata 01

PDF (Authoritative):
http://docs.oasis-open.org/cmis/CMIS/v1.1/errata01/os/CMIS-v1.1-errata01-os-complete.pdf

HTML:
http://docs.oasis-open.org/cmis/CMIS/v1.1/errata01/os/CMIS-v1.1-errata01-os-complete.html

Editable source (TeX):
http://docs.oasis-open.org/cmis/CMIS/v1.1/errata01/os/tex/

XML schemas, WSDL and Orderly schema:
http://docs.oasis-open.org/cmis/CMIS/v1.1/errata01/os/schema/

XML and JSON examples:
http://docs.oasis-open.org/cmis/CMIS/v1.1/errata01/os/examples/

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/cmis/CMIS/v1.1/errata01/os/CMIS-v1.1-errata01-os.zip

Members of the OASIS Content Management Interoperability Services (CMIS) TC [1] approved this specification by Full Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve the Errata 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 Content Management Interoperability Services (CMIS) TC
https://www.oasis-open.org/committees/cmis/

[2] Public reviews:
– 15-day public review, 28 August 2015: https://lists.oasis-open.org/archives/members/201508/msg00012.html
– Comment resolution log: http://docs.oasis-open.org/cmis/CMIS/v1.1/errata01/csprd01/CMIS-v1.1-errata01-csprd01-comment-resolution-log.txt

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

15-day Public Review for #MQTT Version 3.1.1 Errata 01 – ends October 29th

The OASIS Message Queuing Telemetry Transport (MQTT) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

MQTT Version 3.1.1 Errata 01
Committee Specification Draft 01 / Public Review Draft 01
03 September 2015

Specification Overview:

This document lists errata for MQTT Version 3.1.1.

Public Review Period:

The public review starts 15 October 2015 at 00:00 UTC and ends 29 October 2015 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:

Editable source (Authoritative):
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/errata01/csprd01/mqtt-v3.1.1-errata01-csprd01.doc

HTML:
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/errata01/csprd01/mqtt-v3.1.1-errata01-csprd01.html

PDF:
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/errata01/csprd01/mqtt-v3.1.1-errata01-csprd01.pdf

ZIP distribution files (complete):

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

http://docs-staging.oasis-open.org/mqtt/mqtt/v3.1.1/errata01/csprd01/mqtt-v3.1.1-errata01-csprd01.zip

Additional information about this specification and the OASIS Message Queuing Telemetry Transport (MQTT) TC may be found on the TC’s public home page located at:

http://www.oasis-open.org/committees/mqtt/

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

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/mqtt-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 ‘MQTT Version 3.1.1 Errata 01,’ 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 Message Queuing Telemetry Transport (MQTT) TC
http://www.oasis-open.org/committees/mqtt/

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

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

5 Committee Specifications are published by the #OBIX TC

OASIS is pleased to announce the approval and publication of five new Committee Specifications by the members of the OASIS Open Building Information Exchange (oBIX) TC:

OBIX Version 1.1
Committee Specification 01
14 September 2015

Encodings for OBIX: Common Encodings Version 1.0
Committee Specification 01
14 September 2015

Bindings for OBIX: REST Bindings Version 1.0
Committee Specification 01
14 September 2015

Bindings for OBIX: SOAP Bindings Version 1.0
Committee Specification 01
14 September 2015

Bindings for OBIX: WebSocket Bindings Version 1.0
Committee Specification 01
14 September 2015

Overview:

OBIX v1.1 provides the core information model (expressed as an XDM) and interaction pattern for interactions with building control systems, or any control systems. The document specifies an object model used for machine-to-machine (M2M) communication which we name the Open Building Information eXchange (OBIX). It also describes the default XML encoding for OBIX.

Encodings for OBIX: Common Encodings v1.0 specifies different encodings for OBIX objects adhering to the OBIX object model. OBIX provides the core information model and interaction pattern for communication with building control systems.

Specific implementations of OBIX must choose how to encode OBIX Information. The core specification describes an XML encoding, which is used in all examples in that document. The document specifies common alternate encodings, including CoAP, EXI, and JSON.

Bindings for OBIX: REST Bindings v1.0 specifies REST bindings for OBIX. The document describes the REST Binding, an interaction pattern that can be used in conjunction with XML, EXI, CoAP, and JSON encodings, as well as other encodings that may be specified elsewhere.

Bindings for OBIX: SOAP Bindings v1.0 specifies SOAP protocol bindings for OBIX. The document describes the SOAP Binding and includes a WSDL artifact.

Bindings for OBIX: WebSockets Bindings v1.0 specifies Web Socket protocol bindings for OBIX. The OBIX Binding for WebSockets was of particular interest to consumer electronics and smart televisions.

TC Description:

The OBIX (Open Building Information Exchange) specification enables enterprise applications to communicate with control systems (e.g. mechanical, electrical, security…) in buildings. Since OBIX 1.0 was released in 2006, it has found wide use as a semantic integration layer, in widespread use for communication between control systems, even within a building or site. OBIX is in wide use for gathering wide area situation awareness, in fleet management, and in perimeter security.

OBIX 1.1 is a refresh cycle that is intended to maintain full compatibility with the installed base of OBIX systems. The Technical Committee (TC) has re-written portions of the specification for improved clarity, and has increased the formal conformance sections. The intent of these changes is to improve interoperability between disparate implementations.

The structure of the OBIX Specification has changed. The core model of OBIX is in the OBIX 1.1 specification. Specific guidelines for Encodings, and for Bindings (REST, SOAP, and Web Sockets) are now in separate specifications. The Encoding specification has added the Constrained Application Protocol (CoAP) as a REST Binding. CoAP is a new IETF specification that is of growing interest to those implementing the Internet of Things in constrained environments, such as wireless sensor networks. The Encodings specification also adds JSON and EXI as two new lightweight options that extend the range of the REST interaction pattern. By moving Encodings and Bindings to separate specifications, the TC sought to make the core specification simpler while making it possible to define other encodings and bindings without revisiting the core.

The core specification now includes an XML Data Model (XDM) described using an XML Schema (XSD). The TC did not consider a normative schema in 2004; including one now will enhance the ability for developers to validate messages and develop code using standards modern toolkits. Reviewers are asked be sure to examine the enclosed schema, which is normative.

Two features have been added to revised specification. An OBIX 1.1 server is able to provide metadata on each control point if available. If this metadata is based on one or more published taxonomies, the metadata is so identified. An OBIX 1.1 server is also able to more compactly deliver large data-sets of telemetry, as for example, an OBIX Historian request for fine-grained interval data over a prolonged period. The model for these large data-sets is compatible with models described in the OASIS specification WS-Calendar and in the Report Services of OASIS Energy Interoperation.

The OBIX Watch functionality has been enhanced to handle the needs of smaller devices as well as of intermittent communications such as cell phones.

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

– OBIX Version 1.1

PDF (Authoritative):
http://docs.oasis-open.org/obix/obix/v1.1/cs01/obix-v1.1-cs01.pdf

HTML:
http://docs.oasis-open.org/obix/obix/v1.1/cs01/obix-v1.1-cs01.html

Editable source:
http://docs.oasis-open.org/obix/obix/v1.1/cs01/obix-v1.1-cs01.doc

XML schema:
http://docs.oasis-open.org/obix/obix/v1.1/cs01/schemas/obix-v1.1.xsd

Core contract library:
http://docs.oasis-open.org/obix/obix/v1.1/cs01/schemas/stdlib.obix

– Encodings for OBIX: Common Encodings Version 1.0

PDF (Authoritative):
http://docs.oasis-open.org/obix/obix-encodings/v1.0/cs01/obix-encodings-v1.0-cs01.pdf

HTML:
http://docs.oasis-open.org/obix/obix-encodings/v1.0/cs01/obix-encodings-v1.0-cs01.html

Editable source:
http://docs.oasis-open.org/obix/obix-encodings/v1.0/cs01/obix-encodings-v1.0-cs01.doc

– Bindings for OBIX: REST Bindings Version 1.0

PDF (Authoritative):
http://docs.oasis-open.org/obix/obix-rest/v1.0/cs01/obix-rest-v1.0-cs01.pdf

HTML:
http://docs.oasis-open.org/obix/obix-rest/v1.0/cs01/obix-rest-v1.0-cs01.html

Editable source:
http://docs.oasis-open.org/obix/obix-rest/v1.0/cs01/obix-rest-v1.0-cs01.doc

– Bindings for OBIX: SOAP Bindings Version 1.0

PDF (Authoritative):
http://docs.oasis-open.org/obix/obix-soap/v1.0/cs01/obix-soap-v1.0-cs01.pdf

HTML:
http://docs.oasis-open.org/obix/obix-soap/v1.0/cs01/obix-soap-v1.0-cs01.html

Editable source:
http://docs.oasis-open.org/obix/obix-soap/v1.0/cs01/obix-soap-v1.0-cs01.doc

– Bindings for OBIX: WebSocket Bindings Version 1.0

PDF (Authoritative):
http://docs.oasis-open.org/obix/obix-websocket/v1.0/cs01/obix-websocket-v1.0-cs01.pdf

HTML:
http://docs.oasis-open.org/obix/obix-websocket/v1.0/cs01/obix-websocket-v1.0-cs01.html

Editable source:
http://docs.oasis-open.org/obix/obix-websocket/v1.0/cs01/obix-websocket-v1.0-cs01.doc

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:

– OBIX Version 1.1
http://docs.oasis-open.org/obix/obix/v1.1/cs01/obix-v1.1-cs01.zip

– Encodings for OBIX: Common Encodings Version 1.0
http://docs.oasis-open.org/obix/obix-encodings/v1.0/cs01/obix-encodings-v1.0-cs01.zip

– Bindings for OBIX: REST Bindings Version 1.0
http://docs.oasis-open.org/obix/obix-rest/v1.0/cs01/obix-rest-v1.0-cs01.zip

– Bindings for OBIX: SOAP Bindings Version 1.0
http://docs.oasis-open.org/obix/obix-soap/v1.0/cs01/obix-soap-v1.0-cs01.zip

– Bindings for OBIX: WebSocket Bindings Version 1.0
http://docs.oasis-open.org/obix/obix-websocket/v1.0/cs01/obix-websocket-v1.0-cs01.zip

Members of the OASIS Open Building Information Exchange (oBIX) 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 Building Information Exchange (oBIX) TC
https://www.oasis-open.org/committees/obix/

[2] Public reviews:
– 30-day public review, 26 July 2013 for OBIX Version 1.1, Encodings for
OBIX: Common Encodings Version 1.0, Bindings for OBIX: REST Bindings
Version 1.0, and Bindings for OBIX: SOAP Bindings Version 1.0:
https://lists.oasis-open.org/archives/tc-announce/201307/msg00010.html

– 30-day public review, 15 January 2014 for OBIX Version 1.1, Encodings for
OBIX: Common Encodings Version 1.0, Bindings for OBIX: REST Bindings
Version 1.0, Bindings for OBIX: SOAP Bindings Version 1.0, and Bindings for
OBIX: WebSockets Bindings Version 1.0:
https://lists.oasis-open.org/archives/tc-announce/201401/msg00006.html
– Comment resolution logs:
http://docs.oasis-open.org/obix/obix/v1.1/csprd02/obix-v1.1-csprd02-comment-log.xls
http://docs.oasis-open.org/obix/obix/v1.1/csprd02/obix-v1.1-csprd02-comment-resolution-log.pdf
http://docs.oasis-open.org/obix/obix-encodings/v1.0/csprd02/obix-encodings-v1.0-csprd02-comment-resolution-log.pdf
http://docs.oasis-open.org/obix/obix-rest/v1.0/csprd02/obix-rest-v1.0-csprd02-comment-resolution-log.pdf
http://docs.oasis-open.org/obix/obix-soap/v1.0/csprd02/obix-soap-v1.0-csprd02-comment-resolution-log.pdf
http://docs.oasis-open.org/obix/obix-websocket/v1.0/csprd01/obix-websocket-v1.0-csprd01-comment-resolution-log.pdf

– 15-day public review, 10 December 2014 for OBIX Version 1.1, Encodings for
OBIX: Common Encodings Version 1.0, Bindings for OBIX: REST Bindings
Version 1.0, and Bindings for OBIX: SOAP Bindings Version 1.0:
https://lists.oasis-open.org/archives/members/201412/msg00001.html
– Comment resolution logs:
http://docs.oasis-open.org/obix/obix/v1.1/csprd03/obix-v1.1-csprd03-comment-resolution-log.pdf
http://docs.oasis-open.org/obix/obix-encodings/v1.0/csprd03/obix-encodings-v1.0-csprd03-comment-resolution-log.txt
http://docs.oasis-open.org/obix/obix-rest/v1.0/csprd03/obix-rest-v1.0-csprd03-comment-resolution-log.txt
http://docs.oasis-open.org/obix/obix-soap/v1.0/csprd03/obix-soap-v1.0-csprd03-comment-resolution-log.txt

– 15-day public review, 05 August 2015 for OBIX Version 1.1:
https://lists.oasis-open.org/archives/members/201508/msg00001.html
– Comment resolution log:
http://docs.oasis-open.org/obix/obix/v1.1/csprd04/obix-v1.1-csprd04-comment-resolution-log.txt

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

30-day Public Review for Emergency Data Exchange Language (EDXL) Tracking of Emergency Patients (TEP) Version 1.1 – ends Nov. 3rd

The OASIS Emergency Management TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted it for 30-day public review:

Emergency Data Exchange Language (EDXL) Tracking of Emergency Patients (TEP) Version 1.1
Committee Specification Draft 01 / Public Review Draft 01
04 August 2015

Overview:

EDXL-TEP is an XML messaging standard primarily for exchange of emergency patient and tracking information from the point of patient encounter through definitive care admission or field release. TEP supports patient tracking across the Emergency Medical Services (EMS) care continuum, as well as hospital evacuations and patient transfers, providing real-time information to responders, Emergency Management, coordinating organizations and care facilities in the chain of care and transport.

Public Review Period:

The public review starts 05 October 2015 at 00:00 UTC and ends 03 November 2015 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.

Reviewers may provide comments directly from the comment-tag version of document. The file

http://docs.oasis-open.org/emergency/edxl-tep/v1.1/csprd01/edxl-tep-v1.1-csprd01-COMMENT-TAGS.html

contains the HTML version of the draft with a “[comment?]” link next to each section heading. Clicking on this link will launch your email application and begin a message to emergency-comment@lists.oasis-open.org with the specific section number and title in the subject line. Simply enter your comment and click send.

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=emergency.

URIs:

The prose specification document and related files are available here:

Editable source (Authoritative):
http://docs.oasis-open.org/emergency/edxl-tep/v1.1/csprd01/edxl-tep-v1.1-csprd01.odt

HTML:
http://docs.oasis-open.org/emergency/edxl-tep/v1.1/csprd01/edxl-tep-v1.1-csprd01.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/emergency/edxl-tep/v1.1/csprd01/edxl-tep-v1.1-csprd01-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/emergency/edxl-tep/v1.1/csprd01/edxl-tep-v1.1-csprd01.pdf

XML schema:
http://docs.oasis-open.org/emergency/edxl-tep/v1.1/csprd01/xsd/

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/emergency/edxl-tep/v1.1/csprd01/edxl-tep-v1.1-csprd01.zip

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

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

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

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/emergency-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 “Emergency Data Exchange Language (EDXL) Tracking of Emergency Patients (TEP) Version 1.1”, 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 Emergency Management TC
https://www.oasis-open.org/committees/emergency/

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

[3] http://www.oasis-open.org/committees/emergency/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#s10.2.2
RF on RAND Mode

Expansion of Legal Service MDE Position Paper V1.0 30-day Public Review – ends Oct. 31st

The OASIS LegalXML Electronic Court Filing TC [1] members have recently approved a Committee Note Draft (CND) and submitted it for 30-day public review:

Expansion of Legal Service MDE Position Paper Version 1.0
Committee Note Draft 01 / Public Review Draft 01
08 September 2015

Overview:

The document contains proposed Limited Service of Process approaches for inclusion in the OASIS LegalXML ECF version 5.0 specification.

Public Review Period:

The public review starts 02 October 2015 at 00:00 UTC and ends 31 October 2015 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.

Reviewers may provide comments directly from the comment-tag version of document. The file

http://docs.oasis-open.org/legalxml-courtfiling/ecf-esop/v1.0/cnprd01/ecf-esop-v1.0-cnprd01-COMMENT-TAGS.html

contains the HTML version of the draft with a “[comment?]” link next to each section heading. Clicking on this link will launch your email application and begin a message to legalxml-courtfiling-comment@lists.oasis-open.org with the specific section number and title in the subject line. Simply enter your comment and click send.

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=legalxml-courtfiling.

URIs:

The prose specification document and related files are available here:

Editable source (Authoritative):
http://docs.oasis-open.org/legalxml-courtfiling/ecf-esop/v1.0/cnprd01/ecf-esop-v1.0-cnprd01.doc

HTML:
http://docs.oasis-open.org/legalxml-courtfiling/ecf-esop/v1.0/cnprd01/ecf-esop-v1.0-cnprd01.html

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/legalxml-courtfiling/ecf-esop/v1.0/cnprd01/ecf-esop-v1.0-cnprd01-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/legalxml-courtfiling/ecf-esop/v1.0/cnprd01/ecf-esop-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:

http://docs.oasis-open.org/legalxml-courtfiling/ecf-esop/v1.0/cnprd01/ecf-esop-v1.0-cnprd01.zip

Additional information about the specification and the OASIS LegalXML Electronic Court Filing TC can be found at the TC’s public home page:

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

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=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 of “Expansion of Legal Service MDE Position Paper 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 LegalXML Electronic Court Filing TC
https://www.oasis-open.org/committees/legalxml-courtfiling/

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

[3] http://www.oasis-open.org/committees/legalxml-courtfiling/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#s10.2.3
RF on Limited Terms

Business Document Envelope V1.0 Committee Specification 01 published by the OASIS Business Document Exchange (#BDXR) TC

OASIS is pleased to announce the approval and publication of a new Committee Specification by the members of the OASIS Business Document Exchange (BDXR) TC

Business Document Envelope Version 1.0
Committee Specification 01
02 August 2015

Overview:

This specification defines a business-oriented artefact enveloping a payload of one or more business documents or other artefacts with supplemental semantic information about the collection of payloads as a whole. This is distinct from any transport-layer infrastructure envelope that may be required to propagate documents from one system to another.

A business document envelope describes contextual information important to the sender and receiver about the payloads, without having to modify the payloads in any fashion.

Description of the TC:

The OASIS BDXR TC advances an open standards framework to support public e-procurement and e-invoicing. The group defines specifications for a lightweight and federated messaging infrastructure that supports a 4-corner model for the secure and reliable exchange of electronic documents.

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

Editable source (Authoritative):
http://docs.oasis-open.org/bdxr/bdx-bde/v1.0/cs01/bdx-bde-v1.0-cs01.xml

HTML:
http://docs.oasis-open.org/bdxr/bdx-bde/v1.0/cs01/bdx-bde-v1.0-cs01.html

PDF:
http://docs.oasis-open.org/bdxr/bdx-bde/v1.0/cs01/bdx-bde-v1.0-cs01.pdf

BDE-Model:
http://docs.oasis-open.org/bdxr/bdx-bde/v1.0/cs01/mod

Schemas:
http://docs.oasis-open.org/bdxr/bdx-bde/v1.0/cs01/xsd

Runt-time schemas:
http://docs.oasis-open.org/bdxr/bdx-bde/v1.0/cs01/xsdrt

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/bdxr/bdx-bde/v1.0/cs01/bdx-bde-v1.0-cs01.zip

Members of the OASIS Business Document Exchange (BDXR) 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 Business Document Exchange (BDXR) TC
https://www.oasis-open.org/committees/bdxr/

[2] Public reviews:
– 30-day public review, 27 March 2015: https://lists.oasis-open.org/archives/members/201503/msg00008.html
– Comment resolution log: http://docs.oasis-open.org/bdxr/bdx-bde/v1.0/csprd01/bdx-bde-v1.0-csprd01-comment-resolution-log.xls

– 15-day public review, 26 June 2015:https://lists.oasis-open.org/archives/members/201506/msg00009.html
– Comment resolution log: http://docs.oasis-open.org/bdxr/bdx-bde/v1.0/csprd02/bdx-bde-v1.0-csprd02-comment-resolution-log.txt

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

Borderless Cyber D.C. Recap

Presentation slides, photos, recordings and wrap-up report now available.

30-day Public Review for #TOSCA Simple Profile in #YAML V1.0 – ends October 20th

The OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted it for 30-day public review:

TOSCA Simple Profile in YAML Version 1.0
Committee Specification Draft 04 / Public Review Draft 01
27 August 2015

Overview:

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 in order to minimize the learning curve and speed the adoption of the use of TOSCA to portably describe cloud applications.

This proposal describes a YAML rendering for TOSCA. YAML is a human friendly data serialization standard (http://yaml.org/) with a syntax much easier to read and edit than XML. As there are a number of DSLs encoded in YAML, a YAML encoding of the TOSCA DSL makes TOSCA more accessible by these communities.

The TOSCA metamodel uses the concept of service templates to describe cloud workloads as a topology template, which is a graph of node templates modeling the components a workload is made up of and as relationship templates modeling the relations between those components. TOSCA further provides a type system of node types to describe the possible building blocks for constructing a service template, as well as relationship type to describe possible kinds of relations.

Public Review Period:

The public review starts 21 September 2015 at 00:00 UTC and ends 20 October 2015 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.

Reviewers may provide comments directly from the comment-tag version of document. The file

http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.0/csprd01/TOSCA-Simple-Profile-YAML-v1.0-csdpr01-COMMENT-TAGS.html

contains the HTML version of the draft with a “[comment?]” link next to each section heading. Clicking on this link will launch your email application and begin a message to tosca-comment@lists.oasis-open.org with the specific section number and title in the subject line. Simply enter your comment and click send. However, do NOT use the table of contents as it will navigate you away from the file.

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

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

HTML with inline tags for direct commenting:
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.0/csprd01/TOSCA-Simple-Profile-YAML-v1.0-csdpr01-COMMENT-TAGS.html

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

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

Additional information about the specification and the Topology and Orchestration Specification for Cloud Applications (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.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 Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
https://www.oasis-open.org/committees/tosca/

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

[3] http://www.oasis-open.org/committees/tosca/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#s10.2.3
RF on Limited Terms Mode

No results with the selected filters