30-Day CSD Public Review Request for oBIX Version 1.1

Submitted on Thursday, December 19, 2013 - 18:19
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 ##: CSD02
CSD URI: in process - prior request
Additional Resources: completely reorganized, all open for review
Approval Link:
https://www.oasis-open.org/committees/download.php/51816/2013-12-19-obixMinutes.pdf
Previous Public Review Announcement:
https://lists.oasis-open.org/archives/tc-announce/201307/msg00010.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.

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.
Specific implementations of oBIX must choose how to encode oBIX Information.
The
core specification describes an XML encoding, which is used in all examples
in
that document. The document specifies common alternate encodings, including
CoAP, EXI, and JSON.

Bindings for oBIX: REST Bindings v1.0 specifies REST bindings for oBIX. The
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.

Bindings for oBIX: SOAP Bindings v1.0 specifies SOAP protocol bindings for
oBIX.
The document describes the SOAP Binding and includes a WSDL artifact.

Bindings for oBIX: Web Sockets Bindings v1.0 specifies Web Socket protocol
bindings for oBIX.
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
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.

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:
toby.considine@unc.edu
rfa@us.ibm.com
abo@jburk.de
paul.gampe@nextdc.com
mgiannini@tridium.com
harald.e259.hofstaetter@tuwien.ac.at
matthias.hub@de.ibm.com
gjohnson@tridium.com
chkelley@cisco.com
pkrol@tibco.com
ulf.magnusson@tac.com
jsublett@tridium.com
duden@trane.com
robert.zach@tuwien.ac.at
zimmer@caba.org
chet.ensign@oasis-open.org
mberget@trane.com
sboehm@tridium.com
robin@oasis-open.org
udhaya_kumar@trane.com
james.harvey@gsa.gov
thofer@auto.tuwien.ac.at
stamatis.karnouskos@sap.com
carlmattocks@gmail.com
jigar.patel@trane.com
dee.schur@oasis-open.org
cthomas@epri.com
cbvincen@us.ibm.com
kenn@mit.edu
chris.bogen@erdc.dren.mil
bertsch@caba.org
wtcox@coxsoftwarearchitects.com
craig.gemmill@tridium.com
mjung@auto.tuwien.ac.at
jakelee@bspower.co.kr
drjichoi@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
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
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
zach.shelby@sensinode.com
wolfgang.granzer@netxautomation.com
k@auto.tuwien.ac.at
antonio.jara@hevs.ch
skarmeta@um.es
iot6@ipv6forum.com
ntboston@fiatech.org
hberger@realcomm.com
sejones@thes4group.com
marc.petock@lynxspring.com
scottm@j2inn.com
sinclair@automatedbuildings.com
brian@skyfoundry.com
jpetze@gmail.com
jyoung@realcomm.com

Notes:
The TC has asked that the following specs be released together to public
review,
all with a 30 day period:

oBIX Version 1.1 CSD 02
Encodings for OBIX: Common Encodings Version 1.0 CSD 02
OBIX: REST Bindings Version 1.0 CSD 02
Bindings for OBIX: SOAP Bindings Version 1.0 CSD02
Bindings for OBIX: Web Sockets Bindings Version 1.0 CSD01

We also ask that the references in the specifications be aligned so that each
references the others properly:

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