Replies: 3 comments 1 reply
-
|
Use case C : booking - reservation |
Beta Was this translation helpful? Give feedback.
-
|
Use case C : booking - reservation. Maybe a question for Team 2 @edwinvandenbelt Asynchroneous Offer and Booking. When the operators behind the distributor have heterogenous response times, even several minutes, a progressive reply could be made to the retailer, with more and more responses as time goes on (with sort of step functions, like with airlines brokers). Do we must take that into account ? I think that no existing specification handle that |
Beta Was this translation helpful? Give feedback.
-
|
Use case D : payment Voucher are given by retailer (not concerned by OTI), distributors or fare product owner. It is a kind of payment, but request the approval of the distributor to be used (value, status, range of use). If the value of the voucher exceed to total amount of eligible CPP, then a new voucher (or an updated voucher) is provided by the distributor as an ancillary offer, which will be booked and fulfiled if the whole booking is validated. Do you agree with that ? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
PLease add you comments directly in Word documents :
Use case C : booking - reservation BUC C
Use case D : payment : BUC D
For general questions about this use cases, use this discussion.
Please find also in the meeting support additional points we discussed today : CR
Beta Was this translation helpful? Give feedback.
All reactions