Peter Desmet

@EricStienen I think I managed to identify these. For example: ## B-STO.G The observation right after capture (i.e. the second) has `released after revalidation` and is therefore considered a release...

Ok 😅. I suggest that I look up the records that meet those conditions and that we mark them as `released after revalidation` as well. This will make post-processing easier...

Looking more into this: while there are 678 observations with `release after revalidation` where the **observation_location** does not contain "VOC*", there are far fewer records where the **user_name** does not...

Makes sense, but isn't `uniqueKeys` and array just like `primaryKey`?

I think this can be setup with https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

Looks good to me, indeed good to update contribution guide.

I don't know what the state is of the Open Definition, but if it is indeed not maintained than we should opt for an alternative. SPDX - which I am...

After comparing Opendefinition with SPDX: - SPDX lists a lot more licenses 👍 - The identifiers are exactly the same 👍 except for: - `GFDL-1.3-no-cover-texts-no-invariant-sections` = `GFDL-1.3-no-invariants-or-later` or similar in...

Simple is used for almost all specifications in the v1: https://specs.frictionlessdata.io/ I think we can keep it that way. Let's hope that with enough documentation and a getting started guide,...

I would also suggest to hardcode some of the anchors, rather than auto-generating them. For example: Not: https://datapackage.org/specifications/table-schema/#fields-required Bug: https://datapackage.org/specifications/table-schema/#fields Not: https://datapackage.org/specifications/table-schema/#schema-1 But: https://datapackage.org/specifications/table-schema/#dollar-schema