2026-02-13 14:18 UTC
@bovine3dom@masto.ai This technicality is quite interesting, and may be a little mealy-mouthed but also a possible way to bend the rules to do what you want with it: https://opendata.stackexchange.com/a/11260
I am specifically thinking of the idea of sharing an itinerary, the way DBNav does - DBNav creates its own identifier, a uuid, and uses that to reconstruct the data from its own database.
I could see someone sitting down and creating a “open railway share format” that allows somebody to use the various less restrictive data nodes to reconstruct the same information from the more restrictive data. Probably as JSON. This could then become something that is hidden behind a uuid, but crucially could be interpreted by any OpenRailwayShare-enabled app.
Replies (1)
-
@moof@cupoftea.social 2026-02-13 14:20
@bovine3dom@masto.ai Specifically, if I can say “the user wants to see the timetable for train 124 from Point A to point B”, then I don’t need to include the actual timetable data, as that can be derived from the original source.