Author: maestro

Extended context.jsonld in all data models

  By

Every subject — a group of data models — has a file named contex.jsonld at their root.

This file contains the @context with automatically generated IRI for the terms used in the data model.

The Entity types are also available in this file with their long IRI.  In the pointed example are the entries for “SeaConditions”, “WeatherAlert”, “WeatherForecast”, and “WeatherObserved”

Remember that if you want to use other IRI coming, for example, from existing ontologies you can use the service on the Home -> Tools -> Mapper @context with external ontologies

updated common-schema.json

  By , , , , , , , , , , , ,

We have noticed an error in the description of the attribute location in the file common-schema.json, a file that is embedded in most of the data models. It does not affect the data types (so the validation of the schemas is not affected) but it affects the qualification of the NGSI type that it is not properly identified,

GeoProperty is written with capital middle P.

The file has been updated and soon it will be launched an update of all the data models affected.

EBSI Verifiable Credentials mapped as data models

  By

There is a new subject – Verifiable Credentials – in the Cross-Sector domain, with 5 data models derived from those at EBSI. Minor changes to be adapted as standard data models. Due to the fact that they are used only in key-values format the examples are only in this format. The @context defined has been removed because they are implicit attributes in NGSI-LD.

Check the derivedFrom metadata in every schema.json file to get to the EBSI source.

ebsi European Blockchain

pysmartdatamodels options in the tools menu

  By , , , , , , , , , , , ,

New options for pysmartdatamodels package. There are a new element in he tools menu to access the pysmartdatamodels package, its documentation, or a code example.

New service for customization of @context with official ontologies

  By , , , , , , , , , , , ,

Some of the data models available are generated according to some ontologies (like dataModels.OSLO). The @context provided for the subject includes IRIs with the smartdatamodels by default, however, the use of official ontologies can be required.

In order to allow this the file notes_context.jsonld was created and also included in the contribution manual (seection 1.5 slide 23).

Now the service for mapping the external ontologies (Home -> tools -> Mapper @context with external ontologies) can detect that instead of a regular configuration file a notes_context.jsonld is provided and applies the replacement of terms defined there.

It can be also used as an API call, in this link you have an example https://smartdatamodels.org/extra/create_external_referenced_context.php?localContext=https://raw.githubusercontent.com/smart-data-models/dataModel.OSLO/master/context.jsonld&configOntologies=https://raw.githubusercontent.com/smart-data-models/dataModel.OSLO/master/notes_context.jsonld

The structure of the notes_context.jsonld has to follow the template

  • {

“@context”: {

“Term1”: “uri_term_1”,

“Term2”: “uri_term_2”,

}

}