15-Day Committee Specification Draft Public Review Request for oBIX Version 1.1

Submitted on Wednesday, July 1, 2015 - 16:16
Submitted by user:
Submitted values are:

Submitter's Name: Toby Considine
TC Name: OBIX
TC Email Address: obix@lists.oasis-open.org
Work Product Title: oBIX Version 1.1
Committee Specification Draft ##: CSD04
CSD URI: TBD
Additional Resources:
https://www.oasis-open.org/apps/org/workgroup/obix/download.php/56027/Obix%201.1%20Issue%20Tracker%20CSPRD03%20to%2020150701.pdf
Approval Link:
https://www.oasis-open.org/apps/org/workgroup/obix/download.php/55984/2015-06-25-obixMinutes.docx
Previous Public Review Announcement:
https://lists.oasis-open.org/archives/tc-announce/201412/msg00001.html
Abstract:
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.
Notification List:
Holmberg, David david.holmberg@nist.gov
Ron Bernstein ron@lonmark.org
Bob Dolin bobd@echelon.com
Heather Deal heather@lonmark.org
Barry Haaser (barry@lakeviewgroup.com)
Brian Frank brian@skyfoundry.com
steve.ray@sv.cmu.edu
sejones@thes4group.com
paul.price@wems.co.uk
antob@clasma.com
liana.kiff@honeywell.com
mark.litos@litosad.com
cneilson@deltacontrols.com
Dave Robin;
Jim Butler;
Tom Brennen;
Bernhard Isler;
Stephanie Reiniche;
Mike Newman;
Klaus Waechter;
Jerry Martocci; Swan, Bill;
Mark Weber; Steve Bushby;

Notes:
Note that there are artifacts for the OBIX Schema and the OBIX Stdlib.obix
included.

I assume the EA-generated XMI will cause the usual fire drill.
15 days. I think this is the last one.

The results of this submission may be viewed at:
http://tools.oasis-open.org/issues/browse/TCADMIN