Open bkuczenski opened 5 years ago
For Rusability and tables we could say we follow the frictionless data package, including the csv dialect. Validating the descriptor ensures some degree of data quality (e.g. non repeated rows or unexpected data types). That would also include the issues we mentioned about separators, and null values.
Apart from the minimum I suggest we add provenance (R1.2) of the data and license (R1.1). What do you think?
what scapes me is how we document the n-n n-1 1-n issues
The FAIR principles for "Findable, Accessible, Interoperable, Reusable" data products are as follows:
To be Findable:
We need to select a subset of these objectives to (a) define in the context of the hackathon and (b) ensure the other groups are attaining them.