OJPFare alignment to OSDM and EUDIT

[ue71603]

• age should be replaced supported by birthday (calculations into the future are necessary
• gender is necessary (for the calculation for some things)
• taxonomies should be supported. E.g. only one ticket, monthly subscriptions etc
• we need to think how advanced existing entitlement_products can be transported in a safe manner (e.g. Libero card for 3 zones based on Bern city, which is different form a Libero card for 3 zones based on Interlaken). This might be done as hash token encoding the "user" to the price calculating system which knows all cards/reductions/birthday etc. already

[schlpbch]

@ue71603 : Thanks for opening, will provide detailed specification and PRs.

[tim-rivett]

I accept that for some use cases "age should be replaced supported by birthday (calculations into the future are necessary" but not all use cases require the date of birth and data protection guidance expects minimisation of personal data so both age & Date of Birth need to be supported with the use case defining which is required to be provided.

[ue71603]

@tim-rivett I had a discussion with @schlpbch reductions in tariff may (senior) or may not (no longer a kid) be available for trips in the future. And on what is age based. without the exact birthday the calculations may result in errors. Gender is required as well for the same reason (when retirement ages are different). So, we need to consider all these factors.

[ue71603]

Manuel Q:
I would have been more comfortable if OJP fares had some products (without prices) and an overall price

The main issue when harmonizing with OSDM is that the OJPFare/fareProduct
is actually quite close from OSDM "fare"
could be considered close from OSDM "product" ... but has a price, which in OSDM is typical of offer/bookingParts
That's my main worry, if we were to consider OJPFare/fareProduct as OSDM/fares or OSDM/products with prices .... that would actually clash with one of OSDM main mechanical part (I mean most statuses, actions runs on offer/bookingParts or fares)