Difference between revisions of "Things"
From AMTech WikiDocs
(→Unique addressability of things) |
(→Thing instances) |
||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
==Collections== | ==Collections== | ||
| − | *This views are organized by collections of things types | + | *This views are organized by collections of [[IoT_Semantics#Things_and_Observations_semantic|things types]] |
| − | ** [[Tree_editor#Filter|Filter]] can be applied to show a subset of collections | + | ** [[Tree_editor#Filter|Filter]] can be applied to show a subset of collections |
| + | |||
==Thing instances== | ==Thing instances== | ||
| − | + | Instances can be created, updated, cloned or deleted (See [[Tree_editor#Edition|resources edition]]) | |
| − | + | ||
| − | *[[Tree_editor| | + | The properties of a thing instance are defined in its type [[IoT_Semantics#Things_and_Observations_semantic|semantic]]. |
| + | Some fields are common to every thing type | ||
| + | *[[Location]]: spatial location of the thing. | ||
| + | *[[Proximity area]]: field used for in-room or proximity location. | ||
| + | *[[Floor plan]]: the thing types with the '''floorplan''' checked in its semantic will include this field. It allows the user to associate an image to the thing and to calibrate it spatially: to define a parallelogram in the map so the plan could coincide with the thing location. An example could be to associate a floorplan to a shopping center map boundary so we could locate later the different stores present in the mall. | ||
| + | |||
| + | Navigating to a thing instance makes possible to edit its fields [[Tree_editor|using tree editor]] while fields like [[location]] and [[floor plan]] require the use of the [[spatial view|map]]. | ||
==Apply filters== | ==Apply filters== | ||
| Line 12: | Line 19: | ||
==Unique addressability of things== | ==Unique addressability of things== | ||
| − | *AMTech [[IoT_Restful_API|DAP]] implements it by leveraging on the [[IoT_Semantics#Things_and_Observations_semantic|Semantic Web]] and focusing on making all thing instances addressable by their URI. | + | *AMTech [[IoT_Restful_API|DAP]] implements it by leveraging on the [[IoT_Semantics#Things_and_Observations_semantic|Semantic Web]] and focusing on making all thing instances addressable by their URI. See relevant entry in [https://en.wikipedia.org/wiki/Internet_of_things#Unique_addressability_of_things Wikipedia page on IOT]. |
| − | https://en.wikipedia.org/wiki/Internet_of_things#Unique_addressability_of_things | + | |
Latest revision as of 16:53, 20 December 2016
Collections
- This views are organized by collections of things types
- Filter can be applied to show a subset of collections
Thing instances
Instances can be created, updated, cloned or deleted (See resources edition)
The properties of a thing instance are defined in its type semantic. Some fields are common to every thing type
- Location: spatial location of the thing.
- Proximity area: field used for in-room or proximity location.
- Floor plan: the thing types with the floorplan checked in its semantic will include this field. It allows the user to associate an image to the thing and to calibrate it spatially: to define a parallelogram in the map so the plan could coincide with the thing location. An example could be to associate a floorplan to a shopping center map boundary so we could locate later the different stores present in the mall.
Navigating to a thing instance makes possible to edit its fields using tree editor while fields like location and floor plan require the use of the map.
Apply filters
- It is a good practice to apply filter and/or observers to select the subset of things we would like to work with.
- Using the map spatial filters can be applied
Unique addressability of things
- AMTech DAP implements it by leveraging on the Semantic Web and focusing on making all thing instances addressable by their URI. See relevant entry in Wikipedia page on IOT.
