search

EveryMundo / emDataStandards

EveryMundo's Data Standards
7 stars 20 forks source link

Add priceOption to the priceSpecification field #28

Closed BigDataKatha closed 5 years ago

BigDataKatha commented 5 years ago

In order to enable different price options (ROUND_TRIP, ONE_WAY, EACH_WAY) by route in one single fare visualization, we need a label that can be used internally - specifying the airline business logic for a route.

Current priceSpecification object:

{
  "priceBeforeTaxesAndFees": 234.21,
  "totalPrice": 250.6,
  "taxAmount": 16.39,
  "currencyCode": "USD",
  "currencySymbol": "$",
  "isSoldOut": false,
  "priceOffers": [
    "JOURNEY",
    "HOTEL"
  ],
  "totalPriceUSD": 250.6,
  "fuelPrice": 57.89,
  "additionalFeesAmount": 12,
  "priceAdvertised": 250.6,
  "pricingGroupId": "USD-US"
}

Suggested new priceSpecification object with the new field "priceOption":

{
  "priceBeforeTaxesAndFees": 234.21,
  "totalPrice": 250.6,
  "taxAmount": 16.39,
  "currencyCode": "USD",
  "currencySymbol": "$",
  "isSoldOut": false,
  "priceOffers": [
    "JOURNEY",
    "HOTEL"
  ],
  "totalPriceUSD": 250.6,
  "fuelPrice": 57.89,
  "additionalFeesAmount": 12,
  "priceAdvertised": 250.6,
  "pricingGroupId": "USD-US",
  "priceOption": "EACH_WAY"
}
BigDataKatha commented 5 years ago

Not needed because we are using the field flightType for this purpose .