Kyle Husmann

> But the rationale for #875 is a very specific one; namely, to facilitate (if not encourage) the use of categorical variables in the analytic software packages that support them....

Note that this is failing the check for windows-latest (3.6) because the runner is grabbing the latest version of evaluate, which now requires R >= 4.0.0.

I agree, I think it can safely be removed, and it would be a good idea to avoid confusion. For future reference I'll mention here that the only capability of...

If this is the style we want to enforce, we may want to set the [`proseWrap`](https://prettier.io/docs/en/options.html#prose-wrap) option in our `.prettierrc.json` to `never`. This will do a few things: 1. When...

> frictionless-r ignores the resource.compression property. > So I'm neutral regarding promoting this to the specs Agreed -- inferring compression from the path seems just fine. Do we get some...

> I will play a devil's advocate role here, but you know, inferring a Table Schema usually works just fine as well 😃 Haha, to play counter devil's advocate: It's...

> I think, currently, the spec doesn't mention compression at all so the behavior does look just undefined generally speaking. I think we at least need to clarify it. I...

> I think it's more like a convention rather than a standard I agree, I was being sloppy with my language there :) To be clear, I'm neutral on the...

Hmmm isn't it more correct in the singular? Although the primary key for a table may be determined by multiple fields, there is only one primary key definition per table....

> Which isn't what a reader is likely to assume if we say that null values are "excluded". Or what a data packager may want, hence why I originally proposed...