Registration details of the booking registration process with deep-link

[pierrecamilleri]

I report the unresolved discussion found in PR #4, as the PR is being merged in order to have a consolidated branch. The discussion concerns the functional specification of booking with a deep-link.

@osarrat osarrat

A sentence like "If the passenger decides to continue the booking process, the operator SHOULD first redirect the passenger to the operator registration process prior to the booking process if the passenger has not yet a user account registered in the operator platform." should be added, and the the flow summary diagram.

@riclage riclage

@osarrat I removed the sentence fragment "and the passenger was already registered with the operator service." I propose we don't include any reference to a registration process in this spec, since this is up to each operator to decide how to do this. Sentences in the spec like "it is at the operator's discretion to decide how to continue guiding the passenger through the booking process" already imply that the operator can require a registration if they so wish. What do you think?

Link to original comment

[osarrat]

Hi @riclage ,

As mentionned during our live discussion on this issue more than a month ago, it seems important to me that we integrate the topic of the registration in the specification just not to seem to have an hidden corner in it.
In the most recent version of the specification, we could change the sentence 
> If the operator provides a website or if its app was already installed, then clicking on the deep link SHOULD automatically and seamlessly redirect the passenger to the operator's booking flow. It is up to the operator to decide where to start this flow and what to do with the parameters sent to the MaaS app in the search to provide the passenger with the best booking experience. It is up to the passenger to decide whether to book the clicked journey or not.
into
> If the operator provides a website or if its app was already installed, then clicking on the deep link SHOULD automatically and seamlessly redirect the passenger to the operator's booking flow. It is up to the operator to decide where to start this flow and what to do with the parameters sent to the MaaS app in the search to provide the passenger with the best booking experience. It is also up to the operator to decide if, when and how the passenger must register or not for the service. It is up to the passenger to decide whether to book the clicked journey or not.

[riclage]

Hi @osarrat , since the PR was merged, can we close this issue or do you think it is still relevant?