roll

@peterdesmet Regarding provisional properties, I think we have an even more eloquent solution for example using a special Data Package Draft/Next extension (or a profile per feature) where we can...

In my opinion, the most pressing issue for v2 is `number` type ambiguity. With a simple example like this: > schema.json ```yaml fields: -name: value type: number ``` > data.csv...

Great @nichtich! BTW have you seen this work bootstrapped on the implementation level: - https://github.com/frictionlessdata/dplib-py/tree/main/dplib/plugins/dcat/models - https://frictionlessdata.github.io/dplib-py/plugins/dcat/

@nichtich That's the DCAT model and the mapper to/from the Data Package model - https://github.com/frictionlessdata/dplib-py/blob/main/dplib/models/package/package.py

Related to #845

Thanks @peterdesmet, updated https://github.com/frictionlessdata/datapackage/commit/e63f8d9bf6025f6ee0550932b9a0d3ef3ef3f2b5 BTW I asked @sapetti9 to add a quick custom properties discussion to the CC as I have some doubts about recommending using colons and also, we...

@pwalsh I really hope they won't =) Over the years all the attempts to make "Frictionless (Data) something" a user-friendly brand were honestly failing as it's very long, still not...

Thanks, everyone! The Data Package (v2) is going to be released today! We will post the update in the announcement issue https://github.com/frictionlessdata/datapackage/issues/854 to notify all the contributors.

I think it might be useful to have a pattern defining best practices for this case

Thanks! I've create an issue for the framework as well - https://github.com/frictionlessdata/framework/issues/1349