Need single "soldProductId" on offer parts

[ralfbayer-db]

We base some mappings on the product Id returned in an (e.g. admission)offerPart. However, with through fares (e.g. High Speed Train + Local Train), some providers return a list of product IDs for one admission. 

We would need a new attribute "soldProductId", which refers to a product id which contains the relevant parameters from a selling point of view (e.g. refund options etc.).

[ralfbayer-db]

Proposal to add "soldProductId" or "commercialProductId" to the OfferParts - parked until next week as some parties with interest were not present today.

[ralfbayer-db]

The "list of products" was introduced in order to facilitate admissions which have multiple, incompatible refund conditions, e.g. TGV and TER in France.

If that were the case within a single OfferPart, this would have to have conflicting refund conditions valid for the same (or overlapping) date ranges, where it is completely unclear how this should be interpreted by the consuming system. In these cases it would be much cleaner to use serial admission offer parts (e.g. one for the TGV part, and another one for the TER part). Then we could either completely get rid of the product list (and only have one product per offer part), or at least introcude a "commercial product id" which defines things like tariff used and conditions relevant to this offer part.

[ralfbayer-db]

We agreed on an attribute called "summaryProductId".