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

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.

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.

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

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 test service for contributors. Strongly recommended before contributing a data model.

There is a new service for simplifying the testing of a contribution to a data model.

The new service will check it, just by providing the link to the root of the folder in an publicly accessible repository

  • That the schema.json is
    • Present in the right position
    • It is a valid json and it has the right structure (types and descriptions)
    • It has the right metadata, and the required section
    • External references are valid
    • The descriptions are included
  • That the examples are:
    • Present in the right position
    • Key values are validated by the schema
  • Notes.yaml and ADOPTERS.yaml are present in the right position

all the files (mandatory ones like schema and examples) and the optional (notes.yaml, ADOPTERS.yaml)

There is a specific page for this test in the contribution manual