search

TIDES-transit / TIDES

Transit ITS Data Exchange Specification for historical transit operations data
https://tides-transit.github.io/TIDES
Apache License 2.0
25 stars 4 forks source link

📄🚀 Add factor labels #202

Open e-lo opened 8 months ago

e-lo commented 8 months ago

Describe the feature you want and how it meets your needs or solves a problem

As a TIDES user, I want the labels of enumerated values to be documented in the spec so that their descriptions can be self-documenting.

Describe the solution you'd like

New support for this in Frictionless: https://github.com/frictionlessdata/specs/pull/844

botanize commented 7 months ago

I'm pretty sure enums are enumerated by value in the spec, e.g., https://github.com/TIDES-transit/TIDES/blob/b4d722cff27b0c35a12b27703ebd3a6732df66ef/spec/vehicle_locations.schema.json#L170 and https://tides-transit.org/main/tables/#vehicle-locations.

Are you asking for option 1 (adding "enumOrdered": true), or 2, using integers for the enum values and adding enumLabels? It doesn't look like either of those would make enums any more self-documenting.

Or is this specifically about referencing enums from other sources, like GTFS route types in trips_performed, where we'd need to use option 2 to align the integer values with the GTFS standard?