Category: Cross Sector

Distribution and Catalogue from STAT-DCAT-AP new data models published

  By

The mapping of the STAT-DCAT-AP 1.0.1 ha been extended with the mapping of two new classes Distribution and Catalogue in the subject (subject is a group of data models).

Thanks to the collaboration with the project INTERSTAT these two models has been mapped.

  • Catalogue. Catalogue of datasets compliant with STAT-DCAT-AP 1.0.1 specification.
  • Distribution. This is a distribution belonging to a dataset according to the STAT-DCAT-AP standard 1.0.1

Their terms are already available in the @context of the subject.

FIWARE summit: Presentation on SALTED project. Data enrichment.

  By , , , , , , , , , , , ,

Here there are the slides of the SALTED project presented at the session on SDM during past FIWARE summit held at Vienna.

It deals with data enrichment and how to merge heterogeneous data sources.

FIWARE summit presentations. Training on SDM.

  By , , , , , , , , , , , ,

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

New data model DataServiceRun. Candidate for extending DCAT-AP

  By

The new data model, DataServiceRun, is included into the Smart Data Models’ subject DCAT-AP. Initially this subject maps all the contents of the standard DCAT-AP 2.0.1 but also, aligned with the agile standardization philosophy of the initiative, it extends exiting data models and hopefully would be submitted to the original standardization group for its adoption.

Also the data model DataService has also been extended with 3 additional attributes.

DataServiceRun. A representation of one specific run of a data service (e.g. DataService).

New forms for joining SDM community

  By , , , , , , , , , , , ,

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

Subject Saref for systems and 3 DM, Connection, ConnectionPoint and System

  By

The new subject datamodel.S4SYST is mapping the data models from SAREF for systems 1.1.2.

Thanks to the contributors Grzegorz Wiszniewski and Jakob Bjørnskov t the project Twin4Build – A holistic Digital Twin platform for decision-making support over the whole building life cycle.

  • Connection. The class of connections between systems. This class qualifies property s4syst:connectedTo. A connection describes potential interactions between systems. Any two connected systems are connected through a connection. A connection can connect more than two systems at the same time.

  • ConnectionPoint. The class of connection points of systems, at which they may be connected to other systems. This class qualifies properties s4syst:connectsSystem and s4syst:connectedThrough. A connection point belongs to exactly one system. Any system connected through a connection is connected at one of its connection points to the connection. The system of a connection point that is connected through a connection is itself connected through the connection.

  • System. The class of systems, i.e., systems virtually isolated from the environment, whose behaviour and interactions with the environment are modeled. Systems can be connected to other systems. Connected systems interact in some ways. Systems can also have subsystems. Properties of subsystems somehow contribute to the properties of the supersystem.

Primäres System

Smart Data Models Session at FIWARE summit

  By , , , , , , , , , , , ,

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

      By , , , , , , , , , , , ,

    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

      By , , , , , , , , , , , ,

    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

      By , , , , , , , , , , , ,

    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.