15-Day Committee Specification Draft Public Review Request for OASIS OBIX TC issue Encodings for OBIX: Common Encodings Version 1.0

Submitted on Monday, November 10, 2014 - 15:57
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: OASIS OBIX TC issue Encodings for OBIX: Common Encodings
Version 1.0
Committee Specification Draft ##: CSD03
CSD URI: TBD
Additional Resources:
https://www.oasis-open.org/apps/org/workgroup/obix/download.php/54482/obix-encodings-v1.0-wd14.zip
Approval Link:
https://www.oasis-open.org/apps/org/workgroup/obix/download.php/54511/2014-11-06-obixMinutes.rtf
Previous Public Review Announcement:
https://lists.oasis-open.org/archives/tc-announce/201401/msg00006.html
Abstract: 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.
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.
Notification List: See OBIX 1.1
Notes: Diif log included in Zip archive

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