Category: SmartAeronautics

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.

After growing in options and service, it was necessary to update the main menu (not only to make it more legible), but also to make it more natural.

Explore the tools section where all the available services are listed together

Documentation contains everything related to the documentation generated at the SDM and that can be necessary for several tasks

About include mostly the same elements (the starting point and FAQs)

Search remains the same because is one of the most used resources

Community for the interconnection between users and contributors.

New data model request to learn how to start

Every data model in the Smart Data Models program can be mapped with external ontologies and there is a service on the main menu to achieve that.

See main menu -> @context -> generate an external @context

After the publication of data models of CPSV-AP now it is possible to map with their URI thanks to the mapping file.

There is a new service for the creation of schema of a data model when the input is a csv payload.

It is available in the home -> Draft a data model -> Create a data model from csv payload

If you detect any issue or you want to make a suggestion, please send it to info@smartdatamodels.org

test it here

If you want to access a slide with the main parameters for the Smart Data Models Program you can access it through the Main menu -> About -> Statistics

Besides of the parameters updated every hour some slides containing the last parameters o the community like the # of terms, the linked pages, etc.

This is the new content added

Source presentation

We used to have a weekly meeting on Mondays. But this was not very flexible for the actual users. So we have done two things

1. Change the meeting from weekly to monthly (and the content of the meeting will be to report but to provide support)
2. Enable a new service for allocation of a specific slot of support. You can book your own 30 minutes support slot.

Let’s enjoy ourselves.

In our Twitter account @smartdatamodels now it will be twit twice a day (9:00 and 15:00) a link with the chosen data model of the day. Follow

Enjoy!!

The creation of a data model requires two mandatory files, one example and a JSON schema containing the definitions and data types of the elements in the entity.
However, the JSON schema creation could be somehow demanding.
The new tool opens the door for people with only basic knowledge of JSON (every FIWARE user should be proficient in it).
If you have an entity defined in your system just retrieve it in key values format and paste it in this form (available at Menu -> Draft a data model -> Generate your schema out of your payload.

It will return a new page with a raw version of a JSON schema. What you have to check for a final submission?

1.- The title and description of the overall schema

2.- The id address of the schema (you’d need the subject to locate it)

3.- If you want to include any tags

4.- Remove those definitions that does not match your data model and include the missing ones.

so you would be able to make a PR with this JSON schema and your example according to the contribution manual.

Check it here as well