Open Ludee opened 1 year ago
As far as I understand, we don't have to use the exact naming from the frictionless example. They used, this specific names as they are proposed by this guide of the open data institute.
In general, we could also keep our naming, as these fields are additional fields that are not part of the frictionless specification.
Description of the issue
Latest version has two additional (custom) fields for the license:
attribution
andinstruction
. They are very useful but not conform with frictionless.The documentation has specific keys for this:
Source: https://frictionlessdata.io/blog/2018/03/27/applying-licenses/#provide-additional-license-information
Ideas of solution
attribution
tocopyrightNotice
copyrightStatement
to a link that proves the data is licensedDiscuss:
attributionText
is not conform with TASL. Would be a copy of other keys depending on the licenses.instruction
is a nice-to-have feature that briefly states the rights and obligation. Do we keep it?Workflow checklist