Search offers - the 'Delivery' part - 20260702#68
Conversation
edwinvandenbelt
changed the title
…and property updates
| @@ -0,0 +1,25 @@ | |||
| allOf: | |||
There was a problem hiding this comment.
I took the liberty to add 'PlaceHolder' concept, where retailers have the complete list of things they have to complete before they can purchase the package. E.g. personal aspects or choices of allocations/ancillaries.
|
Hmmm. On second thought, why is a 'REQUIRED ANCILLARY' or 'REQUIRED ALLOCATION' connected to the |
|
And why it is a 'TRIP PATTERN SECTION', instead of 'TRIP SECTION'? Now we need to use the tripPatternId explicitly when using sections. Not in all cases the TRIP PATTERN (inbound/outbound) is needed. And you cannot have sections that partly cover the first pattern and partly covers the second pattern... |
|
To be added somewhere: a token indicating that the offer package is valuable only if the customer buys another package with the same token provided by another distributor. That enable lower end-to-end price when a retailer combines 2 offers provided by 2 differents distributors that have aggrements. |
| description: The channel of the offer. | ||
| x-enum-values: | ||
| - "web" | ||
| - "mobile" |
| - completed | ||
| - issued | ||
| - revoked | ||
| - refunded |
There was a problem hiding this comment.
"refund" implies a financial transaction, which relies on retailer's process. "Canceled" would be better
| properties: | ||
| issuer: | ||
| type: string | ||
| description: The entity that issues the entitlement right. |
There was a problem hiding this comment.
it should be possible to have a code here (optional), like RICS code
| - "ISO/IEC 7816-4" # NFC, MIFARE DESFire | ||
| - "GATT" # Bluetooth Low Energy | ||
| - "AXA Bike lock" # AXA Bike lock | ||
| - "OTHER" # Other content standard |
There was a problem hiding this comment.
is calypso NFC card in this list ?
2 participants
This pull request is a large one, and an important one. It contains the draft 'Package', with all details.
A short guideline to help you navigate through all files.
a) start with the
SEARCH OFFER DELIVERY. That is the 'main' concept.it contains
WARNINGs, and a list ofOFFERED PACKAGE(SALES OFFER PACKAGE)b) the
OFFERED PACKAGEinherits fromPACKAGE, and containsPACKAGE ELEMENTs,PRICE(FARE PRICE)SUMMARY DETAILs (describing e.g. (after-sales) conditions)c)
PACKAGE ELEMENTs refer to:travellers (INDIVIDUAL TRAVELLER),luggage,passenger vehicles,animals)TRIP SECTIONs.PRICE(FARE PRICE)PACKAGE ELEMENTis OR aTRAVEL RIGHT, OR anANCILLARY, OR anALLOCATION(for e.g. a seat or bike)d) TRIP has a sequence of LEGs (timed legs, continuous legs, transfer legs), being compliant to OJP. LEGs can be bundled into TRIP PATTERNs using the same trip pattern reference (e.g. 'outbound-P1')
The other concepts are supportive.
The
PACKAGE ELEMENTcan have 'REQUIRED INFORMATION', like a date of birth, license driver's number, address, and so on (x-enum). The requested information should be supplied in the PURCHASE PACKAGE REQUEST (due to GDPR).A 'PACKAGE ELEMENT' can be a TRAVEL RIGHT, an ANCILLARY or an ALLOCATION. And the ALLOCATION itself can be a SPOT ALLOCATION (seat, bike spots etc) or an ASSET ALLOCATION (a scooter, parking spot etc).
Each 'PACKAGE ELEMENT' has a 'TRIP SECTION' where it is valid. This allows that SPOT ALLOCATIONS can be used separately from the TRAVEL RIGHTS (in other words, within a single leg you can have multiple seats, to specify you have to change seats during the ride).