Thing, Sensor, Actuator, Location, Task, etc presented in the figure, could be considered RESTful resource. [Comments from Xiang Su, Teemu Leppänen] #22
[NOTE: This is from #15. The above link has more than one issues. In order to make it easier to track, I decide to split them into individual issues]
Moreover, Thing, Sensor, Actuator, Location, Task, etc presented in the figure, could be considered RESTful resource, accessed with their own URLs in the physical device, and with their state exposed as the representation of the particular instance. For example, when a new Task is created for a Thing, it is automatically assigned URL address.. POST http://Thing/Task. Then with GET we are able to receive the representation of the task, such as the state of the task.
[NOTE: This is from #15. The above link has more than one issues. In order to make it easier to track, I decide to split them into individual issues]
Moreover, Thing, Sensor, Actuator, Location, Task, etc presented in the figure, could be considered RESTful resource, accessed with their own URLs in the physical device, and with their state exposed as the representation of the particular instance. For example, when a new Task is created for a Thing, it is automatically assigned URL address.. POST http://Thing/Task. Then with GET we are able to receive the representation of the task, such as the state of the task.