Wording improvements in GTFS-Fares v2

This GitHub issue was raised in response to a discussion in #286, and has been prioritized by MobilityData, who is going to work on it with the agenda described below. MobilityData is trying this format to resolve open issues with GTFS extensions - if you have any feedback regarding this format, please reach out to specifications@mobilitydata.org

The need

The specification needs to be clear: it should leave no room for interpretation due to ambiguities in the field definitions.

The issue

It was raised that the wording in some files and fields is unclear, and may be misinterpreted. Particularly for:

• fare_products.amount
• The processing of multi-leg journey costs
• Transfers within blank from_leg_group_id and/or to_leg_group_id
• fare_transfer_rules.transfer_count

Potential options

• Option 1: Do nothing - and leave the wording as-is
• Option 2: Improve the field definitions (I will post a message in this issue with the proposed changes in the coming days)

Recommendation:

MobilityData recommends Option 2 as we want the specification to be as clear as possible.