Define the simplified SensorThings API about historical-datastore HOT 4 CLOSED

{
  "@iot.id": 5,
  "@iot.selfLink": "http://toronto-bike-snapshot.sensorup.com/v1.0/Things(5)",
  "description": "Ft. York / Capreol Crt. Toronto bike share station with data of available bikes and available docks",
  "name": "7000:Ft. York / Capreol Crt.",
  "properties": {},
  "[email protected]": "http://toronto-bike-snapshot.sensorup.com/v1.0/Things(5)/Datastreams",
  "[email protected]": "http://toronto-bike-snapshot.sensorup.com/v1.0/Things(5)/HistoricalLocations",
  "[email protected]": "http://toronto-bike-snapshot.sensorup.com/v1.0/Things(5)/Locations"
}

I removed nested navigationLinks because they do not add any meta information that is not part of the specification. The links should already be known to clients.

from historical-datastore.

Also, the `@iot.` prefix for control information makes the handling of JSON keys more difficult.

In addition, because of the dot we lose the ability to search objects using jsonpath expressions. Escaping may not always work.

My suggestion is to remove the `iot.` part and change to @id and @selfLink or remove `@iot.` all together. 

from historical-datastore.

+ `@iot.selfLink` is redundant and is difficult to set if service is behind a reverse proxy.

from historical-datastore.

José Ángel Carvajal Soto Marco Jahn Raphael Ahrens Karl Catewicz Hassan Rasheed Any comments?

https://docs.linksmart.eu/display/HDS/Simplified+SensorThings+API

from historical-datastore.