Price Handling: Unterschied zwischen den Versionen
Aus DRV STRING
K (Bachemj verschob die Seite Price handling nach Price Handling, ohne dabei eine Weiterleitung anzulegen) |
K (→Structure of Price Elements) |
||
| Zeile 1: | Zeile 1: | ||
== Structure of Price Elements == | == Structure of Price Elements == | ||
| − | All total prices will be kept together in a Prices/TotalPrices block in the | + | All total prices will be kept together in a Prices/TotalPrices block in the BookingResponse (String_booking.xsd). To be decided: Use a central block for detail prices as well which will the contain an ID reference to the services / travellers they refer to, or keep them with their respective elements. |
The same question arises for the "requested prices" in the BookingRequest - keep them in a central place or with the services they relate to. | The same question arises for the "requested prices" in the BookingRequest - keep them in a central place or with the services they relate to. | ||
TODO: Define the workflow from prices returned by a search or given by external systems to prices from booking availability. | TODO: Define the workflow from prices returned by a search or given by external systems to prices from booking availability. | ||
Aktuelle Version vom 1. August 2017, 13:16 Uhr
Structure of Price Elements
All total prices will be kept together in a Prices/TotalPrices block in the BookingResponse (String_booking.xsd). To be decided: Use a central block for detail prices as well which will the contain an ID reference to the services / travellers they refer to, or keep them with their respective elements.
The same question arises for the "requested prices" in the BookingRequest - keep them in a central place or with the services they relate to.
TODO: Define the workflow from prices returned by a search or given by external systems to prices from booking availability.
