roll
BTW `lexical` is already actually used in the spec - http://localhost:8080/specifications/table-schema/#number > The lexical formatting follows that of decimal in [XMLSchema](https://www.w3.org/TR/xmlschema-2/#decimal) This sentence I think is very easy to understand...
> Although reading through the standards again I'm also now realizing that's not quite the case because we're allowing type info to be associated with JSON source data... so it's...
The conversation is happening here so I'm adding @pwalsh's comment: > @nichtich @roll the original terminology seems pretty standard, eg > https://aws.amazon.com/compare/the-difference-between-logical-and-physical-data-model/ > https://www.gooddata.com/blog/physical-vs-logical-data-model/ > Whereas I have never come...
First of all, probably I did not understand it correctly but I never thought about `physical` and `logical` in terms described here - https://www.gooddata.com/blog/physical-vs-logical-data-model/. I was thinking that in the...
Hi @nichtich, Are you interested in working on the updated version of https://github.com/frictionlessdata/datapackage/pull/17 that incorporates comments from this issue? After working closely with the specs last month and refreshing in...
> Table Schema specification defines how to map from level 2 to level 3. I think it's a good wording! > Yes. I'd like to provide an update but I...
> It might also be converted to None, e.g. in case missingValues=[1]. Currently, it cannot because `missingValues` items in v1 have to be strings. So basically, I think we found...
If we lean towards 3 distinct layers (physical/native/logical) as an implementor I'm curious what will be the behaviour for this resource for example: ```yml data: - [id] - [1] -...
> The spec is currently written / defined as (a) a 2-layer scheme. This is why missingValues is string[], and why trueValues/falseValues are string[]: everything should hit the TableSchema as...
I think it will be simple and correct to say that regarding the data model, Table Schema is no more than an extension of a native data format (all of...