Should booking without MaaS Connect be in the Scope of this standard ?

[pierrecamilleri]

PR #18 introduces a way of booking without using any MaaS Connect-like mechanism.

Is this a hard requirement that should be covered by the standard, or does it only (possibly) come as a bonus?

The point of view of Mobility by Colas (@levenes-mbc) would be much appreciated.

[ghislainfabmob]

Booking without MaaS Connect is a feature available when using full-API booking. And it seems good to allow both Connect and non-Connect with full-API booking.
When it comes to the "intelligent deeplink" we try to create, we agreed that Connect was not mandatory at the time when you are redirected to the MSP. However nobody expressed a need to go through the entire booking process without MaaS Connect. There was the assumption that at some point in the process the user would have to use MaaS Connect. This means at some point it should be possible to link a journey ID to a user ID.
It raises a new question for me: do we expect the user to connect through a MaaS Connect (I mean an OIDC mechanism that links its 2 accounts in the MaaS and the MSP) or do we allow an authentification at an MSP account unrelated to the MaaS user account? i would advocate that we expect the MSP to synchronise with MaaS the user account and connect them.
=> Question 2: when the user jumps to the MSP booking page he might not be logged in in its MaaS account (or even have one) which raises new possible issues.