GSMA in their Iot Big data project has created an ontology for mapping some of the elemtens in the data models.
Now in the folder
data-models > context -> ontologies_files ->gsma.json you have the file you can use with the external @context generator service in the main menu.
Now in the documentation directory of every data model ‘/doc’ you can see two new files spec_IT.md and spec_JA.md that are the Italian and Japanese translations of the specifications.
They are in beta version, (and they are nice automatic translations, but automatic).
|
|
A new data model has been published in the dataModel.Transportation subject belonging to the Smart Cities domain.
It is coming from the use case of IUDX
In the right part of the screen, the last widget logs some of the minor changes that happen on a daily basis in the Smart Data Models Program.
Most of them are thanks to the contributors and people who raise issues in the repositories of the data models.
Only the last ten will be available but if you want the full story you can download the file.
The new service for the generation of externally referenced @context has now available the mapping of the 13 SAREF ontologies.
Check them out in the ontologies_files directory in the data-models repo.
If you want to use data models coming from several subjects you will have to merge (somehow) their @contexts.
In this first step, we offer you a service that allows you to choose what subjects you need to merge and to generate the @context.
See the instructions on the page. Now in Main menu -> @context -> Generate a local context
It also provides you with the conflicts in the attributes’ names, in order to let you solve them manually.
In the next step, possibly next week, you will have another service that will allow you to choose what reference ontologies and vocabularies you want to use and replace the Smart data models IRIs with those coming from these external sources.
The local @context, used by NGSI-LD users of the platform has now taken into account those generic terms which are in the commons-schema.json at the root.
In fact, there is a @context based on these terms named common-context.jsonld.
So, the common terms have an IRI with this pattern https://smartdatamodels.org/term that in most cases is taking you to an actual page with some information about the term.
We the middle of a reorganization of the @context resources.
Our first priority is to not touch the @context that is currently available. We grant you we keep it.
Why is this new option being created?, because otherwise is not possible to solve the conflicts in the IRI when we have attributes with the same ‘name’ but with different meanings. Consequently, their long IRIs (for use in NGSI-LD) need to be different.
The first step is the creation of a local context.jsonld in the root of every subject. It has been made available today.
You can see an example of this local @context for the subject weather.
The long IRI has the format (predictable):
“https://smartdatamodels.org/” +Â subject name + “/” + attribute name
Ej. “precipitation”: “https://smartdatamodels.org/dataModel.Weather/precipitation”,
Soon there will be pages on that IRI (they are in fact URL) with some info about the attribute you could use for any purpose.
1) In the coming future, you will be able to use the local IRI from the Smart Data Models program or commonly used ontologies and vocabularies.
2) A core of attributes will be kept common for many data models e.g. name, description, alternateName, location, address, etc. They will have IRI in the format
“https://smartdatamodels.org/” + attribute name
currently we already have these IRI but there will be also a translator for the properties in the format
“https://smartdatamodels.org/dataModel.Weather/category”: “https://smartdatamodels.org/category”,
3) Additionally, the Smart Data Models to remain interoperable with external ontologies and vocabularies. so there will be also the option to create a @context with external references in the format
“https://smartdatamodels.org/name”: “schema:name”
Your comments are welcomed
The standard GBFS for real-time mobility in bike has been completely mapped (version 2.2) in the subject dataModel.GBFS of the Smart Data Models program.
the standard is maintained by North American Bikeshare and Scootshare association
It is located at dataModel.GBFS subject.
Slack channel
Discord channel #smart-data-models
help on discord
Invitation to discord 
Validate a payload with a data model(external)
