Validating Data Packages

[loleg]

In a recent data literacy workshop, I prototyped a process to authenticate Data Packages (see Frictionless Data, cross-posted here) with my students. The idea is that, after publishing a dataset on the Internet, we would create a document summary of the data (basically an NFT), and use Proxeus to certify it for users.

Built into this document would be some readable and easy-to-follow instructions for using the data, and checking its authenticity and completeness. This would for example help increase confidence in the use of Open Data. A major inspiration for this are the ODI Certificates.

Here are some screenshots of the idea. User-facing form with details of the Data Package:

This should be replaced with just a URL to the location of the datapackage.json so no copy-and-paste is required. Though we may still want to add some fields with information about the person/institution creating the certificate, some evaluation of the dataset, etc. As a next step, the user pays a small gas fee for publishing the certificate:

The resulting PDF certificate can be inspected, downloaded, and additional signature requests made:

Here is the result of a document validation check succeeding:

A screenshot of the admin area where the form is designed:

Feedback welcome!