Open roll opened 3 months ago
In 2019, we introduced a pattern for schema metadata properties, to be able to describe their name, description and other caracteristics. This helps users to understand schemas and increase their sharing and reuse, for example as part of a cataloging use case.
These metadata properties have since been used by a significative number of schemas, most of which have been created in France and cataloged on schema.data.gouv.fr.
Examples of adoption:
Some of the properties have also been implemented in frictionless-py
:
descriptor
(optional)name
(optional)type
(optional)title
(optional)description
(optional)In order to solidify the growing adoption of the metadata properties and increase the coherence between the spec and implementation, we propose to add a subset of those properties, those most frequently used, to the Table Schema specification and documentation, as part of the v2 Frictionless Data specs.
We will also propose via an issue on the frictionless-py
repository to implement those properties in the library and document them.
All those properties would stay optional to ensure the retrocompatibility of the spec and implementations with existing schemas.
name
:
title
:
description
:
homepage
:
path
:
The direct path to the schema itself can be useful to help accessing it (i.e. machine readability).
sources
:
[
{
"title": "Décret n° 2017-26 du 12 janvier 2017 relatif aux infrastructures de recharge pour véhicules électriques et portant diverses mesures de transposition de la directive 2014/94/UE du Parlement européen et du Conseil du 22 octobre 2014 sur le déploiement d’une infrastructure pour carburants alternatifs",
"path": "https://www.legifrance.gouv.fr/jo_pdf.do?id=JORFTEXT000033860620"
}
]
keywords
:
[
"electric vehicle",
"ev",
"charging station",
"mobility"
]
resources
:
Oftentimes, schemas are shared with example resources to illustrate them, with valid or even invalid files (e.g. with constraint errors).
[
{
"title": "Exemple de fichier IRVE valide",
"path": "https://raw.githubusercontent.com/etalab/schema-irve/v2.3.0/statique/exemple-valide-statique.csv"
}
]
created
:
lastModified
:
version
:
contributors
:
[
{
"title": "Alexandre Bulté",
"email": "validation@data.gouv.fr",
"organisation": "Etalab",
"role": "author"
},
{
"title": "Pierre Dittgen",
"email": "pierre.dittgen@jailbreak.paris",
"organisation": "Jailbreak",
"role": "contributor"
},
...
]
Adding other custom properties, would still be allowed and tolerated by implementations such as frictionless-py
We propose to contribute to all or part of this work.
Thanks a lot, @amelie-rondot!
Would you be interested in creating a PR for this change (please take a look at the v2 Contribution Guideline), or would you like me to work on it?
Hello @roll,
From now, I will not have enough time to continue to work on frictionless
and Validata
projects. But my french colleague Pierre Camilleri takes the lead on it and is interested to create this PR to adopt this change.
Hi @pierrecamilleri,
Amazing! Please let me know if you need any help
Hi @pierrecamilleri,
Please take into account that the changes that will consist Data Package (v2) needs to be accepted by the Working Group by the end of May so we need to make a proposal on this one in next few weeks otherwise it will be in later versions
Thanks for the reminder ! I am currently working on it so I should propose a PR in the coming days if not today.
Overview
The recipe is published here - https://datapackage.org/recipes/metadata-in-table-schema/
It's heavily used in one of the most prominent Data Package adoption cases - http://schema.data.gouv.fr/
I'm ccing @johanricher for more details here