roll

> In the physical representations of data where boolean values are represented with strings, the values set in trueValues and falseValues are to be cast to their logical representation as...

We discussed it in Discord and I think that `type: array; format: separator` to have something like: ``` id,array 1,"A,B,C" ``` might make sense for the specs

@AyrtonB It must be a JSONSchema rule in `frictionless/assets/profiles/schema/general.json`. We need to update the `format` definition there for `array` types

I generally like the idea of reducing "magic" for the profile field and using raw URLs. Is there is a plan to drop Data Package Identifier spec also (not implemented...

Extending `number` definitely is a nice option. It can have something like `precision` property: - infinite (default) - double - single I didn't mention it in the first place just...

@drunkcod Currently, Frictionless Framework uses `field.floatNumber` (bool, default: False) - https://framework.frictionlessdata.io/docs/references/api-reference/#fieldfloat_number - similar to `bareNumber` notation - https://specs.frictionlessdata.io/table-schema/#number No support from the specs yet

I think we need to prioritize this feature as it's critical for a lot of cases

Moved to the specs as it's doubtful that we can do it solely on the software level as standard date libraries don't support negative dates (so BCE is a new...

It's definitely a topic for an extensive discussion :smiley:

I agree theoretically it's an implementation level but in reality, it's not possible to support it in any of 10 language implementations without breaking changes unless there is a help...