OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

obix message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: OBIX V1.1 15 day public review ends August 19

The OASIS Open Building Information Exchange (oBIX) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

OBIX Version 1.1
Committee Specification Draft 04 / Public Review Draft 04
25 June 2015

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

Previous public reviews were synchronized for the following specifications:

- Encodings for OBIX: Common Encodings v1.0 which specifies common alternate to XML encoding, including CoAP, EXI, and JSON.
- Bindings for OBIX: REST Bindings v1.0
- Bindings for OBIX: SOAP Bindings v1.0
- Bindings for OBIX: WebSockets Bindings v1.0

The TC determined that no changes were necessary to these allied specifications, and they are not being submitted for additional public review.

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.

The Technical Committee is working on a Committee Note for those beginning to use OBIX.

Public Review Period:

The public review starts 05 August 2015 at 00:00 UTC and ends 19 August 2015 at 2t3: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.

The prose specification document and related files are available here:

PDF (Authoritative):


HTML with inline tags for direct commenting:

Editable source: 


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:


Additional information about this specification and the OASIS Open Building Information Exchange (oBIX) TC may be found on the TC's public home page located at:


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:


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


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 'OBIX Version 1.1', we call your attention to the OASIS IPR Policy [4] applicable especially [5] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member's patent, copyright, trademark and license rights that read on an approved OASIS specification. OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC's work.

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

[1] OASIS Open Building Information Exchange (oBIX) TC 

[2] Previous public reviews: 
- 30-day public review, 26 July 2013: https://lists.oasis-open.org/archives/tc-announce/201307/msg00010.html

- 30-day public review, 15 January 2014: https://lists.oasis-open.org/archives/tc-announce/201401/msg00006.html 
  - Comment resolution logs: 

- 15 day public review, 10 December 2014: https://lists.oasis-open.org/archives/members/201412/msg00001.html
  - Comment resolution log: 

[3] Redlined DIFF file: http://docs.oasis-open.org/obix/obix/v1.1/csprd04/obix-v1.1-csprd04-diff.pdf

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

[5] http://www.oasis-open.org/committees/obix/ipr.php
RF on Limited Terms Mode


Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]