• Print
  • Dark
    Light

Change Requests

  • Updated on 08 Jan 2019
  • 3 minutes to read
  • Contributors

Changes in this Release

This page details the changes which were approved and included in the PADIS 18.2 release.

Offer Group

Change RequestItemDescription
CR80 Consolidation of FareRules and OrderRules MessagesThere are currently two sets of messages which can be used to return the rules of an Order. The FareRules message pair returns filed fare rules for a given routing, while the OrderRules message pair return the terms and conditions of a given Order. Proposal is to consolidate the functionality into a single message pair "RulesRQ/RS" which would be able to return either Filed Fare rules, or free text Offer/Order Rules (functionality as it is today). A vote was taken by the Offers Group which passed to consolidate these two messages into one.
CR80 Decommission of Baggage Charge and Allowance MessagesThe NDC restructuring group had updated the AirShoppingRS message in 2017 with BaggageAllowance/Charges information at the Offer level in order to integrate the functionality from these messages into the Offer management messages. This proposal intends to take this work a step further by removing duplicate functionality and encouraging implementers to use the shopping messages as a way to satisfy the baggage requirements.Offers group voted to decommission BaggageAllowanceRQ/RS and BaggageChargesRQ/RS Messages.
CR80Decommission of Baggage List MessageDuring Baggage restructuring discussions in 2017, it was suggested that BaggageListRQ/RS be merged with ServiceListRQ/RS as the messages serve similar functions and maintain similar structures. Offer Group voted to decommission the BaggageListRQ/RS messages while ensuring the RQ functionality from BaggageListRQ exists in ServiceListRQ.
CR80Decommission of FileRetrieve and CustomerInput MessagesThe CustomerInput and FileRetrieve messages have limited usage in implementations today. Offers Group voted to decommission CustomerInputRQ/RS and FileRetrieveRQ/RS NDC Messages
CR80 Decommission of Ticketing MessagesTicketing information exists in both the Order messages as well as separate ticketing messages in NDC. Over the last three years, we have seen limited use of several of the ticketing messages, mostly due to the fact that the functionality already exists in the NDC Order messages (e.g. ability to retrieve ticket history, display ticket information, etc.). Orders Group voted to decommission AirDocDisplayRQ/RS and AirDocHistoryRQ/RS NDC Messages
CR87Currency Code AlignmentSchemas are not consistently using the correct acronym to symbolise currency. To change CurCode to "Cur" as per the standard vocabulary.
CR87Removal of Description IDThe description ID in the ServiceDefinition should not be mandatory as there is no corresponding link and therefore it should be removed as it is not needed.
CR87Removal of Media IDThe Media ID field in the Service Definition is not linked to anything and therefore should be removed. It has no reason to exist.

Order Group

Change RequestItemDescription of Change
CR027Unused ticket as a form of paymentAgents today, especially those in the United States or Canada, can in some cases pass the number of an unused ticket from a cancelled Order as a form of payment towards a new booking.
CR052Payment Card Data Transmission in Distribution cleanupAmend data field names and descriptions by using the wording commonly employed in the card industry, in order to avoid creating confusion for the schema user. Remove data fields that are not relevant at Order level because they refer to the response the airline has received on a card authorization request.
CR063Support of 3D Secure authentication flowAdditional authentication may be required for some credit cards in internet transactions. If the credit card provided at payment time is enrolled for the 3D-Secure (3DS) process, a redirection to a bank's Access Control Server (ACS) is required to perform the user authentication and validate the payment. This step will capture additional security data that need to be transmitted to the merchant. This is 3DS 1.0
CR088Enhancement of schemas following the ONE Order Pilot Review FeedbackThis CR is to cover the enhancements on the ONE Order Messages Schemas, proposed during the 2017 OOPRT review under the ONE Order task force.