The ETSI standardization body has just published a new version of the NGSI-LD standard. This is the API standard implemented by the FIWARE components.
The specification can be downloaded from this link.
Some changes are:
The ETSI standardization body has just published a new version of the NGSI-LD standard. This is the API standard implemented by the FIWARE components.
The specification can be downloaded from this link.
Some changes are:
Vessel is a new data model of the subject Marine Transport that is the first one of the new domain Smart Logistics.
Thanks to the I4Trust project
The Manifesto for Agile Standardization (MAS) describes the 7 principles that we apply to the Smart Data Models program.
0. Don't just standardize, be agile and standardize 1. Do not reinvent the wheel 2. Normalize real cases 3. Be open 4. Don't be overly specific 5. Flat not Deep 6. Sustainability is key
If you want to read the agile standardization manifesto’s complete explanation a one-page document is located at the root of our data models repository.
Not all changes in the data models are reported with a blog post, Twitter dissemination o LinkedIn post. But if you notice there is a widget in the right part of the front page (scroll down till Announcements) where these tiny changes are reported (see the image or browse the front page).
Most of them are issues, suggestions or PR solved thanks to the collaboration of the community. They make the data models better for all.
We cannot say thanks individually to all of them but please feel our gratitude.
You can download all of the tiny annoncements from this simple text file.
Just thanks
There is a new subject, dataModel.OSLO, for the mapping of the OSLO ontology for mobility.
A new data model BicycleParkingStation is also available there.
This is also an outcome of the collaboration with the GreenMov project.
There are 3 new data models coming from the collaboration with the GreenMov project.
They are located at the Environment subject.
TrafficEnvironmentImpact. Environmental Impact of traffic based on the vehicles traffic and their emission characteristics
TrafficEnvironmentImpactForecast. Environmental Impact of traffic based on the vehicles’ traffic expectations and their emission characteristics
Many of the datasets published in open data portals are extensively used elsewhere. Well-maintained portals have managers that document the data structure and provide definitions of the types and contents of every field in these datasets. These are some of the requirements for the successful publication of a new Smart Data Model.
With this simple python script (and others to come) at the utils folder it can be drafted a JSON schema compliant with the Smart Data Models Program contribution manual. It is an early version (not everything is updated) but you can check it out.
 Parameters:
– base url of the ODS portal
– dataset_id of the dataset
Returns:
A draft json schema compliant with Smart Data Models Program,
some limitations: it does not translate descriptions (required in English)
some data types
It prints the schema and also returns (if possible a file named schema.json)
test it with this command
SDM_OpenDataSoft_schema_converter.py https://data.ameli.fr/ effectifs
The data model for the electrical charging stations (EVChargingStation) has a major extension with the contributions of IUDX. this is located at the Transportation subject.
It includes attributes for the identification of the vehicle type, others related to the payment and the transaction, and others related to the identification of the station.
The Smart Data Models Program does not define canonically and uniquely the terms used in the data models. There are many ontologies and vocabularies providing solutions to this issue.
For those users of linked data solutions, every subject includes a context.jsonld file (see example) with long IRI for the terms used in the data models. Besides this, the IRI provided are in fact URL to pages with additional information about the term (see example).
not only this but also two services are available on the tools menu on the front page.
But when mapping an existing open and adopted standard now it is possible to customize the context generated by using a new file notes_context.jsonld (see this empty example) at the root of the subject. It will replace the automatic IRI for a term with the customized one.
Usually whenever there is an extension of a data model it is a minor update so it is reported in the widget Announcements of the frontpage
However, the update of the RoadSegment data model is so important (more than 30 new attributes) that it is worthy to be announced this way. It is also noticeable the emphasis on the cycling information. Thanks to IUDX for their contribution. It is available in the Transportation subject.