Ethan Welty

@rufuspollock Fundamentally, the number as it is stored in the text file. Once it is read in, the concept of decimal places may be lost (for example, "1.10" could become...

The simplest I can think of is to allow the `pattern` constraint on at least all field types with string representations (so everything except JSON data stored as JSON rather...

@OriHoch Totally agree. This is an example where limiting choice probably benefits everyone (data authors, consumers, and developers). I'd suggest dropping formats `any` and `default`, scratching field types `date`, `time`,...

@Stephen-Gates Probably a typo, but just in case: `2016-12-25T00:01:01Z+10` should be written as `2016-12-25T00:01:01+10` (or `+10:00` or `+1000`). The `Z` is a shorthand for `+00:00`, aka UTC. See https://en.wikipedia.org/wiki/ISO_8601#Time_zone_designators It's...

In Google and Numpy style, section headers follow a strict formatting. Can these formats be represented by your existing tokens? - google: `\n(Arguments|...)\:\n\t` -> `NEWLINE (ARGUMENTS | ... ) COLON...

In essence, I'm hoping to have something like we have for validating a single table against a remote Table Schema, but for a group of tables (related by foreign keys)...

> When browsing table data, there is a condition, geometry is shown only, when detected type is geography Is there a reason to require the `geography` type (in PostgreSQL)? Both...

> I think we're all aligned on what the issue is here, and I would love to submit a patch. Still on my radar. @dataspun Here is my attempt at...

I would have argued YAML is easier for a non-programmer to read, but in any case I've now made it a habit of also including a markdown and/or pdf rendering....

Continuing the discussion from https://github.com/frictionlessdata/project/discussions/685: @roll Your recent improvements sped things up nicely! Now, my benchmark, which used to take 1125 ms on my machine, now runs in less than...