2025 Session Notes: Community‐driven data formats

Known (API) Formats:

• Friendly Public Transit Format
• Bahn-Vorhersage internal
• Motis
• OpenTripPlanner

Good practice example (GTFS - now mostly community driven)

Consumers should be there first. -> There needs to be a validation that things work in practice

Format errors are preventable, but data errors still occur and are not related to the

Transmodel:

• GTFS now still trending and gets more recognition by legislators, due to adoption.

Example for custom community standards:

• DB RIS Events (trip / journey data)

Example for lack of standards:

• Wagon stop positions in a station and train arrangement.

Has there be one standard? or can Interoperability solve it.

One example of a domination standard lacking flexibility might be OSM tagging schema -> extending standards exist and solve related issues.

A split of concerns might be helpful to develop interoperable standards.

It's ok (and might be necessary) to say no to contributions / extensions of a standard. -> Guide the people to the right spot to bring there data to (channeling mapping energy).

Should we introduce new ids for journeys? Swiss journey Id is introduced. The community should check if it works for use cases and adopting it.

How standards come to existence?

• Projects come up with

• If more projects adopt it, it becomes a standard

• documenting it is important and needed

How should versioning work?

How can we deprecate things?

Statement: Announcements of different wagon positions for persons

Problem: How well can we convert between formats (losslessly)?

Too little time.. (:

Note pad