cross-linking more use cases

[derhuerst]

In #7 it sounds like you're collecting more use cases for Deutsche-Bahn-related APIs.

Linking in some old tracking Issues here:

• predict delays and/or disruptions public-transport/ideas#3
• build usable, fast, nice-looking and correct open source apps public-transport/ideas#4
• create non-internet/non-app channels to receive information public-transport/ideas#8
• create an open source "journey planning as a group" bot public-transport/ideas#9

[jschirrmacher]

Cool, thanks, this is exactly what we need. I'll try to transfer this in our Use Cases

[jschirrmacher]

How could public-transport/ideas#8 be an idea for a future Bahn-API? I understand that it focuses on non-internet use-cases, so no API could possibly be used? Could you please explain a little further?

[derhuerst]

How could public-transport/ideas#8 be an idea for a future Bahn-API? I understand that it focuses on non-internet use-cases, so no API could possibly be used? Could you please explain a little further?

non-internet channels:

• apps querying local API endpoints (e.g. an endpoint inside the train/bus wifi)
• apps caching responses from well-designed REST endpoints for offline-use
• API libraries that pull data from static offline data sets (e.g. routing over GTFS sets)
• APIs for P2P use cases, e.g. a routing engine running locally, pulling transit data from a P2P network

non-app (but API-based) channels:

• displays in the public, informing about the current operating status
• scripts that generate non-app content (e.g. network plans, station maps, etc) from APIs
• embedded stuff, e.g. sensors reporting departures/delays/etc.

I think we should keep in mind API use cases beyond the traditional Internet-based client-server model. This will allow us, once there is enough data available, explore many more user experiences than what we have today (very dumb client-server apps & strictly unidirectional communication via public displays).

[jschirrmacher]

Thanks, that makes it a lot more clear for me!
Would you mind to create Markdown files from that and put them into the https://github.com/dbsystel/Bahn-API/tree/master/use-cases folder? I would gladly approve a PR from you!

[derhuerst]

Would you mind to create Markdown files from that

As a repo admin, you can copy the Markdown by clicking "⋯" & "Edit", or by using the Refined GitHub browser extension.

[jschirrmacher]

Thanks for the link! I didn't thought of the Markdown itself, but wanted to encourage you to make separate use cases like the ones in https://github.com/dbsystel/Bahn-API/tree/master/use-cases out of your ideas 😁 .
But never mind, I'll try my best to do that myself. I'll only need a few days.

[derhuerst]

FYI, from public-transport/ideas#3 (comment):

@lenaschimmel and @flauschzelle are working on Dystonse, which is closely related.