Joey Reid

As far as I can tell, `null`[ is allowed for the enum constraint](https://github.com/frictionlessdata/framework/blob/5e092abae1167c6d8e452cb934b9f202ecf28801/frictionless/schema/field.py#L304)—unless the field is required, then it will fail the required constraint.

True, `gps_quality` is not *required*, so you can use null. I think it would be helpful to communicate this somehow, so that implementers don't need to be familiar with the...

I think it would be great to have a better introduction, especially one that includes motivating examples. The two examples you gave would fit well in a (much talked about,...

I suggest we add an "Extensions" page to the documentation. It should contain recommendations or best practices, derived from the principles we've used to create this spec, e.g., use informative...

> 2. The concept of a loose and unchecked foreign key does come up in other cases, and it would be useful for many use cases, not just TIDES, to...

**Re: heading vs bearing** In navigation heading (direction pointed relative to true north) and bearing (angle between two points) are not the same thing. So I think there are two...

I'd like to add an option: 4. remove `tides.spec.json`, it contains no information not already available in the table schemas, autogenerate table on architecture page from *.schema.json files. e.g., ```python...

Hey @e-lo, this looks like two issues to me: 1. list fields required for desired features 2. decide on a method for communicating feature requirements, e.g., fork repo, feature flags,...

> > Given that this link re-writing is fairly fragile, would it be possible to add CI to check links? > > I agree that we should add a CI...

We receive operator logon/logoff messages with vehicle, operator and timestamps (and duty number, though that isn't always accurate) , so another option that more closely matches our vendor data could...