> On 6 Sep 2015, at 09:08, <kajimoto.kazuo@jp.panasonic.com> <kajimoto.kazuo@jp.panasonic.com> wrote: > > Dear TD/AP and WoT members, > > I’m a little bit confused the boundaries between 3 interaction type, that is, “Property”, > “Action” and “Event”. Much of the initial work on the IoT focused on the hardware and local transport protocols. More recently a lot of attention has been on the role of REST based protocols. The choice of protocol will depend on the context, so it is important to consider an architecture which can accommodate a wide range of protocols. The next step will be to focus on application developers and reducing the cost of developing IoT services. Decoupling scripting from the underlying transfer and transport protocols simplifies scripting and enables the protocols to be altered to suit changing circumstances. Web developers are familiar with software objects with properties and methods, as well as event based programming. It therefore is appealing to consider how to model physical and abstract entities as software objects (aka) “things” and to examine how to decouple this from the protocols used to synchronise things and their proxies across a distributed system. Methods thus correspond to actions and may have arguments as input and may return results. In a distributed system, results of actions are asynchronous. Properties for software objects aren’t strictly necessary given methods, and yet are commonplace due to their convenience. Properties many read only or may allow updates through assignments. It is up to the designers to choose whether a property or an action is best suited for any given case. Hoping this helps. Regards, — Dave Raggett <dsr@w3.org <mailto:dsr@w3.org>>
Received on Sunday, 6 September 2015 18:25:06 UTC