📄🚀 Add factor labels

[e-lo]

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: frictionlessdata/datapackage#844

[botanize]

I'm pretty sure enums are enumerated by value in the spec, e.g.,

TIDES/spec/vehicle_locations.schema.json

Line 170 in b4d722c

"enum": [

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?