30-Day CSD Public Review Request for OBIX: REST Bindings Version 1.0

Submitted on Sunday, July 14, 2013 - 14:07
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: REST Bindings Version 1.0
Committee Specification Draft ##: 01
CSD URI: TBD
Additional Resources : http://
Approval Link:
https://www.oasis-open.org/committees/document.php?document_id=49923&wg_abbrev=obix
Abstract: This document specifies REST bindings for oBIX. oBIX provides the
core
information model and interaction pattern for communication with building
control systems. Specific implementations of oBIX must choose how to bind
oBIX
interactions. This 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.
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 and SOAP) 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 Schema (XSD) for oBIX. 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 enclose 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.
Notification List:
bertsch@caba.org
wtcox@coxsoftwarearchitects.com
craig.gemmill@tridium.com
mjung@auto.tuwien.ac.at
toby.considine@gmail.com
pellizzoni.rodolfo@gmail.com
robert.zach@tuwien.ac.at
james.harvey@gsa.gov
ron@rb-cg.com
gershon.janssen@gmail.com
david.holmberg@nist.gov
stephan@enernex.com
dkatz@sustainable.on.ca
bobsmithttl@gmail.com
ko@onuma.com
Bill.W.East@usace.army.mil
zach.shelby@sensinode.com
wolfgang.granzer@netxautomation.com
k@auto.tuwien.ac.at
antonio.jara@hevs.ch
skarmeta@um.es
iot6@ipv6forum.com
phil.davis@schneider-electric.com
francois2.jammes@schneider-electric.com
Mark.Petock@lynxspring.com
sejones@thes4group.com
scottm@j2inn.com
sinclair@automatedbuildings.com
john@skyfoundry.com
angel.stacy@epa.gov
alex.azad@gmail.com
sbhusari@gmail.com
urbienert@prodigy.net
rich@echelon.com
jboch@ipkeys.com
mbordenaro@cs.com
wbrodt@nasa.gov
cb@ibt.ch
david.wollman@nist.gov
thomas.burke@opcfoundation.org
jimbutler@cimetrics.com
capehart@ise.ufl.edu
gceton@csinet.org
achasey@asu.edu
fcleve@xanthus-consulting.com
j.cooper@siemens.com
vijay@gryd.org
sharondinges@gmail.com
realjay2@mac.com
pgannon@gmail.com
GGhatikar@lbl.gov
bparsonnet@comcast.net
jackmcgowan@energyctrl.com
mwebb@theclimategroup.org
mwebb@theclimategroup.org
andreas.tolk@simisinc.com
javs@ieee.org
david.turner@microsoft.com
steve.widergren@pnnl.gov
venerablebede@gmail.com
nick@nicknisbet.com
rakkaray@gmail.com
michael@leppitsch.com
zimmer@caba.org
deke@dksic.net
eric.simmon@nist.gov
sak2113@yahoo.com
starkov71@gmail.com
ralphtaylor01@earthlink.net
rzivney@identive-group.com
rcteal@mac.com
john.teeter@energyos.org
joe.schuch@gmail.com
tracy@engenuity.com
ron.melton@pnl.gov
steve@steveray.com
richard.schomberg@edf.fr
douglas.rice@htng.org
doug.ransom@alumni.uvic.ca
anno@thescholtens.com
mark.litos@litossc.com
mmcgranaghan@epri.com
dmacpherson@cannondesign.com
jmyers333@comcast.net
johnloporto@comcast.net
ulf.magnusson@buildings.schneider-electric.com
david.malkin@ge.com
dpope@coradvisors.net
frabuck@att.net
wlydon@wi.rr.com
manolescue@gmail.com
mammoli@unm.edu
CMMartin@unc.edu
jphillips@spp.org
glushko@sims.berkeley.edu
sggraham@nc.rr.com
ldgussin@gmail.com
bhaaser@gmail.com
alexhabre@hotmail.com
darryl.hamilton06@gmail.com
stephanie.hamilton@sce.com
dave@upperbay.com
jeff.harding@us.abb.com
donna.harper@honeywell.com
lhechtjr@gmail.com
chertzog@smartgridlibrary.com
north.hinkle@hp.com
bhodges33@gmail.com
ghorst@epri.com
matt@onesmugpelican.com
rhuijbre@cisco.com
timothy.d.huneycutt@gmail.com
morenitainfante@yahoo.it
mivanovich@amca.org
gershon@gershon.nl
finith@designatlantic.com
hwjohnson@ieee.org
rkalisch77@gmail.com
myron@pluritas.com
jskatz@us.ibm.com
david.r.kaufman@honeywell.com
sami.kazi@vtt.fi
ProfessorKeel@gmail.com
liana.kiff@honeywell.com
tim.kingston@gastechnology.org
michel@universal-devices.com
mlaherty@cisco.com
mlavelle1942@gmail.com
beverlyr@bnpmedia.com
Notes:
We wish that the public review for 4 CSD01 be announced simultaneously and go
out as a group. As each of these specifications makes normative reference to
at
least one of these others, this means that each is invalidated as it changes
versions.
• oBIX Version 1.1 CSD 01
• Encodings for OBIX: Common Encodings Version 1.0 CSD 01
• OBIX: REST Bindings Version 1.0 CSD 01
• Bindings for OBIX: SOAP Bindings Version 1.0 CSD01
We ask that the TCADMIN assist us in properly aligning the references in
these
specifications in whatever way seems best in their experience. (Quorate vote
on
requesting this change)

We further invite the TCADMIN to consider this issue during the public review
and provide the TC with comments on how to handle this issue best in future
drafts to minimize special handling caused by this issue.

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