Difference between revisions of "Observers"
From AMTech WikiDocs
(→Target things) |
|||
| Line 7: | Line 7: | ||
===Target things=== | ===Target things=== | ||
| + | targetthings | ||
"[{\"thingType\":\"/amtech/linkeddata/types/composite/entity/truck\",\"thingsId\":[\"truck888\"], | "[{\"thingType\":\"/amtech/linkeddata/types/composite/entity/truck\",\"thingsId\":[\"truck888\"], | ||
proximityarea}]" | proximityarea}]" | ||
Revision as of 21:06, 3 March 2016
Contents
Things' observers
Activity observers
Follower's observers
API's observers
Target things
targetthings "[{\"thingType\":\"/amtech/linkeddata/types/composite/entity/truck\",\"thingsId\":[\"truck888\"], proximityarea}]" It allows to establish relations between an observation and things instances grouped by type including a proximity area. It offers a tool to resolve thing type instances. From client to server: It can be configured to used by observer to returns just target things instances. The proximityarea is used at the observation enrichment to assigned target things instances with a location. From server to client: Allows to send observations to specific instances. Example m2mBridge leverages this functionality to implement centralized management and send observations.
