1

eG4U/Eurocities Workshop 8-10 October 2018

CONTEXT INFORMATION MANAGEMENT- NGSI-LD API AS BRIDGE BETWEEN SYSTEMS –

Contact: Mike Fisher at NGSI-LD@etsi.org

22

ProprietaryData

Open Data

A.I.

CONTEXT INFORMATION MANAGEMENT:EXCHANGE DATA AND DEFINITIONS (ONTOLOGY)

User Apps

IoT

Context Information Management

APPsAPPs

APPs

PROVENANCE, licensing, privacy. USAGE, Billing, FOAF info, errors?

Provenance Usage

Context Information Ontologies

Context Information Ontologies

Context Information Ontologies

Context Information Ontologies

Context Information Ontologies

Context Information Ontologies

Context Information Ontologies

Context Information Ontologies

3

GOAL: INTERCHANGE DATA AND CONTEXT

ETSI ISG CIM has been working to create a better link or bridge between traditional IoT and database approaches and the semantic web.

We define an API called NGSI-LD.

• The underlying model uses entities identified by URIs and attribute identified by URIs (preferably re-using consensus ontologies)

• It is mandatory that all terms are defined and are referenced via their URIs, but it is not mandatory that the URIs are also URLs.

• The entities can have attributes (Properties or Relationships) which can themselves have attributes i.e. the model is a Property Graph.

The binding of the API for HTTP uses JSON-LD messages, with developer-friendly formatting and mandatory referencing to context information

4

GOAL: KEEP IT SIMPLE, DON‘T RE-INVENT

The API does not re-use SPARQL as the default query language, but is simplified for better performance in distributed and federated architectures, where information can be arbitrarily distributed. It allows filtering and retrieval of entities with their properties and relationships.

The biggest open issues are:

• How should re-use of consensus ontologies be encouraged?

• How get efficient collaboration with many communities?Open Source groups: Project Haystack, Fiware Foundation, Eclipse ...SDOs: SmartM2M (SAREF), CEN/CENELEC, OGC, W3C, oneM2M, ...

• Do our choices/compromises adhere to the most important points for the semantic web, to allow a useful "bridge" between systems?

55

VARIOUS ARCHITECTURES POSSIBLE

Centralised Distributed Federated

Application NGSI-LD API

Simplicity© ETSI 2018. All rights reserved

66

VARIOUS ARCHITECTURES POSSIBLE

Application

More flexibility

Centralised Distributed Federated

NGSI-LD API

© ETSI 2018. All rights reserved

77

VARIOUS ARCHITECTURES POSSIBLE

Application

Integration of multiple Systems

Centralised Distributed Federated

NOTE: functionality of Context Broker or Context

Registry is described in a separate presentation.

Their roles are to allow discovery and authorized

access to repositories of Context Information,

as well as scalable execution of Queries.

NGSI-LD API

© ETSI 2018. All rights reserved

88

EXAMPLE: POLICE REPORT AN ACCIDENT

Vehicle LegalEntity

Source: ETSI ISG CIMModel still under discussion in ETSI ISG CIMEvery Police Department generates tons of data (defined forms) 8

StreetFurniture

The police reports therewas an accident at a certain time and what was damaged

99

EXAMPLE: POLICE REPORT AN ACCIDENT

Vehicle

urn:ngsi-ld:Vehicle:A4567

brandName observedAt

urn:ngsi-ld:Org:Officer123

LegalEntity

inAccident

reportedBy

Source: ETSI ISG CIMModel still under discussion in ETSI ISG CIM

The police reports therewas an accident at a certain time and what was damaged

location

Context Information Ontologies

Town Hall and Police Department share info both more efficient 9

“Mercedes” 2017-07-29T12:00:00 [ 8.672, 49.398]

Entity Type Entity Instance Relationship Property Value

urn:ngsi-ld:SmartLamppostB

:Downtown1

StreetFurniture

1010

EXAMPLE: ENTITY "VEHICLE" AND ITS CONTEXTIN NGSI-LD (BASED ON NGSI AND ON JSON-LD)

{"id": "urn:ngsi-ld:Vehicle:A4567","type": "Vehicle","brandName": {

"type": "Property","value": "Mercedes"

},"inAccident": {

"type": "Relationship","object": "urn:ngsi-ld:SmartLamppostB:Downtown1","observedAt": "2017-07-29T12:00:00","providedBy": {

"type": "Relationship","object": "urn:ngsi-ld:Org:Officer123"

} },

}

"@context": ["http://uri.etsi.org/ngsi-ld/coreContext.jsonld","http://example.org/cim/commonTerms.jsonld","http://example.org/cim/vehicle.jsonld", "http://example.org/cim/parking.jsonld" ]

1111

Need consensus in each domaine.g. Here we see 4 in Buildingse.g. Here we see dozen in IoT ??

EC has begun regulating to reducethese barriers to trade / efficiency !e.g. INSPIRE Directive (deadline 2019)

Metadata, Data Specifications, Network Services, Data and Service Sharing, Spatial Data Services, Monitoring and Reporting

„To ensure that the spatial data infrastructures of the Member States are compatible and usable in a Community and transboundary context, the INSPIRE Directive requires that common implementing Rules (IR) are adopted …”

11

BUT SEVERE LACK OF AGREEDDOMAIN ONTOLOGIES (DEFINITIONS)

121212

BUT SEVERE LACK OF META-DATA: PROVENANCE, QUALITY, LICENSING

Do you label the source and measurement technique? The accuracy?

Do you use timestamps and geospatial attributes?

Do you include a license condition? Or is it "only in the department„

Do you tag personal information for faster GDPR responses?

Source:: http://aura.abdn.ac.uk/bitstream/handle/2164/6051/baillie_acm_jdiq_15.pdf?sequence=1

DO YOURPARTNERS ?

13

WHERE COULD NGSI-LD BUILD BRIDGES?

SmartM2M/SAREF

• Reusing ontologies, hierarchical classes

OGC

• CityGML : detailed consensus ontology; recommend re-use?

• CityJSON : connect CityJSON community to IoT, RDBMS, etc ?

• Confirm/re-use spatial and temporal modelling ?

INSPIRE / JOINUP

• Benefiting from INSPIRE Directive and eGov trends?

© ETSI 2018. All rights reserved

1414

ProprietaryData

Open Data

A.I.

CONTEXT INFORMATION MANAGEMENT:NEEDS COLLABORATIONS FROM ALL SIDES

User Apps

IoT

Context Information Management

APPsAPPs

APPs

Provenance Usage

Context Information Ontologies

Context Information Ontologies

Context Information Ontologies

Context Information Ontologies

Context Information Ontologies

Context Information Ontologies

Context Information Ontologies

Context Information Ontologies

1515

Contact for ETSI ISG CIM: ISGSupport@etsi.org

+ visit at: https://portal.etsi.org/CIM

+ feedback to ngsi-ld@etsi.org

Chairman: Lindsay Frost (NEC)VCs: Christophe Colinet (eG4u) + Mike Fisher (BT)

Open pages for more material:https://docbox.etsi.org/ISG/CIM/Open

... PLEASE JOIN THE EFFORT TO ALIGNCONTEXT INFORMATION STANDARDS

15

16

Dr. Mike FisherBT Chief Researcher, Distributed Computing

Vice-Chair of ETSI ISG CIM

ETSI ISG CIM https://portal.etsi.org/CIM has goal to create an info-exchange layer addressing various domains

ETSI ISG CIM is open to any legal entity (see ApplicationForm)