roll
Thanks! It will be handled in the Table Dialect Spec - https://github.com/frictionlessdata/specs/issues/697
It took me a while to think about it, and based on the current Table Schema's concept of `physical` (I'm not sure that physical is a good word here it's...
Hi @peterdesmet, Sorry for the confusion. https://github.com/frictionlessdata/datapackage/pull/5 has been reverted and issue returned back to the discussion (I was measled by #864)
I think `nanValues` and `infValues` are really nice proposal! It's not supported by `pandas` or `polars` but can be easily added on the post-processing stage. Currently, I'm removing it from...
The discussion was continued here - https://github.com/frictionlessdata/specs/issues/736 The support was added in `frictionless-py` and we are considering adding it as a part of the specs in v2 (see #736)
It was defined as a pattern - https://specs.frictionlessdata.io/patterns/#missing-values-per-field And now it's a candidate for entering the spec. CLOSING in favor of #861
After quite a long and comprehensive discussion the Data Package Working Group decided to keep `resource.name` required and unique but agreed to remove sluggishness requirements: - https://github.com/frictionlessdata/datapackage/pull/21 - https://github.com/frictionlessdata/datapackage/pull/27
WAS MERGED in https://github.com/frictionlessdata/specs/pull/651
FIXED by https://github.com/frictionlessdata/datapackage/pull/50