I 76 Add more information for the passenger
To make it possible to create descriptive booking confirmations, itineraries , app-tickets and Resplus-tickets, more information is needed in the booking response from the provider .
See Issue #331 in Git.
E.g.: Reservation is only valid together with a complementary travel pass
The product-object has conditions, but this is not really conditions it is more extended descriptions.
Suggested modelling:
Solution: Added TextElement with attributes description and shortDescription
E.g.
- Please, call the Taxi company 070-222222 two hours before departure to confirm the transport
This is information in DatedJourney on leg-level has no place to be delivered in current OSDM-version
Solution: No change needed, we use DatedJourney.attributes.text with the code set to SERVICE_TEXT
Applied Passenger Categories
E.g.: PERSON with age 17 -> YOUTH
This is information on admission-level similar to appliedReductions. Can we add a list of appliedPassengerTypes?
Suggested modelling:
See issue #332 in Git.
Updates to allow "PERSON" in offer/booking response as well as request (code list update in documentation only)
Solution: Added AppliedPassengerType
E.g.: The ticket is personal. You need to be able to prove your identity onboard the train.
There is no place to deliver this in the current fulfillment resource. Suggested place is an array of descriptive strings in the fulfillmentPart-object
See issue #331 in Git.
Security feature type format
Only graphical types available today. We need a nongraphical alternative
Suggested modelling:
Solution: Added SecurityFeatureType.symbology
E.g.,: Eurail pass
The national distribution service will probably not have all discount cards (from all IMS's) available in Meta Data GET /reduction-cards. Good if the provider returns the name of the reduction together with the code
Suggested modelling, name is added as mandatory in CardTypeReference:
Solution: Modeled as CardTypeReference.cardName.