broker

Context

The context define all the already discussed property for types :

context for helsinki use case

Calling the broker with the context

You can use the “Link” header to define the context of your request when calling the NGSILD-Broker.

<https://sedimark.github.io/broker/jsonld-contexts/sedimark-compound.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json"

creation of assets

An example of asset creation for a broker deployed on “localhost:8080” would be the following :

POST “localhost:8080/ngsi-ld/v1/entities”

body : example here

fetching of asset by id

GET “localhost:8080/ngsi-ld/v1/entities/{id}”

response example

fetching of a list of assets

GET “localhost:8080/ngsi-ld/v1/entities?type=Asset”

temporal entities

If your properties are changing through time, you can add an observedAt value inside the properties to mark the point that they represent in times.

Then you can use the temporal endpoints to fetch the temporal representation. https://stellio.readthedocs.io/en/latest/API_walkthrough.html#get-temporal-evolution-of-attributes