Difference between revisions of "Things"

Revision as of 16:30, 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)

Navigating to a thing makes possible to edit the instance fields Using tree editor. 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.

Properties

The properties of a thing instance are defined in its type semantic. There are some properties that are common to every type. Beside name and description there are a few that are important to mention:

• Location: spatial location of the thing.
• Proximity area: field used for in-room or proximity location.
• Floorplan: the thing types with the floorplan checked in its semantic, will include this field that allows the user to associate a floorplan 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.