Price Handling: Unterschied zwischen den Versionen
Aus DRV STRING
(Die Seite wurde neu angelegt: „== Structure of price elements == All total prices will be kept together in a Prices/TotalPrices block in the BooningResponse (String_booking.xsd). To be deci…“) |
|||
| Zeile 2: | Zeile 2: | ||
All total prices will be kept together in a Prices/TotalPrices block in the BooningResponse (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. | All total prices will be kept together in a Prices/TotalPrices block in the BooningResponse (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. | ||
Version vom 21. Juni 2017, 08:46 Uhr
Structure of price elements
All total prices will be kept together in a Prices/TotalPrices block in the BooningResponse (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.
