Resource report data model mapped from OSLO ontology at GreenMov project

There is 1 new data model coming from the collaboration with the GreenMov project. This is a mapping of the OSLO ontology for Personal transport hubs

They are located at the OSLO subject.

  • Resource Report. Resource Report Schema meeting Passenger Transport Hubs AP Schema specification. A summary of resources connected to mobility services based on defined filters by the person requesting the report.

Vista aérea de las colas de acceso a Gibraltar (9460862160) (5)

Contributors: Updated the service for checking your schema

In order to create a new data model or to update an existing one, Check your schema before contributing it, to check the schema on the front page.

The service has been updated to check not only the attributes of the payload but also the schema metadata (schema version, license, derivedFrom, title, description) so it will be easier to complete it before submission.

The code is available at the directory utils in the data-model repository.

Presentations of the Smart Data Models session at FIWARE summit

Here you can have the presentation of the people presenting at the Smart Data Models session of the FIWARE summit.

1.- Fernando Lopez (FIWARE Foundation) SDMX towards context information: achieving interoperability
2.- David Garcia (NTT Data) Public resources monitoring and management through innovative solutions based on extension of smart data models
3.- Mannix manglani (Mannixonline) TOURISM DATA MODELS
4.- Alberto Abella (FIWARE Foundation) Water data models
5.- Antonino Sirchia (Engineering) How FIWARE and Smart Data Models can make a City resilient on Flooding Risks
6.- Romain Magnani (EGM) The NGSI-LD data lab: an engaging interface for building NGSI-LD data configuration
7.- Clara Pezuela (ATOS) GreenMov: Green and smart mobility services
8.- Andrea Cruciani.(FIWARE SmartAgriFood MSC ) Agrigateway
9.- Hugo Miguel Serra (Deloitte) Smart Buildings data models

Training on Smart Data models

Tomorrow at day 0 of the FIWARE summit there will be a training session about Smart Data Models.
Slides are freely shared here

This training will be delivered face to face.

  • Intro:
    • Board and what is Smart Data Models Program
    • Current Status
    • Contributos and dissemintions
  • Agile standardization
    • Current standardization status
    • M.A.S.: Manifesto for agile standardizationç
    • Standardization in a digital market
  • Data model contents
    • Contents of a data model
    • Schema: review
    • Additional documents: examples, contributors, adopters, notes*
    • Generated documents: model.yaml, examples, README, context
  • Data Model creation
    • Incubated repository.
    • From csv, json or open data portals
    • Tests
  • Data Model moderation
    • Data model moderation
  • Future
    • pysmartdatamodels
    • New services. Integration
    • New data models. Mapping of standardizations
    • Other services for the contributors

MAS: Manifesto for Agile Standardization

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.

 

Announcements widget. Just thanks

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

Connecting Open Data Soft open data with Smart Data Models for drafting new data models

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

 

New customization option for context

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.

  1. Merging several contexts and detecting conflicts. (for merging several context from different subjects)
  2. Mapping a context with external ontologies. (mapping a local context from SDM to any external ontology). These are the ones available but more could be easily created on demand.

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.