FIWARE summit presentations. Training on SDM.

In these links you can find the two presentations of the training camp held during past week FIWARE summit.

New forms for joining SDM community

The last option of the menu, now include the forms to join the SDM community in the different roles:

Board Member: Organization managing the SDM together with the existing members FIAWRE, TMForum, IUDX and OASC

Contributor: People who bring new / update data models

Adopter: Organization or project using some of the data models

User: People willing to be informed about the updates on the Smart Data Models initiative

Smart Data Models Session at FIWARE summit

Next 12th of June 17:00 we will have a 1 hour session during the FIWARE summit in Vienna.

The session will be a group of short presentations (<12 min) about actual use cases using Smart Data Models.

Fill out the form if you are willing to participate as a speaker

    By using this form you agree with the storage and handling of your data by this website.

    Entities have their own pages

    In the context.jsonld of every subject there are long IRI for every first-level attribute and for the names of the entities. See this example.

    formerly the link of the attributes took you to an existing web page while the links of the entities take you nowhere. Strictly there is not need to take anywhere, however, it would be useful to create such pages with basic information. Now there are also links to the entities’ pages, where a new page is being created. See this example.

    Now all of them have their own page with these sections

    • Definition
    • Version
    • Original Schema
    • Contributors of the Subject
    • Adopters of the data model
    • Examples of the data model
    • Attributes of the entity
    • Required Attributes

    See here the example for the data model Anomaly.

    MasterSheet for submission of simple data models

    We have released a master sheet that simplifies the contribution to the smart data models.

    It uploads the data model to a new repository called drafted.

    The video help is also available

    Steps for using the spreadsheet

    0.- Make a local copy in your google account and grant permission the first time you use it (it warns you that it is not validated by google, true, but anyhow go to advance and grant the permissions

    1.- Include your example in json key values

    2.- Include the name of the data model, its title, the subject, and the description together with your email

    3.,- Describe the attributes, their NGSI type, their data type, and the written description.

    And click on the two buttons


    updated common-schema.json

    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.

    pysmartdatamodels options in the tools menu

    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

    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

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

    • {

    “@context”: {

    “Term1”: “uri_term_1”,

    “Term2”: “uri_term_2”,