broker

SEDIMARK Data Broker

The SEDIMARK Data Broker is the default store for Data Assets generated by Providers through the SEDIMARK Orchestration Tool, or pushed directly from the data source.

The Broker is also employed by the SEDIMARK Toolbox for storing Asset Descriptions created after the generation of Assets (i.e. Data, AI Models, Services etc.), as a by-product to provide metadata about the Asset.

The Broker is realised through the Stellio Context Broker.

Context

The context defines all properties for each type of Asset :

• Asset (Abstract Class. Properties common to all types)
• DataAsset
• AIModelAsset
• ServiceAsset

Context for reference Use Cases:

• Mobility Management for Municipality Services, Helsinki
  • Air Quality
  • Traffic
  • Place Geometries
• Water Quality and Environment
  • Weather Stations
  • Hydrometric Stations
• Urban Planning for Cycle Routes, Santander
  • Vehicle
  • Vehicle (Bike) Stations
• Domestic Energy Consumption and Churn
  • Energy Consumption

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

additionnal resource https://ngsild.org/