OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

obix-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Comments on the oBIX Version 1.1 and JSON Encoding Public Drafts

Dear all,

please find below some comments and thoughts on the committee drafts. Additionally I've shared a proposal regarding a possible oBIX WebSocket Binding, please see https://www.oasis-open.org/apps/org/workgroup/obix/download.php/50167 The comments related to the "WatchService" would enable the message exchange pattern which is used in WebSocket based communication.

oBIX Version 1.1 Committee Specification Draft 01 / Public Review Draft 01 11 July 2013

Following text could be added to chapter 11 "Watches" to support transient (or non-persistent) watches:

The client can either 1) periodically poll the Watch URI using the pollChanges operation to obtain the events which have occurred since the last poll or 2) if the Watch was created with the makePush operation the updates will be pushed to the client as they occur as long as the connection is open.

WatchService is then composed of two operations:

<obj href="">
  <op name="make" in="obix:Nil" out="obix:Watch"/>

  <op name="makePush" in="obix:Nil" out="obix:Watch"/>


WatchService.makePush creates a transient watch which will be deleted on disconnection of the client.

For an Watch object which was created by this operation the existing Watch operations have following semantics:

1) Watch.add: as the existing

2) Watch.remove: as the existing

3) Watch.pollChanges: will throw an err

4) Watch.pollRefresh: will throw an err

5) Watch.delete: will throw an err

Encodings for oBIX: Common Encodings Version 1.0 Committee Specification Draft 01 / Public Review Draft 01 11 July 2013

We suggest

1) to call the structural element "items" instead of "nodes" because of the semantic meaning of the term "node" / "nodes" in HTML context (where JSON is usually used)

2) to call the tag element "type" instead of "tag" - as it seems to be more like a type than a tag, but I guess there are some edge cases where the "type" property is already used?

3) to fix the JSON examples, especially the quotes and comma after "tag" in the second and third line:


{“tag”:”obj”, “href”:”/a/”, “nodes”:[

{“tag”,”obj”, “name”:”b”, “href”:”b”}, “nodes”:[

{“tag”,”obj”, “name”, “c”}, {“tag”,”ref”, “name”, “d”, “href”:”d”}, ]

}] }



"tag" : "obj",
"href" : "/a/",
"nodes" : [ {
"tag" : "obj",
"name" : "b",
"href" : "b",
"nodes" : [ {
"tag" : "obj",
"name" : "c"
                }, {

"tag" : "ref",
"name" : "d",
"href" : "d"
                } ]

        } ]


I am happy to receive your thoughts on my comments!

Mit freundlichen Grüßen / Best regards
Matthias Hub

Solution Development Consultant IBM Connections and Smarter Home matthias.hub@de.ibm.com | +49-7034-643 x1261 | +49-160-7422995
IBM Deutschland Research & Development GmbH Schönaicher Straße 220, 71032 Böblingen Vorsitzender des Aufsichtsrats: Martina Köderitz, Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen, Registergericht: Amtsgericht Stuttgart, HRB 243294

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]