Component/s: 2nd or subsequent public review
Submitted on Monday, November 10, 2014 - 16:02
Submitted by user:
Submitted values are:
Submitter's Name: Toby Considine
TC Name: OBIX
TC Email Address: firstname.lastname@example.org
Work Product Title: OASIS OBIX TC issue Bindings for OBIX: REST Bindings v1.0
Committee Specification Draft ##: CSD03
CSD URI: TBD
Previous Public Review Announcement:
Abstract: Bindings for OBIX: REST Bindings v1.0 specifies REST bindings for
OBIX. The document describes the REST Binding, an interaction pattern that
be used in conjunction with XML, EXI, CoAP, and JSON encodings, as well as
encodings that may be specified elsewhere.
The OBIX (Open Building Information Exchange) specification enables
applications to communicate with control systems (e.g. mechanical,
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
gathering wide area situation awareness, in fleet management, and in
OBIX 1.1 is a refresh cycle that is intended to maintain full compatibility
the installed base of OBIX systems. The Technical Committee (TC) has
portions of the specification for improved clarity, and has increased the
conformance sections. The intent of these changes is to improve
between disparate implementations.
The structure of the OBIX Specification has changed. The core model of OBIX
in the OBIX 1.1 specification. Specific guidelines for Encodings, and for
Bindings (REST, SOAP, and Web Sockets) are now in separate specifications.
Encoding specification has added the Constrained Application Protocol (CoAP)
a REST Binding. CoAP is a new IETF specification that is of growing interest
those implementing the Internet of Things in constrained environments, such
wireless sensor networks. The Encodings specification also adds JSON and EXI
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
other encodings and bindings without revisiting the core.
The core specification now includes an XML Data Model (XDM) described using
XML Schema (XSD). The TC did not consider a normative schema in 2004;
one now will enhance the ability for developers to validate messages and
code using standards modern toolkits. Reviewers are asked be sure to examine
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
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
data over a prolonged period. The model for these large data-sets is
with models described in the OASIS specification WS-Calendar and in the
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: Diff log included in Zip archive
The results of this submission may be viewed at: