search

VDVde / OJP

Open API for distributed journey planning. CEN/TS 17118:2017.
https://www.vdv.de/open-journey-planner.aspx
22 stars 12 forks source link

Update trip refinement #298

Closed ue71603 closed 1 year ago

ue71603 commented 1 year ago

Based on Malte's comment: Isn't there still a parameter missing in the TripRefine request to select a specific sharing provider when requesting a specific trip with that provider?

And some discussions I had with Andreas and André.

It is now possible to control more, what refinement should do, which system should do it. A lot will need to be described in the specification.

normanoffel commented 1 year ago
  1. It is probably a good idea to indicate in the TripResponse which TripLeg needs to be refined because it is only an estimate.
  2. I assume the SystemID meant to address responding systems which could be added to the documentation annotation.
  3. What is the purpose of the SystemID when for example compared to the OperatorRef? Isn't the original responding system always the one to be asked for refinement as well?
ue71603 commented 1 year ago

Use case 5.24 is adapted.

7.9 and 8.10 will have to be updated after this PR is done. I will add some more information there while finalising this PR.

ue71603 commented 1 year ago

simpliefied a lot. So I guess we have no longer issues with it? @normanoffel @herlitze

@AndreasAtSBB : Pls check, if this still fits the bill for your document.