Define and require "ID stability" for agency_id, route_id, and stop_id fields #171

[Aaron Antrim]

Open for discussion on GitHub:

A proposal to add an "ID stability" term definition:

"Where ID stability is required, ID values must not be reused to describe a different entity than in the original usage. ID values for entities should also be maintained across datasets."

This change would allow applications to depend on more stable IDs.

https://github.com/google/transit/pull/171

[Aaron Antrim]

This is open for discussion for 7 days. Voting will begin next week. Please post comments expressing support, dissent, or requests for changes.

--
You received this message because you are subscribed to the Google Groups "General Transit Feed Spec Changes" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gtfs-changes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gtfs-changes/4B78E960-5DE6-474F-A1D9-2E7C2C124FB5%40mobilitydata.org.
For more options, visit https://groups.google.com/d/optout.

[Aaron Antrim (MobilityData)]

The GitHub thread (https://github.com/google/transit/pull/171) has some great discussion going on.

While there is expressed support for requiring ID stability, there are also concerns about the practical ability of transit agencies and vendors to follow this requirement. We may need to change the proposal. Let's keep the discussion going for at least another 2 weeks.

These contributions to the discussion will be particularly helpful to better inform updates to the proposal right now:

- Examples of use cases that require or benefit from stable IDs.

- Examples of GTFS export practices, including agency, vendor, and post-processing steps -- involving both stable and non-stable IDs.

On Tuesday, July 2, 2019 at 11:48:19 AM UTC-7, Aaron Antrim (MobilityData) wrote:

This is open for discussion for 7 days. Voting will begin next week. Please post comments expressing support, dissent, or requests for changes.

On 1 Jul 2019, at 11:00 PM, Aaron Antrim <aa...@mobilitydata.org> wrote:

Open for discussion on GitHub:

A proposal to add an "ID stability" term definition:

"Where ID stability is required, ID values must not be reused to describe a different entity than in the original usage. ID values for entities should also be maintained across datasets."

This change would allow applications to depend on more stable IDs.

https://github.com/google/transit/pull/171

--
You received this message because you are subscribed to the Google Groups "General Transit Feed Spec Changes" group.

To unsubscribe from this group and stop receiving emails from it, send an email to gtfs-changes+unsubscribe@googlegroups.com.