From ca8d54297874fe9d653be707b7760c911edbd347 Mon Sep 17 00:00:00 2001 From: Michael Ganss Date: Wed, 6 Dec 2017 16:48:10 +0100 Subject: [PATCH] Use type names from interfaces for properties in implementing classes --- XmlSchemaClassGenerator.Tests/XmlTests.cs | 11 + .../xsd/iata/Acknowledgement.xsd | 38 + .../xsd/iata/AirDocDisplayRQ.xsd | 123 + .../xsd/iata/AirDocDisplayRS.xsd | 272 + .../xsd/iata/AirDocHistoryRQ.xsd | 38 + .../xsd/iata/AirDocHistoryRS.xsd | 109 + .../xsd/iata/AirDocIssueRQ.xsd | 176 + .../xsd/iata/AirDocNotifRQ.xsd | 206 + .../xsd/iata/AirShoppingRQ.xsd | 622 + .../xsd/iata/AirShoppingRS.xsd | 706 + .../xsd/iata/AirlineProfileNotif.xsd | 137 + .../xsd/iata/AirlineProfileRQ.xsd | 65 + .../xsd/iata/AirlineProfileRS.xsd | 175 + .../xsd/iata/BaggageAllowanceRQ.xsd | 382 + .../xsd/iata/BaggageAllowanceRS.xsd | 317 + .../xsd/iata/BaggageChargesRQ.xsd | 328 + .../xsd/iata/BaggageChargesRS.xsd | 370 + .../xsd/iata/BaggageListRQ.xsd | 312 + .../xsd/iata/BaggageListRS.xsd | 284 + .../xsd/iata/CustomerInputRQ.xsd | 149 + .../xsd/iata/CustomerInputRS.xsd | 142 + .../xsd/iata/FareRulesRQ.xsd | 138 + .../xsd/iata/FareRulesRS.xsd | 135 + .../xsd/iata/FileRetrieveRQ.xsd | 72 + .../xsd/iata/FileRetrieveRS.xsd | 72 + .../xsd/iata/InvGuaranteeRQ.xsd | 222 + .../xsd/iata/InvGuaranteeRS.xsd | 234 + .../xsd/iata/InvReleaseNotif.xsd | 110 + .../xsd/iata/OfferPriceRQ.xsd | 570 + .../xsd/iata/OfferPriceRS.xsd | 772 + .../xsd/iata/OrderCancelRQ.xsd | 126 + .../xsd/iata/OrderCancelRS.xsd | 246 + .../xsd/iata/OrderChangeNotif.xsd | 579 + .../xsd/iata/OrderChangeRQ.xsd | 854 + .../xsd/iata/OrderCreateRQ.xsd | 561 + .../xsd/iata/OrderHistoryRQ.xsd | 59 + .../xsd/iata/OrderHistoryRS.xsd | 547 + .../xsd/iata/OrderListRQ.xsd | 687 + .../xsd/iata/OrderListRS.xsd | 272 + .../xsd/iata/OrderReshopRQ.xsd | 876 + .../xsd/iata/OrderReshopRS.xsd | 1173 + .../xsd/iata/OrderRetrieveRQ.xsd | 513 + .../xsd/iata/OrderRulesRQ.xsd | 63 + .../xsd/iata/OrderRulesRS.xsd | 83 + .../xsd/iata/OrderViewRS.xsd | 663 + .../xsd/iata/SeatAvailabilityRQ.xsd | 709 + .../xsd/iata/SeatAvailabilityRS.xsd | 1021 + .../xsd/iata/ServiceListRQ.xsd | 370 + .../xsd/iata/ServiceListRS.xsd | 619 + .../xsd/iata/aidm_commontypes.xsd | 814 + .../xsd/iata/edist_commontypes.xsd | 24449 ++++++++++++++++ .../xsd/iata/edist_structures.xsd | 2257 ++ .../xsd/iata/xmldsig-core-schema.xsd | 263 + XmlSchemaClassGenerator/Generator.cs | 52 +- 54 files changed, 45124 insertions(+), 19 deletions(-) create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/Acknowledgement.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/AirDocDisplayRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/AirDocDisplayRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/AirDocHistoryRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/AirDocHistoryRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/AirDocIssueRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/AirDocNotifRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/AirShoppingRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/AirShoppingRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/AirlineProfileNotif.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/AirlineProfileRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/AirlineProfileRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/BaggageAllowanceRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/BaggageAllowanceRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/BaggageChargesRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/BaggageChargesRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/BaggageListRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/BaggageListRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/CustomerInputRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/CustomerInputRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/FareRulesRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/FareRulesRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/FileRetrieveRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/FileRetrieveRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/InvGuaranteeRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/InvGuaranteeRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/InvReleaseNotif.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OfferPriceRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OfferPriceRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OrderCancelRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OrderCancelRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OrderChangeNotif.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OrderChangeRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OrderCreateRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OrderHistoryRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OrderHistoryRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OrderListRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OrderListRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OrderReshopRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OrderReshopRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OrderRetrieveRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OrderRulesRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OrderRulesRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/OrderViewRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/SeatAvailabilityRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/SeatAvailabilityRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/ServiceListRQ.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/ServiceListRS.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/aidm_commontypes.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/edist_commontypes.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/edist_structures.xsd create mode 100644 XmlSchemaClassGenerator.Tests/xsd/iata/xmldsig-core-schema.xsd diff --git a/XmlSchemaClassGenerator.Tests/XmlTests.cs b/XmlSchemaClassGenerator.Tests/XmlTests.cs index 7994dcd7..8fa676b8 100644 --- a/XmlSchemaClassGenerator.Tests/XmlTests.cs +++ b/XmlSchemaClassGenerator.Tests/XmlTests.cs @@ -91,6 +91,7 @@ private Assembly Compile(string name, string pattern, Generator generatorPrototy const string IS24ImmoTransferPattern = @"xsd\is24immotransfer\is24immotransfer.xsd"; const string WadlPattern = @"xsd\wadl\wadl.xsd"; const string ClientPattern = @"xsd\client\client.xsd"; + const string IataPattern = @"xsd\iata\????[^_][^_]?[^-]*.xsd"; [Fact, TestPriority(1)] [UseCulture("en-US")] @@ -110,6 +111,16 @@ public void CanDeserializeSampleXml() TestSamples("Wadl", WadlPattern); Compile("IS24ImmoTransfer", IS24ImmoTransferPattern); TestSamples("IS24ImmoTransfer", IS24ImmoTransferPattern); + Compile("Iata", IataPattern, new Generator + { + EntityFramework = true, + DataAnnotationMode = DataAnnotationMode.All, + NamespaceProvider = new Dictionary { { new NamespaceKey(""), "XmlSchema" }, { new NamespaceKey("http://www.iata.org/IATA/EDIST/2017.2"), "Iata" } } + .ToNamespaceProvider(new GeneratorConfiguration { NamespacePrefix = "Wadl" }.NamespaceProvider.GenerateNamespace), + MemberVisitor = (member, model) => { }, + GenerateInterfaces = true + }); + TestSamples("Iata", IataPattern); } private void TestSamples(string name, string pattern) diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/Acknowledgement.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/Acknowledgement.xsd new file mode 100644 index 00000000..ee77cbba --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/Acknowledgement.xsd @@ -0,0 +1,38 @@ + + + + + + + The Acknowledgement document is a simple notification from party to party acknowledging the receipt of another transaction such as an inventory release or an updated order + + It may also provide information indicating the status of the document. + +This document is used consistently as an optional response to a notification transaction. + + + + + + + Status Code. Example: OK + + + + + Status Message. + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocDisplayRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocDisplayRQ.xsd new file mode 100644 index 00000000..37cfac24 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocDisplayRQ.xsd @@ -0,0 +1,123 @@ + + + + + + + + The AirDocDisplay transaction set requests an Airline to return flight (ET) and/or ancillary (EMD) document details. + + + + + + + + + Air Document Display Request Query. + + + + + + Used to specify they types of documents to display when requested by other than the ticket/document number. + + + + + If true, only display electronic tickets. + + + + + When true, only display EMDs. + + + + + + + Flight information for which a ticket/document is requested. + + + + + + + + + + + + + + The ticket/document number to be displayed. + + + + + The order id for which a ticket/document is requested. + + + + + The frequent flier information for which a ticket/document is requested. + + + + + Passenger check in information for which a ticket/document is requested. + + + + + + + Common NDC Data List choices. + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocDisplayRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocDisplayRS.xsd new file mode 100644 index 00000000..49c28681 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocDisplayRS.xsd @@ -0,0 +1,272 @@ + + + + + + + + The AirDocDisplay transaction returns the results of a payment and ticketing query. + + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + Query Results. + + + + + + + Ticket/document information + + + + + + Ticket/document information. + + + + + + Association to a passenger. + + + + + Booking and Servicing Agent information. + + + + + + + + + + + + Payment information. + + + + + + Payment detail. + + + + + + + + Origin and Destination Airport/ City. + + + + + + The origin city code. + + + + + The destination city code. + + + + + + + + Endorsement/ Restriction text. + + + + + + + + + + Additional Reference information. + + + + + + + + + + Fare Information + + + + + + + + + Fare Tax information. + + + + + + + + + + + + + + + + Fare Tax information. + + + + + Associated Order ID(s) information. + + + + + Commission information. + + + + + + + + Agency or airline specified information associated to the passenger. + + + + + Used to specify tax information for a coupon. + + + + + The reissued flown flight coupon information. + + + + + + + + + + + + Common NDC Data List choices. + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + + + + + + + + + + + + + Air Doc Display Response Message Processing. + + + + + + + + Message Policy information. + + + + + + + When true, processing alerts have been generated and the Alerts node should be parsed. + + + + + When true, supplemental marketing information has been generated and the Notifications/ MarketingMessage node should be parsed. + + + + + When true, business warnings have been generated and the Notification/Warning node should be parsed. + + + + + When true, notices have been generated and the Notifications/Notice node should be parsed. + + + + + + Transaction Processing Results, including processing status, payload content notifices, , business warnings and supplemental marketing messages. + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocHistoryRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocHistoryRQ.xsd new file mode 100644 index 00000000..ddd80957 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocHistoryRQ.xsd @@ -0,0 +1,38 @@ + + + + + + + The AirDocHistory transaction requests the history display of an ET or an EMD. + + + + + + + + + Air Document History Request Query. + + + + + + The ticket/document for which history is requested. + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocHistoryRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocHistoryRS.xsd new file mode 100644 index 00000000..f63565cc --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocHistoryRS.xsd @@ -0,0 +1,109 @@ + + + + + + + The AirDocHistory transaction returns the ticket/document history. + + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + Query Results. + + + + + + + Ticket/document information. + + + + + + + When true, this is the ticket/document number for a ticket/document that is being exchanged. + + + + + When true, this is the primary ticket/document number. + + + + + + + + + + + + + + + + + + + Response Message Processing. + + + + + + + + Message Policy information. + + + + + + + When true, processing alerts have been generated and the Alerts node should be parsed. + + + + + When true, supplemental marketing information has been generated and the Notifications/ MarketingMessage node should be parsed. + + + + + When true, business warnings have been generated and the Notification/Warning node should be parsed. + + + + + When true, notices have been generated and the Notifications/Notice node should be parsed. + + + + + + Transaction Processing Results, including processing status, payload content notifices, , business warnings and supplemental marketing messages. + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocIssueRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocIssueRQ.xsd new file mode 100644 index 00000000..b82a8df8 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocIssueRQ.xsd @@ -0,0 +1,176 @@ + + + + + + + + The AirDocIssue transaction set requests an Airline to issue flight (ET) and/or ancillary (EMD) document(s). + + + + + + + + + Air Document Issue Request Query. + + + + + + + Coupon Creation Information, including Traveler; Order/ Booking Reference ID(s); Promotions and Commission. + + + + + + Association to a passenger. + + + + + Booking Reference information. + + + + + + The order id for which a ticket/document should be issued. + + + + + Promotion information. + + + + + + Promotion Code. + + + + + + + + Payment information. + + + + + + Payment detail, including association(s). + + + + + + + + + + + + Association to one or multiple Order Items instance(s). Example:OI1 OI2 + + + + + + + The airline-assigned unique Order ID. Example: ORDER-c98c-4759-a20b + + + + + Airline Designator of airline that owns/ assigned this ID. Example: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Codes + + + + + The POA OrderID should only go to the ORA, not back to the seller. +1. ORA +2. POA + + + + + + + + + + + + + + + + + + + + + Commission information + + + + + + + + Data Lists(s). + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocNotifRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocNotifRQ.xsd new file mode 100644 index 00000000..12dbda2c --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/AirDocNotifRQ.xsd @@ -0,0 +1,206 @@ + + + + + + + + The AirDocNotifRQ transaction sends an unsolicited document change notification message. The Acknowledgement message may be returned to acknowledge receipt of the notification request. + + + + + + + + + + + Ticket document Notification details. + + + + + + Association to a passenger. + + + + + Coupon Type. Example: Y (EMD-S Standalone) + +Encoding Scheme: IATA Padis Codeset - List for data element 1001 (Document/ Message Name, coded) + + + + + + Coupon Document Number. + +Note: This is the document number comprised of the airline code, form code, and serial number. + + + + + + + + + + + Date of Issue. Example: 2017-01-13 + + + + + Coupon Notification details. + + + + + + Applicable coupon number. Example: 1234 + + + + + + + + Type of Service. + + + + + Service date. Example : 15-08-2015 + + + + + Service Details. + + + + + + Service Action Code E.g. HK, HL (use PADIS Codeset) + + + + + Quantity of Services. Example : 3 + + + + + Location Code. Example : LON + + + + + + + Location Indicator Type. Example : Primary or Secondary + + + + + + + + + Service name. Example: Lounge Pass + + + + + + + + + + + Reason For Issuance Sub Codes + + + + + + + + Flight Details. + + + + + + + + + Service Action Code E.g. HK, HL (use PADIS Codeset) + + + + + + + + + + + + + + + + + Common NDC Data List choices. + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/AirShoppingRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/AirShoppingRQ.xsd new file mode 100644 index 00000000..d8cd0fc5 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/AirShoppingRQ.xsd @@ -0,0 +1,622 @@ + + + + + + + + The AirShopping transaction set supports both demanding and flexible shopping experiences for anonymous or personalized shopping. + +The combination of functionally-rich attribute and affinity shopping support date range or specific month (calendar) shopping as an example. + +The response returns offers which may include branded offers or itinerary-priced offers with or without ancillary services. It also returns applicable rules for the integrated fares as well as for each service. + +The message also returns multi-media content at message level as well as media references at the individual offer level. + + + + + + + + + Parameters that influence overall message results. + +Supported Parameter Groups: Inventory Guarantee (offer-associated); Service Filter (offer-associated); Pricing. + +Note: These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Core Air Shopping information by supported Air Shopping Query type. + +Shopping Query Input may be specified as: +1) Prior Shopping Session Basket +2) Attribute Shopping Query +3) Affinity Shopping Query + + + + + + + ATTRIBUTE Query ORIGIN/ DESTINATION qualifiers and preferences. + +Note: +1. An Attribute Query is a search specifying one or more attributes to get more focused results Note that this node only contains Origin/ Destination Airport/ City code information which are mandatory. + +2. Other Attribute Query parameters that may be specified (in other document nodes) include Aircraft Equipment preferences, Seat types and characteristics, Meal preferences and Special Need qualifiers. + + + + + + + + + + Qualifier choices. + +Notes: +1. These qualifiers may be specified for (e.g. apply to) both Attribute and Affinity queries. +2. These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of the capability is not dictated by this specification. + + + + + + + + + + + + + + + + + Contains Forms of Payment type and may include a reference to a passenger. + + + + + + Association to multiple Passenger instance(s). Example: Passenger1 Passenger2 + +Note: May be Recognized or Anonymous Passenger (by PTC) instance(s). + + + + + The form of payment type. Examples: Credit Card, Cash. + +Encoding Scheme: IATA PADIS code list data element [9888] Form of Payment Identification + + + + + + + + + + + Preference choices. + +Notes: +1. These preferences may be specified for (e.g. apply to) both Attribute and Affinity queries. +2. These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of the capability is not dictated by this specification. + + + + + + + + + + + + + + + + + + + Common NDC Data List choices. + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + + + Metadata List(s). + + + + + + + + + + Message Policy information. + + + + + + + + + Air Shopping Request Metadata definition. + + + + + Shopping Query-Related Metadata. + + + + + + + + + + Passenger Metadata List(s). + + + + + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A data type for Air Shopping Request Message Parameters. + +Notes: +1. Derived from MessageParamsBaseType. + + + + + + + Inventory guarantee for Offers in search results. + + + + + + When true, inventory guarantee is requested for applicable Optional Services. + +Note: This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of this capability is not dictated by this specification. + + + + + + + + Group and subgroup code(s) that specify the requested categories of Optional Services to be returned in the results. + + + + + + + + Service group and subgroup code(s). + + + + + + + + + + Pricing Parameters, including Simple Pricing, Award Travel, Auto Exchange, Override Currency and Fee Exemption. + + + + + + Requested override currency code for pricing. +Example: EUR + + + + + Fee exemption application for Offer pricing. + + + + + + + + Exemption(s) based on tax codes plus (optional) tax types within a tax code. + + + + + + Exempt tax code. +Example: YQ/YR + + + + + + + Airport code location for exempt ZP or XF taxes. +Example: MIA + For maximum interoperability, it is recommended that IATA (three character) Airport/ City Code values be used. Use an IATA code or a proprietary string value. + +http://www.iata.org/publications/Pages/code-search.aspx + + + + + + + + + Tax type(s) within the tax code. Examples: I, C + + + + + + + + + + Exempt province(s). + + + + + Entity name. + =notes=: +1. This must be provided for certain exemptions in the Canadian market. + + + + + + + + + + + When true, this request is to be handled by an auto-exchange process + + + + + When true, award eligible in addition to priced offers and fares is requested. + + + + + When true, only award eligible offers/ fares are requested. + + + + + When true, Simple Pricing for flight offers is requested. + + + + + + + Group-related Offer Information. + + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + + AFFINITY QUERY Qualifiers and Preferences. + +Notes: +1. An affinity search is a wide search defining a range of criteria including: + +-Origin/ Destination Location: Airport/ City, State/ Province, Reference Point (includes Search Proximity.) Note that one instance of Departure (origin) location must be specified, but Arrival (destination) is optional as it may be calculated by the airline and returned in priced flight offers. +-Trip Time Periods: Date Range, Season (include with minimum and maximum day qualifiers) +-Travel Budget: Per Person, Per Group +-Keyword Value pairs may be used to specify a variety of affinity qualifiers, such as Climate, Activity, and Point of Interest. +-Trip Travel Time, Duration + +2. These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + AirShopReq Business Object: FLIGHT SPECIFIC definition. + + + + + FlighSegment information. Contains details flight segment information. + + + + + + + + Marketing Carrier information. + + + + + Operating Carrier information. + +Note: This is the carrier that holds the Air Operator’s Certificate for the aircraft used for that flight. + + + + + + A globally unique identifier for this Flight Segment instance. Example: segment1 + + + + + + + Flight information. Flight can be made of one to multiple FlightSegment elements. For example Flight can be made of flight segment BA123 and BA34. + + + + + + Flight journey information. + + + + + + + + A globally unique identifier for this Flight instance. Example: flight1 + + + + + + + + + + A data type for AirShopReq Business Object: ATTRIBUTE QUERY definition. + + + + + Flight origin/ destination information. + + + + + + + + FLIGHT DEPARTURE (ORIGIN). + + + + + FLIGHT ARRIVAL (DESTINATION). + + + + + + Flight-related shopping response IDs, including the unique (master) Shopping Session ID, Offer IDs, Offer Item IDs and Service IDs. + + + + + + Indicates a calendar search request with days before and/or days after the specified date. + + + + + Number of days befiore the specified date. + + + + + Number of days after the specified date. + + + + + + + + A globally unique identifier for this OriginDestination instance. Example: origDest1 + + + + + + + + + + + AirShopReq Business Object: AFFINITY QUERY definition. + + + + + Flight origin/ destination information. + + + + + + + + + + + + + + + + + + + + + + + + + + Trip Budget. + + + + + + + + + + + Affinity Query Keyword(s) with optional preference level. + + + + + + Keyword/ Value Search Criteria. + +Note: Keyword-Value pairs may be used to specify a variety of affinity qualifiers, such as Climate, Activity, and Point of Interest. + + + + + + + + + + + + + + + + + + FLIGHT SPECIFIC QUERY Qualifiers and Preferences. + +Notes: +1. A flight specific search is a search for fares for specific listed flights only. + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/AirShoppingRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/AirShoppingRS.xsd new file mode 100644 index 00000000..395e370a --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/AirShoppingRS.xsd @@ -0,0 +1,706 @@ + + + + + + + + The AirShopping transaction set supports both demanding and flexible shopping experiences for anonymous or personalized shopping. + +The combination of functionally-rich attribute and affinity shopping support date range or specific month (calendar) shopping as an example. + +The response returns offers which may include branded offers or itinerary-priced offers with or without ancillary services. It also returns applicable rules for the integrated fares as well as for each service. + +The message also returns multi-media content at message level as well as media references at the individual offer level. + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + + + Offers Grouped by Airline Supplier. + + + + + + + Container element for the set of Offers constructed and returned by a single Offer Responsible Airline. + + + + + + + A collection of Offer Items. + + + + + + + + Summary of proposed flight information in the context of this specific Offer. + + + + + + Reference to the Flight ID specified within this Offer. Should be repeated for all Flights included. + + + + + + + Reference to the Origin/Destination ID specified within this Offer. + + + + + Flight-level price class + + + + + + + + + Itinerary-level price class (eg. most restrictive applies) + + + + + + + + A set of one or more Services. The Offer Item assigns a total price for all included services for all passengers and all segments referenced. Once constructed, the OfferItem cannot be modifed. + + + + + This block contains references to the Baggage Allowance characteristics (no. of pieces / weight / dimensions, etc) included in the Flight services for one or more Passengers. + + + + + + Reference to FlightIDs in DataLists + + + + + Reference to PassengerIDs in DataLists + + + + + Reference to BaggageAllowanceIDs in DataLists + + + + + + + + + + + + + Container for standalone optional OfferItems. This supports the shopping basket concept. The main purpose of this structure is to reduce the size of the message by inserting Offer Items which are applicable to multiple flight-related Offers defined above. + +NB. For the OfferID of the ALaCarteOffer: Default OfferID identifier for A La Carte Offer Items in a scenario where items here are not selected for a flight-related Offer above. + + + + + + + + One Service or Service Bundle which is priced per unit. A La Carte Offer Items are optional and variable quantities of these can be selected by any of the eligible passengers for the applicable segments and/or price classes. + + + + + + + + + + Calendar based Flight Price. + +Note: this contains lead-based flight prices for the requested travel date and requested lead calendar period. + +This capability supports multi-day calendar shopping, e.g. returning priced flight offers for a specified period before and/or after the actual requested date. + +The mandatory PriceCalendarDate contains the date associated with the price. If it is a lead calendar price, the @LeadPriceInd should be set to true. + + + + + + Price calendar date, example 2015-04-25. [Encoding Scheme] ISO 8601 Date Format (YYYY-MM-DD) + + + + + + + Association to one Origin/Destination instance. Example: od1 + + + + + + + + + The total price for all Travelers associated with this offer. + + + + + Passenger type code and travelers quantity. + +Example: ADT + +Encoding Scheme: IATA (three character) Passenger Type Code + + + + + + + Number of Traveler(s) for associated passenger type and country of residence. + +Example: 2 + + + + + + + + + + When true, this is a lead calendar shopping price for a date that is prior to or after the required travel date. + + + + + + + + + + + + + Payment information. + + + + + + Payment detail, including association(s). + + + + + + + + + + + + + + + Association to one or multiple Offer Items instance(s). Example:OI1 OI2 + + + + + + + Reference to the OfferID of the selected Offer (either a standard Offer or an a-la-carte Offer) returned in a previous shopping response. + + + + + Designator of Airline that owns/ assigned these IDs. Examples: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Code + + + + + Reference to unique shopping session response ID, as provided in the airline's previous shopping response. + + + + + + + + + + + + + + + + + + Promotion information. + + + + + + Promotion Code. + + + + + + + + + Data Lists(s). + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Enumeration: + +CarryOn +Checked + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + + + + + + Description Details + + + + + + + + + + + + List of Flight Segments + + + + + + + + + + List of Flight elements. + + + + + + Journey information describing the travel between an airport/city where travel commences and an airport/city where travel ultimately terminates. A journey may be comprised of one or more segments. Note: This node will be renamed to journey in future releases. + + + + + + Flight journey information. + + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + + + A globally unique identifier for this Flight instance. Example: flight1 + + + + + + + + + + List of Origin/Destination elements. + + + + + + + + + + + + + Price Class list. + + + + + + + + + + Description and characteristics of a Service + + + + + + + + + + + + + + Seat information by aircraft section. + + + + + + + + + + Description value. + + + + + + + + + + + + Mark-up Style. Example: HTML + + + + + + LINK to Description information source. + + + + + Description-associated Media Object(s). + + + + + + Description-associated MEDIA OBJECT ID or Key. Example: IMG1 + + + + + Description-associated MEDIA LINK. + + + + + Description-associated Media Attachment ID. Example: ATT1. + + + + + + + + + + + Images and/or links for the entire section defined by the range of rows. + + + + + + + + + + Refers to aircraft seat characteristics; seat option codes. Examples: E (EXIT ROW), M (Middle Seat), A (Aisle seat), L (Left side of aircraft), Q (Bulk Head). Refer to PADIS code list 9825. + + + + + Associated Keyword Unit of Measure, if relevant. Example: INCH + + + + + Lowest Width Measurement value for this section. Example: 20 + + + + + Lowest Pitch Measurement value for this section. Example: 32 + + + + + Seat Description Key-Value Word Pairs. +Examples: +ReclineDegree - 25 +BedLengthLowEnd - 68 +BedLengthHighEnd - 78 +WidthLowEnd - 20 +WidthHighEnd - 21.5 +PitchLowEnd - 32 +PitchHighEnd - 34.4 + + + + + + + Key-Value detail. + + + + + + + + + + + + + + + + + + Metadata List(s). + + + + + Message Policy information. + + + + + + + + + + + + + Air Shopping Response Metadata definition. + + + + + Shopping Query-Related Metadata. + + + + + + + + + + Passenger Metadata List(s). + + + + + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Transaction Processing Results, including processing status, alerts, business warnings, supplemental marketing messages and policy. + + + + + Response Message Processing. + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/AirlineProfileNotif.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/AirlineProfileNotif.xsd new file mode 100644 index 00000000..2addc070 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/AirlineProfileNotif.xsd @@ -0,0 +1,137 @@ + + + + + + + Airline Profile Sender pushes Airline Profile or link to Airline Profile Receivers that have been activated/authorized, including Profile version number. +The message also returns multi-media content at the message level with media content references at the individual service level. + + + + + + + + Core Query for requesting Airline Profiles. + + + + + + Identification of the Airline Profile Receiver : may be either an Aggregator Identity ID, a Travel Agency ID, or an Airline identity Code as defined in the Order Management Data Dictionary + + + + + Profile owner (Airline) + + + + + Airline Profile Data elements or Link + + + + + + Airline Profile Data elements or Link + + + + + + Link to Airline Profile Source File. Alows large AP file to be distributed over FTP, FTPS, ... as agreed bilaterally with Profile Owner + + + + + Actual Data Elements of the Profile + + + + + + Point of sale Geographic Specification information. + + + + + Point of sale Non Geographic Specification information. + + + + + Offer Geographic Specification + + + + + + + + + + Offered Service. Example: 1. Transportation 2. Baggage 3. Seats 4. Other + + + + + + + Specify whether the service is offered. Example: True + + + + + + + + + + Add, Delete, Or Change + + + + + Global sequence number of this record in the Airline profile. + + + + + + + + + + + + + Type of action. Examples: Create, Update, Delete. + + + + + + + + Action Type Context. + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/AirlineProfileRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/AirlineProfileRQ.xsd new file mode 100644 index 00000000..70a966ae --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/AirlineProfileRQ.xsd @@ -0,0 +1,65 @@ + + + + + + + Request from an Airline Profile Receiver to an Airline Profile Sender to send one or more Airlines’ Profiles. The Airline Profile (AP) aims at streamlining the volume of NDC shopping requests sent to airline systems by Aggregators or Seller systems. +The message also returns multi-media content at the message level with media content references at the individual service level. + + + + + + + + + Core Query for requesting Airline Profiles. + + + + + + Profile owner (Airline) + + + + + + + When True, only media link to profile location is requested and is expected to be returned. + + + + + + + + + This element indicates that all available profiles from all profile owners are requested. + + + + + + + When True, only media link to profile location is requested and is expected to be returned. + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/AirlineProfileRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/AirlineProfileRS.xsd new file mode 100644 index 00000000..13142abe --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/AirlineProfileRS.xsd @@ -0,0 +1,175 @@ + + + + + + + Response from an Airline Profile Sender to an Airline Profile Receiver to get one or more Airlines’ Profiles +The message also returns multi-media content at the message level with media content references at the individual service level. + + + + + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + + + + Query result. + + + + + + The number of decompressed records contained in this file. + + + + + + + + + + + + Profile owner (Airline). The standard industry alphanumeric code for the airline. + + + + + Airline Profile Data elements or Link + + + + + + Airline Profile Data elements or Link + + + + + + Link to Airline Profile Source File. Alows large AP file to be distributed over FTP, FTPS, ... as agreed bilaterally with Profile Owner + + + + + Actual Data Elements of the Profile + + + + + + Point of sale Geographic Specification information. + + + + + Point of sale Non Geographic Specification information. + + + + + Offer Geographic Specification + + + + + + + + + + Offered Service. Example: 1. Transportation 2. Baggage 3. Seats 4. Other + + + + + + + Specify whether the service is offered. Example: True + + + + + + + + + + Add, Delete, Or Change + + + + + Global sequence number of this record in the Airline profile. + + + + + + + + + + + + + + + + + + + List of supported messages and respective versions. + + + + + + Name of NDC Message. + + + + + Version of NDC Message. + + + + + + X-Path to supported elements and/or attributes with a specific message of a specific version. + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageAllowanceRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageAllowanceRQ.xsd new file mode 100644 index 00000000..142c017e --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageAllowanceRQ.xsd @@ -0,0 +1,382 @@ + + + + + + + + The BaggageAllowance transaction set provides checked and carry-on baggage allowance details. Request qualifiers may include Traveler, origin/ destination, point of sale, flight-specific and ticketed fare information. + +The response returns the baggage allowance, whether or not IATA Reso 302 or DOT rules are applicable, baggage weight, dimensions and size information by origin/ destination pair. Implementers may also obtain an additional catalog of applicable embargoes and charges within the same origin and destination pair. + + + + + + + + + Parameters that influence overall message results. + +Note: These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Ticket identification group, can be associated per Traveler. + + + + + Choice between entering: +1) Cached Shopping Offer IDs +2) Detailed Query Parameters + + + + + Core query parameters. + + + + + + Origin and Destination. + + + + + + + + + + Flight origin/ destination information. + + + + + + + + + + Globally unique Offer instance ID. It is not recommended to exceed 64, and it is not recommended to use dashes. Example: QWASZXERDFCVTYGHBNUIJKNMF67D5F9GHR567SWER41SD458F9456FMDIRTN34DF + + + + + + + + + Contains Shopping Preference choices, ie allowing to specify Airline, Alliance, Flight, Transfer and other shopping preferences. + + + + + + + + + + Contains information to identify how reservation was re-priced to obtain best published fare (Eg. best fare in same cabin, best fare in all cabins, other parameters to select best fare). + + + + + + + + + + + Qualifier choices. + +These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of the capability is not dictated by this specification. + + + + + + + + Contains card type, and Issuer Identification Number. + + + + + + + + + + Contains elements identifying eligibility for special pricing, which may be private or negotiated. + +Notes: +1. Supports pricing discounts and/ or other benefits for Travelers affiliated with companies with private fare and/ or negotiated rate contracts. + +2. Private Fares apply to ALL Travelers. + + + + + + + + + + Existing Flight Itinerary Information. + + + + + + Common NDC Data List choices. + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + + + Metadata List(s). + + + + + Message Policy information. + + + + + + + + + Baggage Allowance Request Parameters definition. + + + + + + + Group and subgroup code(s) that specify the requested categories of Optional Services to be returned in the results. + + + + + + + + Service group and subgroup code(s). + + + + + + + + + + Pricing Parameters, including Simple Pricing, Award Travel, Auto Exchange, Override Currency and Fee Exemption. + + + + + + Requested override currency code for pricing. +Example: EUR + + + + + Fee exemption application for Offer pricing. + + + + + + + + Exemption(s) based on tax codes plus (optional) tax types within a tax code. + + + + + + Exempt tax code. +Example: YQ/YR + + + + + + + Airport code location for exempt ZP or XF taxes. +Example: MIA + For maximum interoperability, it is recommended that IATA (three character) Airport/ City Code values be used. Use an IATA code or a proprietary string value. + +http://www.iata.org/publications/Pages/code-search.aspx + + + + + + + + + Tax type(s) within the tax code. Examples: I, C + + + + + + + + + + Exempt province(s). + + + + + Entity name. + =notes=: +1. This must be provided for certain exemptions in the Canadian market. + + + + + + + + + + + When true, this request is to be handled by an auto-exchange process . + + + + + When true, award eligible in addition to priced offers and fares is requested. + + + + + When true, only award eligible offers/ fares are requested. + + + + + When true, Simple Pricing for flight offers is requested. + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + Baggage Allowance Request Metadata definition. + + + + + Shopping Query-Related Metadata. + + + + + + + + + + Passenger Metadata List(s). + + + + + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageAllowanceRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageAllowanceRS.xsd new file mode 100644 index 00000000..b23e6fa3 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageAllowanceRS.xsd @@ -0,0 +1,317 @@ + + + + + + + + The BaggageAllowance transaction set provides checked and carry-on baggage allowance details. Request qualifiers may include Traveler, origin/ destination, point of sale, flight-specific and ticketed fare information. + +The response returns the baggage allowance, whether or not IATA Reso 302 or DOT rules are applicable, baggage weight, dimensions and size information by origin/ destination pair. Implementers may also obtain an additional catalog of applicable embargoes and charges within the same origin and destination pair. + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + + Search Result Parameters that influence overall message results. + +Note: These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + + Baggage Allowance by Origin/ Destination. + + + + + + + + + + Service(s). + + + + + + Service detail. + + + + + + + + + + + US Department of Transportation (DOT) Reservation or Disclosure Baggage Rule. + + + + + + + + + + + + + + Data Lists(s). + + + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + + + + + Metadata List(s). + + + + + + + + + + Message Policy information. + + + + + + + + + + + + + Baggage Allowance Response Parameters definition. + + + + + + + Pricing Parameters, including Simple Pricing, Award Travel, Auto Exchange, Override Currency and Fee Exemption. + + + + + + Requested override currency code for pricing. +Example: EUR + + + + + Fee exemption application for Offer pricing. + + + + + + + + Exemption(s) based on tax codes plus (optional) tax types within a tax code. + + + + + + Exempt tax code. +Example: YQ/YR + + + + + + + Airport code location for exempt ZP or XF taxes. +Example: MIA + For maximum interoperability, it is recommended that IATA (three character) Airport/ City Code values be used. Use an IATA code or a proprietary string value. + +http://www.iata.org/publications/Pages/code-search.aspx + + + + + + + + + Tax type(s) within the tax code. +Examples: I, C + + + + + + + + + + Exempt province(s). + + + + + Entity name. + =notes=: +1. This must be provided for certain exemptions in the Canadian market. + + + + + + + + + + + When true, fare information for one or more Offer Items has been returned from an auto-exchanging application. + + + + + When true, award eligible in addition to priced offers and fares is requested. + + + + + When true, only award eligible offers/ fares have been returned. + + + + + When true, Simple Pricing for flight offers has been applied. + + + + + + + + + + + Baggage Allowance Response Metadata definition. + + + + + Shopping Query-Related Metadata. + + + + + + + + + + Passenger Metadata List(s). + + + + + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageChargesRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageChargesRQ.xsd new file mode 100644 index 00000000..e73bd798 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageChargesRQ.xsd @@ -0,0 +1,328 @@ + + + + + + + + The BaggageCharges transaction set determines and returns the pricing for a set of checked bags. Request qualifiers include Traveler, origin/ destination, point of sale, flight-specific and ticketed fare information. + +The response returns the baggage charges, whether or not IATA Reso 302 or DOT rules are applicable, and detailed trip-level pricing for all requested passengers, or origin/ destination level pricing that includes checked and carry-on baggage charges + + + + + + + + + Parameters that influence overall message results. + +Note: These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Ticket identification group, can be associated per Traveler. + + + + + Choice between entering: +1) Cached Shopping Offer IDs +2) Detailed Query Parameters + + + + + Core query parameters. + + + + + + Origin and Destination. + + + + + + + + + + Flight origin/ destination information. + + + + + + + + + + Globally unique Offer instance ID. It is not recommended to exceed 64, and it is not recommended to use dashes. Example: QWASZXERDFCVTYGHBNUIJKNMF67D5F9GHR567SWER41SD458F9456FMDIRTN34DF + + + + + + + + + + + Existing Flight Itinerary Information. + + + + + + Common NDC Data List choices. + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + + + Metadata List(s). + + + + + Message Policy information. + + + + + + + + + Baggage Charges Request Parameters definition. + + + + + + + Group and subgroup code(s) that specify the requested categories of Optional Services to be returned in the results. + + + + + + + + Service group and subgroup code(s). + + + + + + + + + + Pricing Parameters, including Simple Pricing, Award Travel, Auto Exchange, Override Currency and Fee Exemption. + + + + + + Requested override currency code for pricing. +Example: EUR + + + + + Fee exemption application for Offer pricing. + + + + + + + + Exemption(s) based on tax codes plus (optional) tax types within a tax code. + + + + + + Exempt tax code. +Example: YQ/YR + + + + + + + Airport code location for exempt ZP or XF taxes. +Example: MIA + For maximum interoperability, it is recommended that IATA (three character) Airport/ City Code values be used. Use an IATA code or a proprietary string value. + +http://www.iata.org/publications/Pages/code-search.aspx + + + + + + + + + Tax type(s) within the tax code. Examples: I, C + + + + + + + + + + Exempt province(s). + + + + + Entity name. + =notes=: +1. This must be provided for certain exemptions in the Canadian market. + + + + + + + + + + + When true, this request is to be handled by an auto-exchange process. + + + + + When true, award eligible in addition to priced offers and fares is requested. + + + + + When true, only award eligible offers/ fares are requested. + + + + + When true, Simple Pricing for flight offers is requested. + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + Baggage Charges Request Metadata definition. + + + + + Shopping Query-Related Metadata. + + + + + + + + + + Passenger Metadata List(s). + + + + + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageChargesRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageChargesRS.xsd new file mode 100644 index 00000000..0ed4bc36 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageChargesRS.xsd @@ -0,0 +1,370 @@ + + + + + + + + The BaggageCharges transaction set determines and returns the pricing for a set of checked bags. Request qualifiers include Traveler, origin/ destination, point of sale, flight-specific and ticketed fare information. + +The response returns the baggage charges, whether or not IATA Reso 302 or DOT rules are applicable, and detailed trip-level pricing for all requested passengers, or origin/ destination level pricing that includes checked and carry-on baggage charges. + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + + Search Result Parameters that influence overall message results. + +Note: These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + + Baggage Charge Information. + + + + + + + Total price of baggage for the whole trip for all passengers. + + + + + + + When true, indicates the baggage is Pre paid + + + + + + + + + Baggage Allowance by Origin/ Destination. + + + + + + + + + + Service(s). + + + + + + Service detail. + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + Airline Name. Example: British Airways + + + + + + + + + + + US Department of Transportation (DOT) Reservation or Disclosure Baggage Rule. + + + + + + + + + + + + + + + + + Data Lists(s). + + + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + + + + + Metadata List(s). + + + + + Message Policy information. + + + + + + + + + + + + + Baggage Charges Response Parameters definition. + + + + + + + Group and subgroup code(s) that specify the requested categories of Optional Services to be returned in the results. + + + + + + + + Service group and subgroup code(s). + + + + + + + + + + Pricing Parameters, including Simple Pricing, Award Travel, Auto Exchange, Override Currency and Fee Exemption. + + + + + + Requested override currency code for pricing. +Example: EUR + + + + + Fee exemption application for Offer pricing. + + + + + + + + Exemption(s) based on tax codes plus (optional) tax types within a tax code. + + + + + + Exempt tax code. +Example: YQ/YR + + + + + + + Airport code location for exempt ZP or XF taxes. +Example: MIA + For maximum interoperability, it is recommended that IATA (three character) Airport/ City Code values be used. Use an IATA code or a proprietary string value. + +http://www.iata.org/publications/Pages/code-search.aspx + + + + + + + + + Tax type(s) within the tax code. Examples: I, C + + + + + + + + + + Exempt province(s). + + + + + Entity name. + =notes=: +1. This must be provided for certain exemptions in the Canadian market. + + + + + + + + + + + When true, this request is to be handled by an auto-exchange process. + + + + + When true, award eligible in addition to priced offers and fares is requested. + + + + + When true, only award eligible offers/ fares are requested. + + + + + When true, Simple Pricing for flight offers is requested. + + + + + + + + + + + Baggage Charges Response Metadata definition. + + + + + Shopping Query-Related Metadata. + + + + + + + + + + Passenger Metadata List(s). + + + + + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageListRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageListRQ.xsd new file mode 100644 index 00000000..0be53451 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageListRQ.xsd @@ -0,0 +1,312 @@ + + + + + + + + The BaggageList transaction set determines and returns a list of applicable bags for a specified itinerary or carrier. + +Request qualifiers may include Traveler, origin/ destination, flight-specific and ticketed fare information. + + + + + + + + + Parameters that influence overall message results. + +Note: These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Choice between entering: +1) Cached Shopping Offer IDs +2) Detailed Query Parameters + + + + + Core query parameters. + + + + + + Origin and Destination. + + + + + + + + + + Flight origin/ destination information. + + + + + + + + + + + + + + + + Existing Flight Itinerary Information. + + + + + + Common NDC Data List choices. + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + + + Metadata List(s). + + + + + Message Policy information. + + + + + + + + + Baggage List Request Parameters definition. + + + + + + + Group and subgroup code(s) that specify the requested categories of Optional Services to be returned in the results. + + + + + + + + Service group and subgroup code(s). + + + + + + + + + + Pricing Parameters, including Simple Pricing, Award Travel, Auto Exchange, Override Currency and Fee Exemption. + + + + + + Requested override currency code for pricing. +Example: EUR + + + + + Fee exemption application for Offer pricing. + + + + + + + + Exemption(s) based on tax codes plus (optional) tax types within a tax code. + + + + + + Exempt tax code. +Example: YQ/YR + + + + + + + Airport code location for exempt ZP or XF taxes. +Example: MIA + For maximum interoperability, it is recommended that IATA (three character) Airport/ City Code values be used. Use an IATA code or a proprietary string value. + +http://www.iata.org/publications/Pages/code-search.aspx + + + + + + + + + Tax type(s) within the tax code. Examples: I, C + + + + + + + + + + Exempt province(s). + + + + + Entity name. + =notes=: +1. This must be provided for certain exemptions in the Canadian market. + + + + + + + + + + + When true, this request is to be handled by an auto-exchange process. + + + + + When true, award eligible in addition to priced offers and fares is requested. + + + + + When true, only award eligible offers/ fares are requested. + + + + + When true, Simple Pricing for flight offers is requested. + + + + + + + + + + + Baggage List Request Metadata definition. + + + + + Shopping Query-Related Metadata. + + + + + + + + + + Passenger Metadata List(s). + + + + + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageListRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageListRS.xsd new file mode 100644 index 00000000..0d781b3a --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/BaggageListRS.xsd @@ -0,0 +1,284 @@ + + + + + + + + The BaggageList transaction set determines and returns a list of applicable bags for a specified itinerary or carrier. + +Request qualifiers may include Traveler, origin/ destination, flight-specific and ticketed fare information. + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + + Search Result Parameters that influence overall message results. + +Note: These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + + Service(s). + + + + + + Service detail. + + + + + + + + Data Lists(s). + + + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + + + + + Metadata List(s). + + + + + Message Policy information. + + + + + + + + + + + + + Baggage List Response Parameters definition. + + + + + + + Pricing Parameters, including Simple Pricing, Award Travel, Auto Exchange, Override Currency and Fee Exemption. + + + + + + Requested override currency code for pricing. +Example: EUR + + + + + Fee exemption application for Offer pricing. + + + + + + + + Exemption(s) based on tax codes plus (optional) tax types within a tax code. + + + + + + Exempt tax code. +Example: YQ/YR + + + + + + + Airport code location for exempt ZP or XF taxes. +Example: MIA + For maximum interoperability, it is recommended that IATA (three character) Airport/ City Code values be used. Use an IATA code or a proprietary string value. + +http://www.iata.org/publications/Pages/code-search.aspx + + + + + + + + + Tax type(s) within the tax code. +Examples: I, C + + + + + + + + + + Exempt province(s). + + + + + Entity name. + =notes=: +1. This must be provided for certain exemptions in the Canadian market. + + + + + + + + + + + When true, fare information for one or more Offer Items has been returned from an auto-exchanging application. + + + + + When true, award eligible in addition to priced offers and fares is requested. + + + + + When true, only award eligible offers/ fares have been returned. + + + + + When true, Simple Pricing for flight offers has been applied. + + + + + + + + + + + Baggage List Response Metadata definition. + + + + + Shopping Query-Related Metadata. + + + + + + + + + + Passenger Metadata List(s). + + + + + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/CustomerInputRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/CustomerInputRQ.xsd new file mode 100644 index 00000000..77bcba3a --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/CustomerInputRQ.xsd @@ -0,0 +1,149 @@ + + + + + + + The CustomerInput transaction set supports other EDIST transactions by providing discrete-but related-functional capabilities for customer authentication and 3D Secure Payment Authentication. Supported functionality includes: + +PIN Phrasing Scheme Membership: Predefined structures and keyword-value pairs are provided for 1.5FA (Factor Authentication) Traveler authentication. + +3-D Secure Payment Protocol: 3DS is designed to reduce fraud and chargebacks during e-commerce Internet transactions. Cardholders are asked to identify themselves at the point of sale before the purchase can be completed. This usually means entering a PIN or other password after entering their card details. + + + + + + + + + Customer Input query parameters. + + + + + + + Passenger Pin Phrase Authentication. + + + + + 3D Secure Payment Program Enrollment, Verification and Authentication information. + + + + + + 3D Secure Payment detail. + + + + + + + + Payment Amount. Example: 300 USD + + + + + Payment Card information. + + + + + Payment Approval/ Authorization information. + +Note: This includes pre-authorized transaction and authorization status. + + + + + + Approval Code Method. Example: M (Manual) + +Note: This is used to specify how the approval code for a credit card sale was obtained. + +Encoding Scheme: IATA PADIS Code List for data element 9890. + + + + + The approval code returned as part of an authorization process. + + + + + Transaction Timestamp. Example: 2015-01-13T13:59:38Z + + + + + The approval code returned as part of an authorization process. + + + + + + + + + + + + When true, this transaction has been pre-authorized. + + + + + + + Used to specify if this is the old, new, or orginal form of payment. + +Encoding Scheme: IATA PADIS code list 9988 + + + + + + + + + + + + + + + + + + + + + Customer Input Request Message Parameters. + + + + + + Message Policy information. + + + + + + + Parameters that influence overall message results. + +Note: These capabilities may not be supported by all EDIST-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/CustomerInputRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/CustomerInputRS.xsd new file mode 100644 index 00000000..a3a4e683 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/CustomerInputRS.xsd @@ -0,0 +1,142 @@ + + + + + + + The CustomerInput transaction set supports other EDIST transactions by providing discrete-but related-functional capabilities for customer authentication and 3D Secure Payment Authentication. Supported functionality includes: + +PIN Phrasing Scheme Membership: Predefined structures and keyword-value pairs are provided for 1.5FA (Factor Authentication) Traveler authentication. + +3-D Secure Payment Protocol: 3DS is designed to reduce fraud and chargebacks during e-commerce Internet transactions. Cardholders are asked to identify themselves at the point of sale before the purchase can be completed. This usually means entering a PIN or other password after entering their card details. + + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + Query Results. + + + + + + + Passenger Pin Phrase Authentication. + + + + + 3D Secure Payment Program Enrollment, Verification and Authentication information. + + + + + + 3D Secure Payment detail. + + + + + + + + Traveler Authentication process status. +Examples: +Y- Customer authenticated +N- Customer not authenticated +A- An authentication attempt occurred but could not be completed +U- Unable to perform authentication + + + + + + + Authentication Status Context. + + + + + + + + + + + + + + + + + + + + + + + + + + + Customer Input Response Message Processing. + + + + + + + + + Message Policy information. + + + + + + When true, processing alerts have been generated and the Alerts node should be parsed. + + + + + When true, supplemental marketing information has been generated and the Notifications/ MarketingMessage node should be parsed. + + + + + When true, business warnings have been generated and the Notification/Warning node should be parsed. + + + + + When true, notices have been generated and the Notifications/Notice node should be parsed. + + + + + + + + Transaction Processing Results, including processing status, payload content notifices, , business warnings and supplemental marketing messages. + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/FareRulesRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/FareRulesRQ.xsd new file mode 100644 index 00000000..804502dc --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/FareRulesRQ.xsd @@ -0,0 +1,138 @@ + + + + + + + The FareRules transaction set returns the filed details of a specific fare basis code (FBC). + + + + + + + + + Parameters that influence overall message results. + +Note: These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Core Fare Rules query parameters. + + + + + + + + + + + + Special fares, which may be private or negotiated fares. + + + + + + Fare Rule Category(s). + + + + + + + + + + + + + + + Metadata List(s). + + + + + + + + + + Message Policy information. + + + + + + + + + A data type Fare Rules Request Message Parameters. + + + + + + + + Fare Rules Request Metadata definition. + + + + + Shopping Query-Related Metadata. + + + + + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/FareRulesRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/FareRulesRS.xsd new file mode 100644 index 00000000..64a45f30 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/FareRulesRS.xsd @@ -0,0 +1,135 @@ + + + + + + + The FareRules transaction set returns the filed details of a specific fare basis code (FBC). + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + + + Fare Rules. + + + + + + + + + + + Fare Rule Category and Description. + + + + + + + Fare Rule Text. + + + + + + + + + + + Metadata List(s). + + + + + + + + + + Message Policy information. + + + + + + + + + + + + + Fare Rules Response Metadata definition. + + + + + Shopping Query-Related Metadata. + + + + + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/FileRetrieveRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/FileRetrieveRQ.xsd new file mode 100644 index 00000000..e2f76e66 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/FileRetrieveRQ.xsd @@ -0,0 +1,72 @@ + + + + + + + The FileRetrieveRQ/ FileListRS transaction set supplements other NDC shopping messages with payloads designed to efficiently exchange offer-associated media using IDs and URLs. + +Using the FileRetrieveRQ message, implementers can subsequently retrieve binary encoded files—such as images or PDFs—from the IDs or URLs in a shopping response message that are returned in the FileListRS message. + +This message pair also supports scenarios where trading partners maintain a physical cache of offer associated media from other trading partners based on media IDs and/or URLs. + + + + + + + + Core query parameters. + + + + + + Image(s) to Retrieve. + + + + + + + + + + Attachment(s) to Retrieve. + + + + + + Media attachment Uniform Resource Identifier (URI). + + + + + + + + + + + + + + + + + + + Message Policy information. + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/FileRetrieveRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/FileRetrieveRS.xsd new file mode 100644 index 00000000..5d263def --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/FileRetrieveRS.xsd @@ -0,0 +1,72 @@ + + + + + + + The FileRetrieveRQ/ FileListRS transaction set supplements other NDC shopping messages with payloads designed to efficiently exchange offer-associated media using IDs and URLs. + +Using the FileRetrieveRQ message, implementers can subsequently retrieve binary encoded files—such as images or PDFs—from the IDs or URLs in a shopping response message that are returned in the FileListRS message. + +This message pair also supports scenarios where trading partners maintain a physical cache of offer associated media from other trading partners based on media IDs and/or URLs. + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + Transaction Processing Results, including processing status, alerts, business warnings, supplemental marketing messages and policy. + + + + + Media, File Attachements and Binary Encoded Image(s). + + + + + + Media File Detail. + + + + + + + + + + + + + + Message Policy information. + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/InvGuaranteeRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/InvGuaranteeRQ.xsd new file mode 100644 index 00000000..dd10ac09 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/InvGuaranteeRQ.xsd @@ -0,0 +1,222 @@ + + + + + + + + The InventoryGuarantee transaction set requests that inventory is guaranteed for specified Offers, pending their conversion into a completed Order. + +The response returns an indication if the inventory has been guaranteed, and if so, the associated inventory guarantee time limit and a unique inventory guarantee reference ID. + + + + + + + + Inventory Guarantee Query. + + + + + + Existing Booking Reference (e.g. PNR Record Locator). Example: R1A3SK + + + + + + Order ID. Example: ORDER7333 + + + + + Order Item ID(s). Example: ORD7333-001 + + + + + Offer ID . Example offer 1234 + + + + + Offer Item ID(s). Example: OFFER1226 + + + + + Qualifiers to influence inventory guarantee request processing. + +Note: These capabilities may not be supported by all EDIST-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of the capability is not dictated by this specification. + + + + + + PAYMENT CARD Qualifier(s). + + + + + + Payment Card. + + + + + + + + PROGRAM Qualifier(s). + + + + + + Program Qualifier detail. + + + + + + + + PROMOTION Qualifier(s). + + + + + + Promotion(s) Information. + + + + + + + + SEAT Qualifier(s). + + + + + + Seat assignment information. + + + + + + + + Social Media Account Qualifier. + + + + + SPECIAL NEED Qualifier(s). + + + + + + Passenger Special Needs Attributes. + + + + + + + + TRIP PURPOSE Qualifier. + + + + + Trip Flight Location information. + +Note: This information may be used for airport associated products, such as an annual lounge pass. + + + + + + + + Airport or City Location code. Example: TPA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + + + + + + + + + + + + + + + Data Lists(s). + + + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/InvGuaranteeRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/InvGuaranteeRS.xsd new file mode 100644 index 00000000..c2938f02 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/InvGuaranteeRS.xsd @@ -0,0 +1,234 @@ + + + + + + + + The InventoryGuarantee transaction set requests that inventory is guaranteed for specified Offers, pending their conversion into a completed Order. + +The response returns an indication if the inventory has been guaranteed, and if so, the associated inventory guarantee time limit and a unique inventory guarantee reference ID. + + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + Query Results. + + + + + + Transaction Processing Results, including processing status, business warnings, supplemental marketing messages and/ or additional information required to complete a transaction. + + + + + Guaranteed Inventory information. + + + + + + Guaranteed Inventory Item detail. + + + + + + Unique Inventory Guarantee ID. Examples: INVREF123456, 68E0-675C + +Note: This is a unique identifier issued by an Airline to reference that inventory for a specified offer will be guaranteed as available for a period. + + + + + + Guaranteed Inventory associations. + + + + + + Associated Service ID(s). Example: SRVC0001 + + + + + Associated Offer Item ID(s). +Example: OFFER1226 + + + + + Associated Order ID +Example: ORDER7333 + + + + + Associated Order Item ID(s). +Example: ORD7333-001 + + + + + Other Named Association(s). + +Note: Includes an association type choice (e.g. MediaGroup) and an instance association value (e.g. mediagrp1). + + + + + Named Instance Association Type. Examples: CarryOnAllowance, MediaGroup + + + + + Associated object instance value. +Example: mediagrp1 + + + + + + + + + + + + + + + + + + + + + + + When true, the inventory is waitlisted. + + + + + + + + + + + When true, no inventory could be guaranteed. + + + + + + + Data Lists(s). + + + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + + + + + Metadata List(s). + + + + + + + + + + + + + + + + + Response Message Processing. + + + + + + + + Message Policy information. + + + + + + When true, business warnings have been generated and the Notification/Warning node should be parsed. + + + + + + + + Transaction Processing Results, including processing status, payload content notifices, , business warnings and supplemental marketing messages. + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/InvReleaseNotif.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/InvReleaseNotif.xsd new file mode 100644 index 00000000..6d70caf9 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/InvReleaseNotif.xsd @@ -0,0 +1,110 @@ + + + + + + + The InventoryRelease transaction sends an unsolicited notification to release guaranteed inventory. + +The Acknowledgement message may be returned to acknowledge receipt of the notification request. + + + + + + + + Inventory Release Notification. + + + + + + Previously guaranteed inventory to release. + + + + + + Unique Inventory Guarantee ID. Examples: INVREF123456, 68E0-675C + +Note: This is a unique identifier issued by an Airline to reference that inventory for a specified offer will be guaranteed as available for a period. + + + + + + Guaranteed Inventory detail. + + + + + + Associated Service ID(s). Example: SRVC0001 + + + + + Associated Offer Item ID(s). +Example: OFFER1226 + + + + + Associated Order ID +Example: ORDER7333 + + + + + Associated Order Item ID(s). +Example: ORD7333-001 + + + + + Other Named Association(s). + +Note: Includes an association type choice (e.g. MediaGroup) and an instance association value (e.g. mediagrp1). + + + + + Named Instance Association Type. Examples: CarryOnAllowance, MediaGroup + + + + + Associated object instance value. +Example: mediagrp1 + + + + + + + + + + + When true, the inventory was waitlisted. + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OfferPriceRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OfferPriceRQ.xsd new file mode 100644 index 00000000..a36341fe --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OfferPriceRQ.xsd @@ -0,0 +1,570 @@ + + + + + + + + The OfferPrice transaction set may return two different sets of content. The response will initially provide the priced Offer reflecting the Offers/OfferItems requested for pricing, and potentially additional a-la-carte ancillary services that are applicable and available for the offer provided. + + + + + + + + + Parameters that influence overall message results. + +Note: These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Core Flight Pricing query parameters. + + + + + + + Existing Flight Itinerary Information. + + + + + Auto Exchange information. + + + + + Data Lists(s). + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Enumeration: + +CarryOn +Checked + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + + + + + + Description Details + + + + + + + + + + + + List of Flight Segments + + + + + + + + + + List of Flight elements. + + + + + + Journey information describing the travel between an airport/city where travel commences and an airport/city where travel ultimately terminates. A journey may be comprised of one or more segments. Note: This node will be renamed to journey in future releases. + + + + + + Flight journey information. + + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + + + A globally unique identifier for this Flight instance. Example: flight1 + + + + + + + + + + List of Origin/Destination elements. + + + + + + + + + + + + + Price Class list. + + + + + + + + + + Description and characteristics of a Service + + + + + + + + + + + + + + Seat information by aircraft section. + + + + + + + + + + Description value. + + + + + + + + + + + + Mark-up Style. Example: HTML + + + + + + LINK to Description information source. + + + + + Description-associated Media Object(s). + + + + + + Description-associated MEDIA OBJECT ID or Key. Example: IMG1 + + + + + Description-associated MEDIA LINK. + + + + + Description-associated Media Attachment ID. Example: ATT1. + + + + + + + + + + + Images and/or links for the entire section defined by the range of rows. + + + + + + + + + + Refers to aircraft seat characteristics; seat option codes. Examples: E (EXIT ROW), M (Middle Seat), A (Aisle seat), L (Left side of aircraft), Q (Bulk Head). Refer to PADIS code list 9825. + + + + + Associated Keyword Unit of Measure, if relevant. Example: INCH + + + + + Lowest Width Measurement value for this section. Example: 20 + + + + + Lowest Pitch Measurement value for this section. Example: 32 + + + + + Seat Description Key-Value Word Pairs. +Examples: +ReclineDegree - 25 +BedLengthLowEnd - 68 +BedLengthHighEnd - 78 +WidthLowEnd - 20 +WidthHighEnd - 21.5 +PitchLowEnd - 32 +PitchHighEnd - 34.4 + + + + + + + Key-Value detail. + + + + + + + + + + + + + + + + + + Metadata List(s). + + + + + + + + + + Message Policy information. + + + + + + + + + A data type for Flight Price Request Message Parameters. + +Notes: Derived from MessageParamsBaseType. + + + + + + + Group and subgroup code(s) that specify the requested categories of Optional Services to be returned in the results. + + + + + + + + Service group and subgroup code(s). + + + + + + + + + + Pricing Parameters, including Simple Pricing, Award Travel, Auto Exchange, Override Currency and Fee Exemption. + + + + + + Requested override currency code for pricing. +Example: EUR + + + + + Fee exemption application for Offer pricing. + + + + + + + + Exemption(s) based on tax codes plus (optional) tax types within a tax code. + + + + + + Exempt tax code. +Example: YQ/YR + + + + + + + Airport code location for exempt ZP or XF taxes. +Example: MIA + For maximum interoperability, it is recommended that IATA (three character) Airport/ City Code values be used. Use an IATA code or a proprietary string value. + +http://www.iata.org/publications/Pages/code-search.aspx + + + + + + + + + Tax type(s) within the tax code. Examples: I, C + + + + + + + + + + Exempt province(s). + + + + + Entity name. + =notes=: +1. This must be provided for certain exemptions in the Canadian market. + + + + + + + + + + + When true, this request is to be handled by an auto-exchange process. + + + + + When true, award eligible in addition to priced offers and fares is requested. + + + + + When true, only award eligible offers/ fares are requested. + + + + + When true, Simple Pricing for flight offers is requested. + + + + + + + + + + + Flight Price Request Metadata definition. + + + + + Shopping Query-Related Metadata. + + + + + + + + + + Passenger Metadata List(s). + + + + + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OfferPriceRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OfferPriceRS.xsd new file mode 100644 index 00000000..7ea6d686 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OfferPriceRS.xsd @@ -0,0 +1,772 @@ + + + + + + + + The OfferPrice transaction set may return two different sets of content. The response will initially provide the priced Offer reflecting the Offers/OfferItems requested for pricing, and potentially additional Offers that are applicable and relevant to the PricedOffer provided. + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + + Search Result Parameters that influence overall message results. + +Note: These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + + Offer containing all the Offers/OfferItems requested for pricing in previous request. + + + + + + + + Summary of proposed flight information in the context of this specific Offer. + + + + + + + + + + + Flight-level price class + + + + + + + + + Itinerary-level price class (eg. most restrictive applies) + + + + + + + + A set of one or more Service s. The Offer Item assigns a total price for all included services for all passengers and all segments referenced. Once constructed, the OfferItem cannot be modifed. + + + + + This block contains references to the Baggage Allowance characteristics (no. of pieces / weight / dimensions, etc) included in the Flight services for one or more Passengers. + + + + + + Reference to FlightIDs in DataLists + + + + + Reference to PassengerIDs in DataLists + + + + + Reference to BaggageAllowanceIDs in DataLists + + + + + + + + + + + + + Additional optional Offers + + + + + + + + + + + Summary of proposed flight information in the context of this specific Offer. + + + + + + + + + + + Flight-level price class + + + + + + + + + Itinerary-level price class (eg. most restrictive applies) + + + + + + + + A set of one or more Service s. The Offer Item assigns a total price for all included services for all passengers and all segments referenced. Once constructed, the OfferItem cannot be modifed. + + + + + + + + + + Container for standalone optional OfferItems. This supports the shopping basket concept. The main purpose of this structure is to reduce the size of the message by inserting Offer Items which are applicable to multiple flight-related Offers defined above. + +NB. For the OfferID of the ALaCarteOffer: Default OfferID identifier for A La Carte Offer Items in a scenario where items here are not selected for a flight-related Offer above. + + + + + + + + One Service or Service Bundle which is priced per unit. A La Carte Offer Items are optional and variable quantities of these can be selected by any of the eligible passengers for the applicable segments and/or price classes. + + + + + + + + + + + + + Payment information. + + + + + + Payment detail, including association(s). + + + + + + + + + + + + + + + Association to one or multiple Offer Items instance(s). Example:OI1 OI2 + + + + + + + Reference to the OfferID of the selected Offer (either a standard Offer or an a-la-carte Offer) returned in a previous shopping response. + + + + + Designator of Airline that owns/ assigned these IDs. Examples: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Code + + + + + Reference to unique shopping session response ID, as provided in the airline's previous shopping response. + + + + + + + + + + + + + + + + + + Promotion information. + + + + + + Promotion Code. + + + + + + + + + Data Lists(s). + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Enumeration: + +CarryOn +Checked + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + + + + + + Description Details + + + + + + + + + + + + List of Flight Segments + + + + + + + + + + List of Flight elements. + + + + + + Journey information describing the travel between an airport/city where travel commences and an airport/city where travel ultimately terminates. A journey may be comprised of one or more segments. Note: This node will be renamed to journey in future releases. + + + + + + Flight journey information. + + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + + + A globally unique identifier for this Flight instance. Example: flight1 + + + + + + + + + + List of Origin/Destination elements. + + + + + + + + + + + + + Price Class list. + + + + + + + + + + Description and characteristics of a Service + + + + + + + + + + + + + + Seat information by aircraft section. + + + + + + + + + + Description value. + + + + + + + + + + + + Mark-up Style. Example: HTML + + + + + + LINK to Description information source. + + + + + Description-associated Media Object(s). + + + + + + Description-associated MEDIA OBJECT ID or Key. Example: IMG1 + + + + + Description-associated MEDIA LINK. + + + + + Description-associated Media Attachment ID. Example: ATT1. + + + + + + + + + + + Images and/or links for the entire section defined by the range of rows. + + + + + + + + + + Refers to aircraft seat characteristics; seat option codes. Examples: E (EXIT ROW), M (Middle Seat), A (Aisle seat), L (Left side of aircraft), Q (Bulk Head). Refer to PADIS code list 9825. + + + + + Associated Keyword Unit of Measure, if relevant. Example: INCH + + + + + Lowest Width Measurement value for this section. Example: 20 + + + + + Lowest Pitch Measurement value for this section. Example: 32 + + + + + Seat Description Key-Value Word Pairs. +Examples: +ReclineDegree - 25 +BedLengthLowEnd - 68 +BedLengthHighEnd - 78 +WidthLowEnd - 20 +WidthHighEnd - 21.5 +PitchLowEnd - 32 +PitchHighEnd - 34.4 + + + + + + + Key-Value detail. + + + + + + + + + + + + + + + + + + Metadata List(s). + + + + + + + + + + Message Policy information. + + + + + + + + + + + + + A data type for Flight Price Response Message Parameters. + + + + + + + Pricing Parameters, including Simple Pricing, Award Travel, Auto Exchange, Override Currency and Fee Exemption. + + + + + + Requested override currency code for pricing. +Example: EUR + + + + + Fee exemption application for Offer pricing. + + + + + + + + Exemption(s) based on tax codes plus (optional) tax types within a tax code. + + + + + + Exempt tax code. +Example: YQ/YR + + + + + + + Airport code location for exempt ZP or XF taxes. +Example: MIA + For maximum interoperability, it is recommended that IATA (three character) Airport/ City Code values be used. Use an IATA code or a proprietary string value. + +http://www.iata.org/publications/Pages/code-search.aspx + + + + + + + + + Tax type(s) within the tax code. +Examples: I, C + + + + + + + + + + Exempt province(s). + + + + + Entity name. + =notes=: +1. This must be provided for certain exemptions in the Canadian market. + + + + + + + + + + + When true, fare information for one or more Offer Items has been returned from an auto-exchanging application. + + + + + When true, award eligible in addition to priced offers and fares is requested. + + + + + When true, only award eligible offers/ fares have been returned. + + + + + When true, Simple Pricing for flight offers has been applied. + + + + + + + + + + + + + Flight Price Response Metadata definition. + + + + + Shopping Query-Related Metadata. + + + + + + + + + + Traveler Metadata List(s). + + + + + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OrderCancelRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderCancelRQ.xsd new file mode 100644 index 00000000..79f10329 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderCancelRQ.xsd @@ -0,0 +1,126 @@ + + + + + + + The OrderCancel transaction set requests the cancellation of a specified order, and returns confirmation of cancellation. + + + + + + + + + + + + Reason for cancellation. + +Encoding Scheme: IATA Padis Codeset REA + + + + + + + + Information relating to prepayment vouchers. + + + + + + + + Check (Cheque) Payment + + + + + If true, preference is to apply refund to carrier credit. + + + + + + When true, it is requested that the refund be applied to the original FOP + + + + + + + + + + Refund amount expected from requestor. + + + + + Order Cancel Query. + + + + + + + + The airline-assigned unique Order ID. Example: ORDER-c98c-4759-a20b + + + + + Airline Designator of airline that owns/ assigned this ID. Example: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Codes + + + + + The POA OrderID should only go to the ORA, not back to the seller. +1. ORA +2. POA + + + + + + + + + + + Deep linking into another site to complete the transaction. + + + + + Object Metadata Association(s). Example: meta1 meta3 + + + + + + + Existing Booking Reference (e.g. PNR Record Locator). Example: R1A3SK + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OrderCancelRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderCancelRS.xsd new file mode 100644 index 00000000..dbba2844 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderCancelRS.xsd @@ -0,0 +1,246 @@ + + + + + + + + The OrderCancel transaction set requests the cancellation of a specified order, and returns confirmation of cancellation. + + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + Query Results. + + + + + + Transaction Processing Results, including processing status, alerts, notices, business warnings, supplemental marketing messages and policy. + + + + + Cancelled order reference. Example: REF12345 + + + + + Order Change Fees(s) and Penalty(s). + + + + + + + + + + Ticket/ document information. + + + + + + Ticket/document detail. + + + + + + Booking and Servicing Agent information. + + + + + + + + + + + + Payment information. + + + + + + Payment detail. + + + + + + + + Origin and Destination Airport/ City. + + + + + + The origin city code. + + + + + The destination city code. + + + + + + + + Endorsement/ Restriction text. + + + + + + + + + + Additional Reference information. + + + + + + + + + + Fare Information + + + + + + + + + Fare Tax information. + + + + + + + + + + + + + + + + Associated Order ID(s) information. + + + + + Commission information. + + + + + + + + + + + + + + + + + + Common NDC Data List choices. + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + + + + + + + + + + Transaction Processing Results, including processing status, alerts, business warnings, supplemental marketing messages and policy. + + + + + Response Message Processing. + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OrderChangeNotif.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderChangeNotif.xsd new file mode 100644 index 00000000..8cb5b37d --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderChangeNotif.xsd @@ -0,0 +1,579 @@ + + + + + + + + The OrderChangeNotif transaction sends an unsolicited order change notification message. The Acknowledgement message may be returned to acknowledge receipt of the notification request. + + + + + + + + Order Change Notification. + + + + + + Group Information. + + + + + Order information. + + + + + + + + Order Item Detail. + + + + + + + + + + + + + + + Ticket/ Document Information. + + + + + + Ticket/document information. + + + + + + Booking and Servicing Agent information. + + + + + + + + + + + + + + + + Document Action Preference - POA to ORA. + +Encoding Scheme: IATA Padis Codeset - List for data element 1225 + + + + + + + + + + Commission information. + + + + + Order Amendment information. + + + + + + Amendment Detail. + + + + + + Amendment Action Type. Examples: Cancel, Create, Divide, Delete, Reissue, Reprice, Update. + + + + + + + The reason for the action. + +Encoding Scheme: IATA PADIS Code List for data element REA. + + + + + + + + + + Offer Item ID with optional Service ID(s). + + + + + + + + + Passenger(s)/ Group associated with the Offer Item. + +Note: This contains references to Passenger and Group instance(s) defined in the Passengers node. + + + + + + Association to multiple Passenger instance(s). Example: pax1 pax2 + + + + + + + + + Associated Optional Service(s). + + + + + + + Passenger(s)/ Group associated with the Offer Item. + +Note: This contains references to Passenger and Group instance(s) defined in the Passengers node. + + + + + + Association to multiple Passenger instance(s). Example: pax1 pax2 + + + + + + + + + + + + Other Named Association(s). + +Note: Includes an association type choice (e.g. MediaGroup) and an instance association value (e.g. mediagrp1). + + + + + Named Instance Association Type. Examples: CarryOnAllowance, MediaGroup + + + + + Associated object instance value. +Example: mediagrp1 + + + + + + + + + + + + Ticket/document information. + + + + + + Booking and Servicing Agent information. + + + + + + + + + + + + + + Passenger(s)/ Group associated with the Offer Item. + +Note: This contains references to Passenger and Group instance(s) defined in the Passengers node. + + + + + + Association to multiple Passenger instance(s). Example: pax1 pax2 + + + + + + + + + + + + + + + + + + + + + Data Lists(s). + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Enumeration: + +CarryOn +Checked + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + + + + + + Description Details + + + + + + + + + + + + List of Flight Segments + + + + + + + + + + List of Flight elements. + + + + + + Journey information describing the travel between an airport/city where travel commences and an airport/city where travel ultimately terminates. A journey may be comprised of one or more segments. Note: This node will be renamed to journey in future releases. + + + + + + Flight journey information. + + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + + + A globally unique identifier for this Flight instance. Example: flight1 + + + + + + + + + + List of Origin/Destination elements. + + + + + + + + + + + + + Price Class list. + + + + + + + + + + Description and characteristics of a Service + + + + + + + + + + + + + + Seat information by aircraft section. + + + + + + + + + + Description value. + + + + + + + + + + + + Mark-up Style. Example: HTML + + + + + + LINK to Description information source. + + + + + Description-associated Media Object(s). + + + + + + Description-associated MEDIA OBJECT ID or Key. Example: IMG1 + + + + + Description-associated MEDIA LINK. + + + + + Description-associated Media Attachment ID. Example: ATT1. + + + + + + + + + + + Images and/or links for the entire section defined by the range of rows. + + + + + + + + + + Refers to aircraft seat characteristics; seat option codes. Examples: E (EXIT ROW), M (Middle Seat), A (Aisle seat), L (Left side of aircraft), Q (Bulk Head). Refer to PADIS code list 9825. + + + + + Associated Keyword Unit of Measure, if relevant. Example: INCH + + + + + Lowest Width Measurement value for this section. Example: 20 + + + + + Lowest Pitch Measurement value for this section. Example: 32 + + + + + Seat Description Key-Value Word Pairs. +Examples: +ReclineDegree - 25 +BedLengthLowEnd - 68 +BedLengthHighEnd - 78 +WidthLowEnd - 20 +WidthHighEnd - 21.5 +PitchLowEnd - 32 +PitchHighEnd - 34.4 + + + + + + + Key-Value detail. + + + + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OrderChangeRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderChangeRQ.xsd new file mode 100644 index 00000000..43fd5b00 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderChangeRQ.xsd @@ -0,0 +1,854 @@ + + + + + + + + The OrderChange/ OrderView transaction set requests modifications to an Order by specifying which order items to change and what to change them to. The updated view of the Order is returned. + + + + + + + + + + Order Change Query. + + + + + + Group and Action. + + + + + + + + Order Action. Examples: Cancel, Create, Divide, Delete, Reissue, Reprice, Update + + + + + + + Action Type Context. + + + + + + + + + + + + + + Reference to the existing Order(s) to be changed. + +The airline-assigned unique Order ID. Example: ORDER-c98c-4759-a20b + + + + + + + Airline Designator of airline that owns/ assigned this ID. Example: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Codes + + + + + The POA OrderID should only go to the ORA, not back to the seller. +1. ORA +2. POA + + + + + + + + + + + + + + + Reference to PADIS codeset REA. When used, provides context for the change being requested. + + + + + + Collection of functions used by the seller to request the airline to commit changes to an existing Order. These may be adding, removing or replacing Order Items (with potential refund conditions, in case of cancellations). The actions possible are determined by the airline and communicated to the seller at the time of an OrderReshopRS (which precedes OrderChangeRQ). It is up to the seller to then accept the proposed actions from the OrderReshopRS by echoing these functions in this OrderServicing structure. + + + + + + Function to accept a new OfferItem and adding it to the existing Order. + + + + + + + + + + Function to accept the deletion of an OrderItem from the existing Order. + + + + + + + + + + + + + Function to Add, Remove or Update the Passenger Details. Providing the New and Previous values together implies an Update. + + + + + + If used alone, requests the addition of information to the passenger details. + + + + + + Type code applying to the Passenger which typically drives pricing (e.g. ADT, CHD, etc). + + + + + + The Age of the Passenger. To be used in NDC Anonymous Shopping requests or when the birthdate (in Individual) is not known. + + + + + The Date of Birth of the Passenger. Anonymous Shopping requests or when the birthdate (in Individual) is not known. + + + + + + Residence Country Code. Examples: US, FR. + + + + + Citizenship Country Code. Examples: US, FR. + + + + + A single human being as distinct from a group, class, or family. + + + + + Passenger Profile ID + + + + + An account set up for a customer within a rewards program which holds funds on behalf of that customer. + + + + + Form of identification. Typically used to identify that the passenger is who he says he is. + +This is the type of FOID as defined in AIRIMP (FF Number, Credit Card Number, etc.). + + + + + + Any document which may be used to identify a person or verify aspects of a person's personal identity. + + + + + Reference to Contact Information, within the context of one message. + + + + + Reference to Passenger instance within the context of one message, associating an infant on lap to this adult passenger. + + + + + Language Code representation. + + + + + Additional, supplementary information about the document or service. + + + + + + + + + + Add or Delete + + + + + + Uniquely identifies a Passenger within the context of one message. + + + + + When true, passenger authorizes the airline to share his/her profile information or send promotional emails. + + + + + + + If used alone, requests the removal of information to the passenger details. + + + + + + Type code applying to the Passenger which typically drives pricing (e.g. ADT, CHD, etc). + + + + + + The Age of the Passenger. To be used in NDC Anonymous Shopping requests or when the birthdate (in Individual) is not known. + + + + + The Date of Birth of the Passenger. Anonymous Shopping requests or when the birthdate (in Individual) is not known. + + + + + + Residence Country Code. Examples: US, FR. + + + + + Citizenship Country Code. Examples: US, FR. + + + + + A single human being as distinct from a group, class, or family. + + + + + Passenger Profile ID + + + + + An account set up for a customer within a rewards program which holds funds on behalf of that customer. + + + + + Form of identification. Typically used to identify that the passenger is who he says he is. + +This is the type of FOID as defined in AIRIMP (FF Number, Credit Card Number, etc.). + + + + + + Any document which may be used to identify a person or verify aspects of a person's personal identity. + + + + + Reference to Contact Information, within the context of one message. + + + + + Reference to Passenger instance within the context of one message, associating an infant on lap to this adult passenger. + + + + + Language Code representation. + + + + + Additional, supplementary information about the document or service. + + + + + + + + + + Add or Delete + + + + + + Uniquely identifies a Passenger within the context of one message. + + + + + When true, passenger authorizes the airline to share his/her profile information or send promotional emails. + + + + + + + + + + Function used by seller to inform the airline that it is accepting the proposed Order, as it has been repriced and returned in the preceding OrderReshopRS. + + + + + + + + + + + Payment information. + + + + + + Payment detail, including association(s). + + + + + + + + + + + + + + + Association to one or multiple Offer Items instance(s). Example:OI1 OI2 + + + + + + + Reference to the OfferID of the selected Offer (either a standard Offer or an a-la-carte Offer) returned in a previous shopping response. + + + + + Designator of Airline that owns/ assigned these IDs. Examples: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Code + + + + + Reference to unique shopping session response ID, as provided in the airline's previous shopping response. + + + + + + + + + + + + + + + + + + + Existing Booking Reference (e.g. PNR Record Locator). Example: R1A3SK + + + + + + + + + Data Lists(s). + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Enumeration: + +CarryOn +Checked + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + + + + + + Description Details + + + + + + + + + + + + List of Flight Segments + + + + + + + + + + List of Flight elements. + + + + + + Journey information describing the travel between an airport/city where travel commences and an airport/city where travel ultimately terminates. A journey may be comprised of one or more segments. Note: This node will be renamed to journey in future releases. + + + + + + Flight journey information. + + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + + + A globally unique identifier for this Flight instance. Example: flight1 + + + + + + + + + + List of Origin/Destination elements. + + + + + + + + + + + + + Price Class list. + + + + + + + + + + Description and characteristics of a Service + + + + + + + + + + + + + + Seat information by aircraft section. + + + + + + + + + + Description value. + + + + + + + + + + + + Mark-up Style. Example: HTML + + + + + + LINK to Description information source. + + + + + Description-associated Media Object(s). + + + + + + Description-associated MEDIA OBJECT ID or Key. Example: IMG1 + + + + + Description-associated MEDIA LINK. + + + + + Description-associated Media Attachment ID. Example: ATT1. + + + + + + + + + + + Images and/or links for the entire section defined by the range of rows. + + + + + + + + + + Refers to aircraft seat characteristics; seat option codes. Examples: E (EXIT ROW), M (Middle Seat), A (Aisle seat), L (Left side of aircraft), Q (Bulk Head). Refer to PADIS code list 9825. + + + + + Associated Keyword Unit of Measure, if relevant. Example: INCH + + + + + Lowest Width Measurement value for this section. Example: 20 + + + + + Lowest Pitch Measurement value for this section. Example: 32 + + + + + Seat Description Key-Value Word Pairs. +Examples: +ReclineDegree - 25 +BedLengthLowEnd - 68 +BedLengthHighEnd - 78 +WidthLowEnd - 20 +WidthHighEnd - 21.5 +PitchLowEnd - 32 +PitchHighEnd - 34.4 + + + + + + + Key-Value detail. + + + + + + + + + + + + + + + + + + + + + + Metadata. + + + + + Parameters that influence overall message results. + +Note: These capabilities may not be supported by all EDIST-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + + + + + + Metadata definition. + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Message Parameters. + + + + + + + Reason for change. + +Encoding Scheme: IATA Padis Codeset REA + + + + + + + + Information relating to prepayment vouchers. + + + + + + + + Check (Cheque) Payment + + + + + If true, preference is to apply refund to carrier credit. + + + + + + When true, it is requested that the refund be applied to the original FOP + + + + + + + + Object association(s) between this object and any other object or metadata instance(s). + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OrderCreateRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderCreateRQ.xsd new file mode 100644 index 00000000..72754a25 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderCreateRQ.xsd @@ -0,0 +1,561 @@ + + + + + + + + The OrderCreate/ OrderView transaction is a multi-function message that may: + +1) Request specified inventory to be held (and returns a reference to the held inventory) + +2) Request that an order to be created (returning the complete view of the Order) + +3) Request additions to order data elements (e.g. add frequent flyer data) + + + + + + + + + + Order Create Query. + + + + + + Group Information. + + + + + Order to be created. + +Two methods are provided for specifying shopping Offer Items that are to be converted into Order Items: + +i) Specifying OfferItems from one or more Offers (whether standard Offers or “A-La-Carte” Offers) by referencing respective OfferItemIDs and the OfferID they are contained in. Further to that, the ResponseID of each Offer must also be specified, which allows the selection of Offers from un-related shopping responses. Multiple Offers would then be merged by the airline and combined into one single Order in the resulting OrderViewRS. Additionally, mechanisms are provided for the selection of different quantities of OfferItems (in the case of a-la-carte OfferItems), the selection of services from combinations/bundles (e.g. “pick 3 out of 5 services”) and the selection of particular seats by specific passengers. + +ii) Specifying individual Order Item Sets and their associated Offer Item(s). This supports EDIST-enabled systems that return multiple Offer Items associated with one flight, e.g. an outbound flight offer and an inbound flight offer. + + + + + + + + + + + Payment information. + + + + + + Payment detail, including association(s). + + + + + + + + + + + + + + + Association to one or multiple Offer Items instance(s). Example:OI1 OI2 + + + + + + + Reference to the OfferID of the selected Offer (either a standard Offer or an a-la-carte Offer) returned in a previous shopping response. + + + + + Designator of Airline that owns/ assigned these IDs. Examples: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Code + + + + + Reference to unique shopping session response ID, as provided in the airline's previous shopping response. + + + + + + + + + + + + + + + + + + Promotion information. + + + + + + Promotion Code. + + + + + + + + Passenger(s)/ Group(s) associated with the Promotion. + + + + + + Association to multiple Passenger instance(s). Example: pax1 pax2 + + + + + + + + + + + + + + + + + Commission information + + + + + Existing Booking Reference (e.g. PNR Record Locator). Example: R1A3SK + + + + + Data Lists(s). + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Enumeration: + +CarryOn +Checked + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + + + + + + Description Details + + + + + + + + + + + + List of Flight Segments + + + + + + + + + + List of Flight elements. + + + + + + Journey information describing the travel between an airport/city where travel commences and an airport/city where travel ultimately terminates. A journey may be comprised of one or more segments. Note: This node will be renamed to journey in future releases. + + + + + + Flight journey information. + + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + + + A globally unique identifier for this Flight instance. Example: flight1 + + + + + + + + + + List of Origin/Destination elements. + + + + + + + + + + + + + Price Class list. + + + + + + + + + + Description and characteristics of a Service + + + + + + + + + + + + + + Seat information by aircraft section. + + + + + + + + + + Description value. + + + + + + + + + + + + Mark-up Style. Example: HTML + + + + + + LINK to Description information source. + + + + + Description-associated Media Object(s). + + + + + + Description-associated MEDIA OBJECT ID or Key. Example: IMG1 + + + + + Description-associated MEDIA LINK. + + + + + Description-associated Media Attachment ID. Example: ATT1. + + + + + + + + + + + Images and/or links for the entire section defined by the range of rows. + + + + + + + + + + Refers to aircraft seat characteristics; seat option codes. Examples: E (EXIT ROW), M (Middle Seat), A (Aisle seat), L (Left side of aircraft), Q (Bulk Head). Refer to PADIS code list 9825. + + + + + Associated Keyword Unit of Measure, if relevant. Example: INCH + + + + + Lowest Width Measurement value for this section. Example: 20 + + + + + Lowest Pitch Measurement value for this section. Example: 32 + + + + + Seat Description Key-Value Word Pairs. +Examples: +ReclineDegree - 25 +BedLengthLowEnd - 68 +BedLengthHighEnd - 78 +WidthLowEnd - 20 +WidthHighEnd - 21.5 +PitchLowEnd - 32 +PitchHighEnd - 34.4 + + + + + + + Key-Value detail. + + + + + + + + + + + + + + + + + + Metadata List(s). + + + + + + + + + + + + Parameters that influence overall message results. + +Note: These capabilities may not be supported by all EDIST-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + + + + + + Metadata definition. + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Message Parameters. + + + + + + + + Object association(s) between this object and any other object or metadata instance(s). + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OrderHistoryRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderHistoryRQ.xsd new file mode 100644 index 00000000..8330f012 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderHistoryRQ.xsd @@ -0,0 +1,59 @@ + + + + + + + The OrderHistory transaction set requests the transaction history and audit trail for a specified Order. + +Note that this transaction is only available to the order creation requestor. + + + + + + + + + + Order History Query. + + + + + + + + + + + + + + Parameters that influence overall message results. + +Note: These capabilities may not be supported by all EDIST-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Message Parameters. + + + + + + + Object association(s) between this object and any other object or metadata instance(s). + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OrderHistoryRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderHistoryRS.xsd new file mode 100644 index 00000000..95d201c2 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderHistoryRS.xsd @@ -0,0 +1,547 @@ + + + + + + + + The OrderHistory transaction set requests the transaction history and audit trail for a specified Order. + +Note that this transaction is only available to the order creation requestor. + + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + Query Results. + + + + + + Transaction Processing Results, including processing status, alerts, notices, business warnings, supplemental marketing messages and policy. + + + + + Order Action(s). + + + + + + Order Action. + + + + + + Order Action. Examples: Cancel, Create, Update, Delete, Reissue, Reprice + + + + + + + Action Type Context. + + + + + + + + + Action Date. + + + + + Entity that performed the action. + + + + + + Entity ID. Examples: ABC123, jsmith + + + + + Entity Name. Examples: Carson Travel, Jane Smith + + + + + + + + Transaction Type. Example: OrderCreate + + + + + Order Action Details. + + + + + + Commission information. + + + + + Group Information. + + + + + Order Item(s). + + + + + + + + + + Passenger Information. + + + + + + + + + + Payment information. + + + + + + Payment detail. + + + + + + + + Total Order Price. Example: 3400 USD + +Note: This is a sub-total of all associated Order Item prices. + Currency, Redemption and Partial Pricing + + + + + Ticket/ Document Information. + + + + + + Ticket/document information. + + + + + + Booking and Servicing Agent information. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Data Lists(s). + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Enumeration: + +CarryOn +Checked + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + + + + + + Description Details + + + + + + + + + + + + List of Flight Segments + + + + + + + + + + List of Flight elements. + + + + + + Journey information describing the travel between an airport/city where travel commences and an airport/city where travel ultimately terminates. A journey may be comprised of one or more segments. Note: This node will be renamed to journey in future releases. + + + + + + Flight journey information. + + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + + + A globally unique identifier for this Flight instance. Example: flight1 + + + + + + + + + + List of Origin/Destination elements. + + + + + + + + + + + + + Price Class list. + + + + + + + + + + Description and characteristics of a Service + + + + + + + + + + + + + + Seat information by aircraft section. + + + + + + + + + + Description value. + + + + + + + + + + + + Mark-up Style. Example: HTML + + + + + + LINK to Description information source. + + + + + Description-associated Media Object(s). + + + + + + Description-associated MEDIA OBJECT ID or Key. Example: IMG1 + + + + + Description-associated MEDIA LINK. + + + + + Description-associated Media Attachment ID. Example: ATT1. + + + + + + + + + + + Images and/or links for the entire section defined by the range of rows. + + + + + + + + + + Refers to aircraft seat characteristics; seat option codes. Examples: E (EXIT ROW), M (Middle Seat), A (Aisle seat), L (Left side of aircraft), Q (Bulk Head). Refer to PADIS code list 9825. + + + + + Associated Keyword Unit of Measure, if relevant. Example: INCH + + + + + Lowest Width Measurement value for this section. Example: 20 + + + + + Lowest Pitch Measurement value for this section. Example: 32 + + + + + Seat Description Key-Value Word Pairs. +Examples: +ReclineDegree - 25 +BedLengthLowEnd - 68 +BedLengthHighEnd - 78 +WidthLowEnd - 20 +WidthHighEnd - 21.5 +PitchLowEnd - 32 +PitchHighEnd - 34.4 + + + + + + + Key-Value detail. + + + + + + + + + + + + + + + + + + + + + + + + + Transaction Processing Results, including processing status, alerts, business warnings, supplemental marketing messages and policy. + + + + + Response Message Processing. + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OrderListRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderListRQ.xsd new file mode 100644 index 00000000..5272e9a0 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderListRQ.xsd @@ -0,0 +1,687 @@ + + + + + + + + The OrderList transaction set retrieves a list of Orders that match one or more search criteria. + + + + + + + + + + Order List Query. + + + + + + Query Filters. + + + + + + Agency. + + + + + + + Agency Seller Name. Example: Carson Travel + + + + + Agency Seller IATA number. Example: 98417900 + + + + + + + + Airline. + + + + + + + Airline Name. Example: British Airways + + + + + + + + Existing Booking Reference (e.g. PNR Record Locator). Example: R1A3SK + + + + + Order Cancellation Date Range. + + + + + + + + + + Order Creation Date Range. + + + + + + + + + + Flight Filters. + + + + + + + + + Arrival Airport. + + + + + + Arrival Airport Location code. Example: GVA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Arrival date. Example: 2017-01-14 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + + + + Departure Airport. + + + + + + Departure Airport Location code. Example: TPA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Departure date. Example: 2017-01-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + + + + Flight origin/ destination information. + + + + + + Departure Airport. + + + + + + Departure Airport Location code. Example: TPA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Departure date. Example: 2017-01-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + + + + Arrival Airport. + + + + + + Arrival Airport Location code. Example: GVA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Arrival date. Example: 2017-01-14 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + + + + + + + + Flight segment information. + + + + + + Departure Airport. + + + + + + Departure Airport Location code. Example: TPA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Departure date. Example: 2017-01-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + + + + Arrival Airport. + + + + + + Arrival Airport Location code. Example: GVA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Arrival date. Example: 2017-01-14 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + + + + + + + + + + + Group Information. + + + + + + Group Name. Example: ABC Tour Club + + + + + The Complete Party (TCP) indicating total party size. Example: 12 + + + + + + + + + Passenger information. + + + + + + A single human being as distinct from a group, class, or family. + + + + + + Individual's first or given name. Example: JOHN. + + + + + Individual's middle name or initial. Examples: G, GEORGE + + + + + Individual's family name, last name. Example: SMITH. + + + + + + + + Passenger Profile ID + + + + + The account set up for a customer within a rewards program which holds funds on behalf of that customer. + + + + + + An enterprise operating aircraft for commercial purposes + + + + + Loyalty Program Name. Example: Miles and More + + + + + Loyalty Program ID: Example: MAM + + + + + Loyalty Program account number. Example: ABC123456 + + + + + Loyalty Program sign-in ID (or username). + + + + + + + + Form of identification. Typically used to identify that the passenger is who he says he is. + +This is the type of FOID as defined in AIRIMP (FF Number, Credit Card Number, etc.). + + + + + + Any document which may be used to identify a person or verify aspects of a person's personal identity. + + + + + Contact Information, within the context of one message. + + + + + + Classification for a particular set of contact information (e.g. Primary, Payment, etc.) + + + + + The address used for postal service. Examples are post office boxes address, postal physical address, postal code + + + + + The email address which should be used for contact purposes. + + + + + A telephone number is a sequence of digits assigned to a fixed-line telephone subscriber station connected to a telephone line or to a wireless electronic telephony device, such as a radio telephone or a mobile telephone, or to other devices for data transmission via the public switched telephone network (PSTN) or other private networks. + + + + + + Other Contact Method information. (i.e. social media handle, website, etc.) + + + + + + + + + + + Payment information. + + + + + + The amount for this form of payment. Example: 300 USD + + + + + Payment Method detail. + + + + + + Credit card issuer code. Example: MC + +Note: This is the 2 character code of the credit card issuer. + + + + + Concealed credit card number, Example: xxxxxxxxxxxx9922 + + + + + + + + + + + + Tokenized card number. + +Note: This capability may not be supported by all EDIST-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of this capability is not dictated by this specification. + + + + + Payment Card Effective and/ or Expiration date(s). + + + + + + Payment Card Effective Date. Example: 0116 + + + + + Payment Card Expiration Date. Example: 0119 + + + + + + + + + Name of credit card holder. Example: JOHN SMITH + + + + + + + + + + + + + + + + Payment Status. Examples: Canceled, Complete, Failed + + + + + + + Payment Status Context. + + + + + + + + + + + + Ticket document numbers. + + + + + + Issue Date Range. + + + + + + + + + + Coupon Document Number. + +Note: This is the document number comprised of the airline code, form code, and serial number. + + + + + + + + + + + Airport or City Code. Example: JFK + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + Applicable coupon number. Example: 1234 + + + + + + + + + + + Ticketing Status. Examples: Requested, Ticketed, Other + + + + + + + Context. + + + + + + + + + + + + Travel Date Range. + + + + + + + + + + Service information. + + + + + + + + + + + + + + + + + + + + + Parameters that influence overall message results. + +Note: These capabilities may not be supported by all EDIST-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Message Parameters. + + + + + + + Object association(s) between this object and any other object or metadata instance(s). + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OrderListRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderListRS.xsd new file mode 100644 index 00000000..11b01989 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderListRS.xsd @@ -0,0 +1,272 @@ + + + + + + + + The OrderList transaction set retrieves a list of Orders that match one or more search criteria. + + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + Query Results. + + + + + + Transaction Processing Results, including processing status, alerts, notices, business warnings, supplemental marketing messages and policy. + + + + + Matched Order(s). + + + + + + Matched Order. + + + + + + Agency. + + + + + + + Agency Seller Name. Example: Carson Travel + + + + + Agency Seller IATA number. Example: 98417900 + + + + + + + + Order Creation Date. + + + + + Departure Airport. + + + + + + Departure Airport Location code. Example: TPA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Departure date. Example: 2017-01-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + + + + Arrival Airport. + + + + + + Arrival Airport Location code. Example: TPA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Arrival date. Example: 2017-01-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + + + + Number in Party. Example: 2 + + + + + + + + + + + + Passenger and Group information. + + + + + + Group Information. + + + + + Passenger Full Name. Example: JOHN SMITH + + + + + + + + + + + + + + + Ticketing Status. Examples: Requested, Ticketed, Other + + + + + + + Context. + + + + + + + + + Order Identificatio + + + + + Current status of the Order Item and related indicators. + + + + + + + Current Order Item status. Example: OK (Confirmed) Encoding Scheme: IATA Padis Codeset - List for data element 4405 (Status, coded) + + + + + + + + When true, the order item cannot be fulfilled due to an aircraft change. + + + + + + + When true, the order item cannot be fulfilled due to a flight schedule change. + + + + + + + + + + + + + + + + + + + + + + + + Transaction Processing Results, including processing status, alerts, business warnings, supplemental marketing messages and policy. + + + + + Response Message Processing. + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OrderReshopRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderReshopRQ.xsd new file mode 100644 index 00000000..8df62cc8 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderReshopRQ.xsd @@ -0,0 +1,876 @@ + + + + + + + + The OrderReshop transaction set passes new shopping requests to an airline to replace existing specified order or order items in an Order or for new shopping requests to add to an existing Order. Airline responds with product offers within the context of the existing Order. + +There is no change to the Order or Order Items, in response to a Reshop request - typically, the Reshop response will be followed by an OrderChangeRQ or OrderCancelRQ transaction, to commit the re-shop offer. + +In the response, the Airline can provide exact instructions as to what actions can finally be executed, as a solution to the initially requested action. + + + + + + + + + + Reshop actions to enquire about desired changes for a given order. New OfferItems will be presented in subsequent response, which will incur reconstruction of new OrderItems post-OrderChangeRQ. + + + + + + Reference to existing Order to which the Seller wants to add, udpate, delete an OrderItem. + + + + + Existing Booking Reference (e.g. PNR Record Locator). Example: R1A3SK + + + + + Reference to PADIS codeset REA. When used, provides context for the change being requested. + + + + + + Function used to reshop items within an order (e.g. adding ancillaries, cancelling order items, replacing order items). + + + + + + Functions to allow a Seller to request additions, replacement or deletions of OrderItems in this specific Order. + + + + + + Action to request new Offer Items for this specific Order. + +If used in conjunction with a “Delete” function, the intention is to replace the deleted item with whatever has been requested in this Add function’s shopping query. + + + + + + [Re-using the query structure from AirShoppingRQ] + +Core Air Shopping information by supported Air Shopping Query type. + +Shopping Query Input may be specified as: +1) Prior Shopping Session Basket +2) Attribute Shopping Query +3) Affinity Shopping Query + + + + + + + + + Flight origin/ destination information. + + + + + + + + + + + + + + + + + + + + + + + + + + Trip Budget. + + + + + + + + + + + Affinity Query Keyword(s) with optional preference level. + + + + + + Keyword/ Value Search Criteria. + +Note: Keyword-Value pairs may be used to specify a variety of affinity qualifiers, such as Climate, Activity, and Point of Interest. + + + + + + + + + + + + + + + + + + + ATTRIBUTE Query ORIGIN/ DESTINATION qualifiers and preferences. + +Note: +1. An Attribute Query is a search specifying one or more attributes to get more focused results Note that this node only contains Origin/ Destination Airport/ City code information which are mandatory. + +2. Other Attribute Query parameters that may be specified (in other document nodes) include Aircraft Equipment preferences, Seat types and characteristics, Meal preferences and Special Need qualifiers. + + + + + + Flight origin/ destination information. + + + + + + + + FLIGHT DEPARTURE (ORIGIN). + + + + + FLIGHT ARRIVAL (DESTINATION). + + + + + + Flight-related shopping response IDs, including the unique (master) Shopping Session ID, Offer IDs, Offer Item IDs and Service IDs. + + + + + + Indicates a calendar search request with days before and/or days after the specified date. + + + + + Number of days befiore the specified date. + + + + + Number of days after the specified date. + + + + + + + + A globally unique identifier for this OriginDestination instance. Example: origDest1 + + + + + + + + + + + + + + + FlighSegment information. Contains details flight segment information. + + + + + + + + Marketing Carrier information. + + + + + Operating Carrier information. + +Note: This is the carrier that holds the Air Operator’s Certificate for the aircraft used for that flight. + + + + + + A globally unique identifier for this Flight Segment instance. Example: segment1 + + + + + + + Flight information. Flight can be made of one to multiple FlightSegment elements. For example Flight can be made of flight segment BA123 and BA34. + + + + + + Flight journey information. + + + + + + + + A globally unique identifier for this Flight instance. Example: flight1 + + + + + + + + + + + + + + Qualifier choices. + +Notes: +1. These qualifiers may be specified for (e.g. apply to) both Attribute and Affinity queries. +2. These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of the capability is not dictated by this specification. + + + + + + + + + + + + + + + + + Contains Forms of Payment type and may include a reference to a passenger. + + + + + + Association to multiple Passenger instance(s). Example: Passenger1 Passenger2 + +Note: May be Recognized or Anonymous Passenger (by PTC) instance(s). + + + + + The form of payment type. Examples: Credit Card, Cash. + +Encoding Scheme: IATA PADIS code list data element [9888] Form of Payment Identification + + + + + + + + + + + Preference choices. + +Notes: +1. These preferences may be specified for (e.g. apply to) both Attribute and Affinity queries. +2. These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of the capability is not dictated by this specification. + + + + + + + + + + + + + + + + + + Reference to passenger to be added to existing order. + + + + + + + + + + + + + Function to request the removal of Order Items from this specific Order. + +If used alone (without a shopping query from the “Add” function), the RS will assume a cancellation is desired for the Order Items specified and will return incurred fees/refund amounts and/or alternative OfferItems. + +If used in conjunction with an “Add” function, the intention is to replace this deleted item with whatever has been requested in the Add function’s shopping query. + + + + + + + + + Reference to the Services within the specified Order Item which the Passenger would like the Airline to retain and return within the proposed Offer Item(s) in the OrderReshopRS. + + + + + + Reference to the Order Item requested for deletion. + + + + + + + + + + + + + Request to Airline whether any fees will apply to a proposed correction to a Passenger's name details. + + + + + + Identifier of the Passenger within the Order in the Order Management System. This is the PassengerID that is assigned at the time of Order creation by the Airline. + + + + + Individual's name title. Examples: MR, MRS, DRn. + + + + + Individual's first or given name. Example: JOHN. + + + + + Individual's middle name or initial. Examples: G, GEORGE + + + + + Individual's family name, last name. Example: SMITH. + + + + + Individual's surname suffixes and letters. Examples: Jr., Sr., III, Ret., Esq. + + + + + + + + + + + Function to reprice entire Order (if only OrderID is supplied within Query) or Specific OrderItems (if defined in nested OrderItem elements) + + + + + + Optionally specify which OrderItem needs to be repriced. + + + + + + + + + + + + Data Lists(s). + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Enumeration: + +CarryOn +Checked + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + + + + + + Description Details + + + + + + + + + + + + List of Flight Segments + + + + + + + + + + List of Flight elements. + + + + + + Journey information describing the travel between an airport/city where travel commences and an airport/city where travel ultimately terminates. A journey may be comprised of one or more segments. Note: This node will be renamed to journey in future releases. + + + + + + Flight journey information. + + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + + + A globally unique identifier for this Flight instance. Example: flight1 + + + + + + + + + + List of Origin/Destination elements. + + + + + + + + + + + + + Price Class list. + + + + + + + + + + Description and characteristics of a Service + + + + + + + + + + + + + + Seat information by aircraft section. + + + + + + + + + + Description value. + + + + + + + + + + + + Mark-up Style. Example: HTML + + + + + + LINK to Description information source. + + + + + Description-associated Media Object(s). + + + + + + Description-associated MEDIA OBJECT ID or Key. Example: IMG1 + + + + + Description-associated MEDIA LINK. + + + + + Description-associated Media Attachment ID. Example: ATT1. + + + + + + + + + + + Images and/or links for the entire section defined by the range of rows. + + + + + + + + + + Refers to aircraft seat characteristics; seat option codes. Examples: E (EXIT ROW), M (Middle Seat), A (Aisle seat), L (Left side of aircraft), Q (Bulk Head). Refer to PADIS code list 9825. + + + + + Associated Keyword Unit of Measure, if relevant. Example: INCH + + + + + Lowest Width Measurement value for this section. Example: 20 + + + + + Lowest Pitch Measurement value for this section. Example: 32 + + + + + Seat Description Key-Value Word Pairs. +Examples: +ReclineDegree - 25 +BedLengthLowEnd - 68 +BedLengthHighEnd - 78 +WidthLowEnd - 20 +WidthHighEnd - 21.5 +PitchLowEnd - 32 +PitchHighEnd - 34.4 + + + + + + + Key-Value detail. + + + + + + + + + + + + + + + + + + + + + + Parameters that influence overall message results. + +Note: These capabilities may not be supported by all EDIST-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Request Message Parameters. + + + + + Transaction Processing Alert(s). + +Note: Alerts contain processing information have resulted in successful, but incomplete transaction processing that initiate - or are part of - an ongoing transaction. + + + + + + Traveler PIN Phrase Authentication Response. + +Notes: +1. This is part of an ongoing transaction for a processing condition that occured when additional Traveler authentication was required to complete transaction processing, such as access to secure FQTV information to complete Order amendment. +2. This information contains the authentication scheme response information, e.g. the Pin Phrase answer. + + + + + + + + Transaction Processing Notice(s). + +Note: These notices contain requested transaction processing parameters that may be ignored by EDIST-enabled systems that do not support the capability. + + + + + + + + + Pricing Parameters Notice. + +Note: Supports specifying transaction pricing parameters. Request messages may include indicators requesting that certain methods be applied during payment processing where relevant. Response messages may additionally include notice about if and how pricing parameters were applied during transaction processing. + + + + + When true, this request is to be handled by an auto-exchange process. + + + + + When true, award eligible in addition to priced offers and fares is requested. + + + + + When true, only award eligible offers/ fares are requested. + + + + + When true, Simple Pricing for flight offers is requested. + + + + + + + + + + + + Requested search processing and results currency information. + +Notes: +1. Currency context is specified in the @application attribute, e.g. Requested, Display. + + + + + + + + + + Reason for change. + +Encoding Scheme: IATA Padis Codeset REA + + + + + + Object association(s) between this object and any other object or metadata instance(s). + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OrderReshopRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderReshopRS.xsd new file mode 100644 index 00000000..c48ddcee --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderReshopRS.xsd @@ -0,0 +1,1173 @@ + + + + + + + + The OrderReshop transaction set passes new shopping requests to an airline to replace existing specified order or order items in an Order or for new shopping requests to add to an existing Order. Airline responds with product offers within the context of the existing Order. + +There is no change to the Order or Order Items, in response to a Reshop request - typically, the Reshop response will be followed by an OrderChangeRQ or OrderCancelRQ transaction, to commit the re-shop offer. + +In the response, the Airline can provide exact instructions as to what actions can finally be executed, as a solution to the initially requested action. + + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + Query Results. + + + + + + Transaction Processing Results, including processing status, alerts, notices, business warnings, supplemental marketing messages and policy. + + + + + A collection of shopping session (message response) IDs, including the unique (master) Shopping Response ID, Offer IDs, Offer Item IDs and Service IDs. + +Notes: This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + Notes: +1. This capability supports reduced message payload sizes by providing a mechanism that supports references to cached Shopping Transactions and/ or Offer information so only object identifiers (e.g. Offer, Service) need to be exchanged in a subsequent Shopping request message, versus specifying the full object details. + +2. This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Group Information. + + + + + + + + Order Action. Examples: Cancel, Create, Update, Delete, Reissue, Reprice + + + + + + + Action Type Context. + + + + + + + + + + + + + + + Reshopped airline offer(s). + + + + + + Reshopped airline offer + + + + + + + + Summary of proposed flight information in the context of this specific Offer. + + + + + + Reference to the Flight ID specified within this Offer. Should be repeated for all Flights included. + + + + + + + Reference to the Origin/Destination ID specified within this Offer. + + + + + Flight-level price class + + + + + + + + + Itinerary-level price class (eg. most restrictive applies) + + + + + + + + OrderItems which the Airline confirms can be deleted in a subsequent OrderChangeRQ. Optionally, a price differential (e.g. refund amounts) can be added to each OrderItem occurrence being deleted. + +Should not be used for "replace" type functions. In the case the Seller is attempting to replace an OrderItem, this item should only be referenced from the AddOfferItem's attribute "OrderItemIDs". + + + + + + It contains the Original order amount, new offer amount, penalty details, fees and due by details. It also contains the taxes information. + + + + + + Original order fare details. + + + + + + + Tax Information. + + + + + + + + New order offer fare details. + + + + + + + Tax Information. + + + + + + + + Penalty fare details. + + + + + + + Tax Information. + + + + + + + + Fees information. + + + + + + + Tax Information. + + + + + + + + Whether the reshop differential is due by passenger or airline. + + + + + + + Use when reshop is due by Passenger. + + + + + + + + + + Use when reshop is due by Airline. + + + + + + + + + + + Tax Information. + + + + + + + + + + + + Unique identifier for this OfferItem instance. Must be unique within XML message. Exceeding 64 characters or use of dashes is not recommended. + + + + + + If set to 'true', indicates mandatory Offer Items which cannot be removed from the Offer. Mandatory Offer Items transition into Order Items. If not present or 'false', the Offer item is optional. The aggregate price at the Offer level initially reflects the sum of the prices for all Mandatory Offer Items within it. + + + + + POA to ORA only: to indicate that the offer is non-modifiable. This indicates to ORA that its offer is non-modifiable (eg. Regulatory or brand protection reasons). If indicator is set to true, nodifications to the POA’s offer ARE NOT allowed. + + + + + + + Offers presented in response to a shopping query from the “Add” function in OrderReshopRQ. If original query also specified items for deletion, the suggested Offers/OfferItems here could be meant to replace the OrderItems specified in the request's Delete function – the differential in price would then be presented in the “ReshopDifferential” structure. + + + + + + + + It contains the Original order amount, new offer amount, penalty details, fees and due by details. It also contains the taxes information. + + + + + + Original order fare details. + + + + + + + Tax Information. + + + + + + + + New order offer fare details. + + + + + + + Tax Information. + + + + + + + + Penalty fare details. + + + + + + + Tax Information. + + + + + + + + Fees information. + + + + + + + Tax Information. + + + + + + + + Whether the reshop differential is due by passenger or airline. + + + + + + + Use when reshop is due by Passenger. + + + + + + + + + + Use when reshop is due by Airline. + + + + + + + + + + + Tax Information. + + + + + + + + + + + + Reference to one or more OrderItems that are going to be replaced by this OfferItem. + + + + + + + + + Function to request a change and/or correction to a passenger name for the specified Order. + + + + + + + + Structure to echo back the name changes allowed by the Airline, packaged within an OfferItem + + + + + + Identifier of the Passenger within the Order in the Order Management System. This is the PassengerID that is assigned at the time of Order creation by the Airline. + + + + + Individual's name title. Examples: MR, MRS, DRn. + + + + + Individual's first or given name. Example: JOHN. + + + + + Individual's middle name or initial. Examples: G, GEORGE + + + + + Individual's family name, last name. Example: SMITH. + + + + + Individual's surname suffixes and letters. Examples: Jr., Sr., III, Ret., Esq. + + + + + + + + + + + + + This block contains references to the Baggage Allowance characteristics (no. of pieces / weight / dimensions, etc) included in the Flight services for one or more Passengers. + + + + + + Reference to FlightIDs in DataLists + + + + + Reference to PassengerIDs in DataLists + + + + + Reference to BaggageAllowanceIDs in DataLists + + + + + + + + + + + + + Container for standalone optional OfferItems. This supports the shopping basket concept. The main purpose of this structure is to reduce the size of the message by inserting Offer Items which are applicable to multiple flight-related Offers defined above. + +NB. For the OfferID of the ALaCarteOffer: Default OfferID identifier for A La Carte Offer Items in a scenario where items here are not selected for a flight-related Offer above. + + + + + + + + One Service or Service Bundle which is priced per unit. A La Carte Offer Items are optional and variable quantities of these can be selected by any of the eligible passengers for the applicable segments and/or price classes. + + + + + + + + + + + + + Function used to request the repricing of an existing Order, possibly as a consequence of expired TimeLimits. Airline returns Offers/OfferItems that describe the changes incurred from the reprice request. + + + + + + Offers presented in response to a reprice request in the OrderReshopRQ. If there is a change in the price of the Order, these Offers may be subsequently accepted in the OrderChangeRQ and the repriced OrderItems (returned as OfferItems) will then replace the old OrderItems. + + + + + + Total price reflecting all services for all passengers across all segments referenced within this Offer Item. + + + + + + Total price amount. + +Notes: +1. This is typically the lowest price for this alternate lead shopping date. +2. If expressed in currency, this price should include base price, taxes and fees/ surcharges. + + + + + + + + + + + + + + Total Base Fare Amount. Example: 200000 + +Note: This includes surcharges (if applicable). + + + + + + Discount Information + + + + + Applicable Surcharge(s). + + + + + + Surcharge detail. + + + + + + + + Ticket Tax/fee/charge details to indicate taxes that apply to country of commencement of travel and routing. + + + + + + + AWARD (Redemption Unit-based) Pricing information. + + + + + PARTIAL CURRENCY and AWARD Pricing Combination information. + + + + + + Individual fee/ surcharge information would appear on the accountable document. + + + + + + + + + + + + + Fare Detail, including Fare Component and Fare Rules. + + + + + + + + Total price reflecting all services for all passengers across all segments referenced within this Offer Item. + + + + + + Total price amount. + +Notes: +1. This is typically the lowest price for this alternate lead shopping date. +2. If expressed in currency, this price should include base price, taxes and fees/ surcharges. + + + + + + + + + + + + + + Total Base Fare Amount. Example: 200000 + +Note: This includes surcharges (if applicable). + + + + + + Discount Information + + + + + Applicable Surcharge(s). + + + + + + Surcharge detail. + + + + + + + + Ticket Tax/fee/charge details to indicate taxes that apply to country of commencement of travel and routing. + + + + + + + AWARD (Redemption Unit-based) Pricing information. + + + + + PARTIAL CURRENCY and AWARD Pricing Combination information. + + + + + + Individual fee/ surcharge information would appear on the accountable document. + + + + + + + + + + + + + Fare Detail, including Fare Component and Fare Rules. + + + + + + + + + + Unique identifier for this OfferItem instance. Must be unique within XML message. Exceeding 64 characters or use of dashes is not recommended. + + + + + + + + Airline-assigned unique Offer identifier. + + + + + Airline designator of the owner/ assigner of the Offer ID, typically used for offer ordering purposes. Example: UA, BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Code + + + + + The POA OrderID should only go to the ORA, not back to the seller. +1. ORA +2. POA + + + + + Indicator to specify if the offer relates to requested date. For example in calendar search, this indicator will be set to 'true' if this airline offer is for a requested date and will not be present (or will be set to 'false' if airline offer is for another date than requested one. + + + + + + + When "true", the Reprice had no effect on the price(s) of the original Order/OrderItems. + + + + + + Reshop Fees(s) and Penalty(s). + + + + + Payment information. + + + + + + Payment detail, including association(s). + + + + + + + + Commission information. + + + + + + + + Order Action. Examples: Cancel, Create, Update, Delete, Reissue, Reprice + + + + + + + Action Type Context. + + + + + + + + + + + + + + Data Lists(s). + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Enumeration: + +CarryOn +Checked + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + + + + + + Description Details + + + + + + + + + + + + List of Flight Segments + + + + + + + + + + List of Flight elements. + + + + + + Journey information describing the travel between an airport/city where travel commences and an airport/city where travel ultimately terminates. A journey may be comprised of one or more segments. Note: This node will be renamed to journey in future releases. + + + + + + Flight journey information. + + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + + + A globally unique identifier for this Flight instance. Example: flight1 + + + + + + + + + + List of Origin/Destination elements. + + + + + + + + + + + + + Price Class list. + + + + + + + + + + Description and characteristics of a Service + + + + + + + + + + + + + + Seat information by aircraft section. + + + + + + + + + + Description value. + + + + + + + + + + + + Mark-up Style. Example: HTML + + + + + + LINK to Description information source. + + + + + Description-associated Media Object(s). + + + + + + Description-associated MEDIA OBJECT ID or Key. Example: IMG1 + + + + + Description-associated MEDIA LINK. + + + + + Description-associated Media Attachment ID. Example: ATT1. + + + + + + + + + + + Images and/or links for the entire section defined by the range of rows. + + + + + + + + + + Refers to aircraft seat characteristics; seat option codes. Examples: E (EXIT ROW), M (Middle Seat), A (Aisle seat), L (Left side of aircraft), Q (Bulk Head). Refer to PADIS code list 9825. + + + + + Associated Keyword Unit of Measure, if relevant. Example: INCH + + + + + Lowest Width Measurement value for this section. Example: 20 + + + + + Lowest Pitch Measurement value for this section. Example: 32 + + + + + Seat Description Key-Value Word Pairs. +Examples: +ReclineDegree - 25 +BedLengthLowEnd - 68 +BedLengthHighEnd - 78 +WidthLowEnd - 20 +WidthHighEnd - 21.5 +PitchLowEnd - 32 +PitchHighEnd - 34.4 + + + + + + + Key-Value detail. + + + + + + + + + + + + + + + + + + Metadata List(s). + + + + + + + + + + + + + + + Transaction Processing Results, including processing status, alerts, business warnings, supplemental marketing messages and policy. + + + + + Metadata definition. + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Response Message Processing. + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OrderRetrieveRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderRetrieveRQ.xsd new file mode 100644 index 00000000..be16fa55 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderRetrieveRQ.xsd @@ -0,0 +1,513 @@ + + + + + + + + The OrderRetrieve/ OrderView transaction set retrieves a specified order that matches one or more search criteria. + +Search criteria may include any supported Order Reference information, which may be the Order ID, a PNR reference, a ticket or coupon/ document number, or other Airline supported order reference and a Traveler Surname and Given Name. + +Note that if the order retrieval request is initiated from the party that originally requested the order creation, then an Order Reference is sufficient with the identity of the requesting party. + +If the order retrieval request is initiated from a party that did not originally request the order creation, then an extended security mechanism may be used to extend order view access to the party (e.g. using a CustomerInputRQ/RS for an additional security challenge (e.g. custom security question and answers.) + +The requestor may additionally specify filters to constrain the response information sets, including: Trip itinerary, Flight segment, Passenger, Payment and Accountable document information. If no filters are specified, all order information is returned. + +If a matching order is found, the OrderView response will contain all order information or filtered information (if filters were requested in the order retrieval request.) If no matching Order is located, the OrderView response will include processing condition information and no order information. + + + + + + + + + + Order Retrieve Query. + + + + + + Query Filters. + + + + + + + Flight Filters. + + + + + + + + Flight origin/ destination information. + + + + + + Departure Airport. + + + + + + Departure Airport Location code. Example: TPA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Departure date. Example: 2017-01-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + + + + Arrival Airport. + + + + + + Arrival Airport Location code. Example: GVA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Arrival date. Example: 2017-01-14 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + + + + + + + + Flight segment information. + + + + + + Departure Airport. + + + + + + Departure Airport Location code. Example: TPA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Departure date. Example: 2017-01-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + + + + Arrival Airport. + + + + + + Arrival Airport Location code. Example: GVA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Arrival date. Example: 2017-01-14 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + + + + + + + + + + + Passenger and Group information. + + + + + + A single human being as distinct from a group, class, or family. + + + + + + Individual's first or given name. Example: JOHN. + + + + + Individual's middle name or initial. Examples: G, GEORGE + + + + + Individual's family name, last name. Example: SMITH. + + + + + + + + Passenger Profile ID + + + + + The account set up for a customer within a rewards program which holds funds on behalf of that customer. + + + + + + An enterprise operating aircraft for commercial purposes + + + + + Loyalty Program Name. Example: Miles and More + + + + + Loyalty Program ID: Example: MAM + + + + + Loyalty Program account number. Example: ABC123456 + + + + + Loyalty Program sign-in ID (or username). + + + + + + + + Form of identification. Typically used to identify that the passenger is who he says he is. + +This is the type of FOID as defined in AIRIMP (FF Number, Credit Card Number, etc.). + + + + + + Any document which may be used to identify a person or verify aspects of a person's personal identity. + + + + + Contact Information, within the context of one message. + + + + + + Classification for a particular set of contact information (e.g. Primary, Payment, etc.) + + + + + The address used for postal service. Examples are post office boxes address, postal physical address, postal code + + + + + The email address which should be used for contact purposes. + + + + + A telephone number is a sequence of digits assigned to a fixed-line telephone subscriber station connected to a telephone line or to a wireless electronic telephony device, such as a radio telephone or a mobile telephone, or to other devices for data transmission via the public switched telephone network (PSTN) or other private networks. + + + + + + Other Contact Method information. (i.e. social media handle, website, etc.) + + + + + + + + + + + Ticket document numbers. + + + + + + Coupon Document Number. + +Note: This is the document number comprised of the airline code, form code, and serial number. + + + + + + + + + + + Date of Issue. Example: 2017-01-13 + + + + + Airport or City Code. Example: JFK + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + Applicable coupon number. Example: 1234 + + + + + + + + + + + + + + Group Information. + + + + + + Group Name. Example: ABC Tour Club + + + + + The Complete Party (TCP) indicating total party size. Example: 12 + + + + + + + + + Payment information. + + + + + + Payment Method detail. + + + + + + Credit card issuer code. Example: MC + +Note: This is the 2 character code of the credit card issuer. + + + + + Concealed credit card number, Example: xxxxxxxxxxxx9922 + + + + + + + + + + + + Tokenized card number. + +Note: This capability may not be supported by all EDIST-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of this capability is not dictated by this specification. + + + + + Payment Card Effective and/ or Expiration date(s). + + + + + + Payment Card Effective Date. Example: 0116 + + + + + Payment Card Expiration Date. Example: 0119 + + + + + + + + + Name of credit card holder. Example: JOHN SMITH + + + + + + + + + + + + + + + + + + + Existing Booking Reference (e.g. PNR Record Locator). Example: R1A3SK + + + + + + + + + + + + + + + Parameters that influence overall message results. + +Note: These capabilities may not be supported by all EDIST-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Message Parameters. + + + + + + + + Object association(s) between this object and any other object or metadata instance(s). + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OrderRulesRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderRulesRQ.xsd new file mode 100644 index 00000000..1d3c74fc --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderRulesRQ.xsd @@ -0,0 +1,63 @@ + + + + + + + + The OrderRules transaction set requests the rules, change and penalty fees applicable to a specified order. + + + + + + + + + + Order Rules Query. + + + + + + + Existing Booking Reference (e.g. PNR Record Locator). Example: R1A3SK + + + + + + + + + + + + Parameters that influence overall message results. + +Note: These capabilities may not be supported by all EDIST-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Message Parameters. + + + + + + + Object association(s) between this object and any other object or metadata instance(s). + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OrderRulesRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderRulesRS.xsd new file mode 100644 index 00000000..0b4cd501 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderRulesRS.xsd @@ -0,0 +1,83 @@ + + + + + + + + The OrderRules transaction set requests the rules, change and penalty fees applicable to a specified order. + + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + Query Results. + + + + + + Transaction Processing Results, including processing status, alerts, notices, business warnings, supplemental marketing messages and policy. + + + + + Order Rules. + + + + + + + + + + + + + + + + + + + + + Transaction Processing Results, including processing status, alerts, business warnings, supplemental marketing messages and policy. + + + + + Response Message Processing. + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/OrderViewRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderViewRS.xsd new file mode 100644 index 00000000..ea6aa29f --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/OrderViewRS.xsd @@ -0,0 +1,663 @@ + + + + + + + + The OrderCreate/ OrderView transaction is a multi-function message that may: + +1) Request specified inventory to be held (and returns a reference to the held inventory) + +2) Request that an order to be created (returning the complete view of the Order) + +3) Request additions to order data elements (e.g. add frequent flyer data) + + + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + Query Results. + + + + + + Transaction Processing Results, including processing status, alerts, notices, business warnings, supplemental marketing messages and policy. + + + + + Group Information. + + + + + Order information. + + + + + + + + Order Item Detail. + + + + + + + + + + Ticket/ Document Information. + + + + + + Ticket/document information. + + + + + + Booking and Servicing Agent information. + + + + + + + + + + + + Fare Tax information. + + + + + + + + + + + + + + Commission information. + + + + + Order Amendment information. + + + + + + Amendment Detail. + + + + + + Amendement Action Type. Examples: Add, Change, Delete, Reissue, Reprice + + + + + + + Action Type Context. + + + + + + + + + Offer Item ID with optional Service ID(s). + + + + + + + + + Passenger(s)/ Group associated with the Offer Item. + +Note: This contains references to Passenger and Group instance(s) defined in the Passengers node. + + + + + + Association to multiple Passenger instance(s). Example: pax1 pax2 + + + + + + + + + Associated Optional Service(s). + + + + + + + Passenger(s)/ Group associated with the Offer Item. + +Note: This contains references to Passenger and Group instance(s) defined in the Passengers node. + + + + + + Association to multiple Passenger instance(s). Example: pax1 pax2 + + + + + + + + + + + + Other Named Association(s). + +Note: Includes an association type choice (e.g. MediaGroup) and an instance association value (e.g. mediagrp1). + + + + + Named Instance Association Type. Examples: CarryOnAllowance, MediaGroup + + + + + Associated object instance value. +Example: mediagrp1 + + + + + + + + + + + + Ticket/document information. + + + + + + Booking and Servicing Agent information. + + + + + + + + + + + + + + Passenger(s)/ Group associated with the Offer Item. + +Note: This contains references to Passenger and Group instance(s) defined in the Passengers node. + + + + + + Association to multiple Passenger instance(s). Example: pax1 pax2 + + + + + + + + + + + + + + + + + + Data Lists(s). + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Enumeration: + +CarryOn +Checked + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + + + + + + Description Details + + + + + + + + + + + + List of Flight Segments + + + + + + + + + + List of Flight elements. + + + + + + Journey information describing the travel between an airport/city where travel commences and an airport/city where travel ultimately terminates. A journey may be comprised of one or more segments. Note: This node will be renamed to journey in future releases. + + + + + + Flight journey information. + + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + + + A globally unique identifier for this Flight instance. Example: flight1 + + + + + + + + + + List of Origin/Destination elements. + + + + + + + + + + + + + Price Class list. + + + + + + + + + + Description and characteristics of a Service + + + + + + + + + + + + + + Seat information by aircraft section. + + + + + + + + + + Description value. + + + + + + + + + + + + Mark-up Style. Example: HTML + + + + + + LINK to Description information source. + + + + + Description-associated Media Object(s). + + + + + + Description-associated MEDIA OBJECT ID or Key. Example: IMG1 + + + + + Description-associated MEDIA LINK. + + + + + Description-associated Media Attachment ID. Example: ATT1. + + + + + + + + + + + Images and/or links for the entire section defined by the range of rows. + + + + + + + + + + Refers to aircraft seat characteristics; seat option codes. Examples: E (EXIT ROW), M (Middle Seat), A (Aisle seat), L (Left side of aircraft), Q (Bulk Head). Refer to PADIS code list 9825. + + + + + Associated Keyword Unit of Measure, if relevant. Example: INCH + + + + + Lowest Width Measurement value for this section. Example: 20 + + + + + Lowest Pitch Measurement value for this section. Example: 32 + + + + + Seat Description Key-Value Word Pairs. +Examples: +ReclineDegree - 25 +BedLengthLowEnd - 68 +BedLengthHighEnd - 78 +WidthLowEnd - 20 +WidthHighEnd - 21.5 +PitchLowEnd - 32 +PitchHighEnd - 34.4 + + + + + + + Key-Value detail. + + + + + + + + + + + + + + + + + + Metadata List(s). + + + + + + + + + + + + + + + Transaction Processing Results, including processing status, alerts, business warnings, supplemental marketing messages and policy. + + + + + Metadata definition. + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Response Message Processing. + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/SeatAvailabilityRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/SeatAvailabilityRQ.xsd new file mode 100644 index 00000000..c9a731db --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/SeatAvailabilityRQ.xsd @@ -0,0 +1,709 @@ + + + + + + + + The SeatAvailability transaction set returns data used to construct respective seat maps with fully integrated fees for any identified premium seats. + +The message also returns multi-media content at the message level with media content references at the individual service level. + + + + + + + + + Parameters that influence overall message results. + +Note: These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Traveler requested qualifiers to influence search results, e.g. offers and/ or offer pricing. + +Notes: +1. Included Existing Orders, Payment Card, Programs, Promotions, Seat, Service, Social Media, Special Fare, Special Needs, Trip Purpose. + +2. These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. + + + + + Choice between entering: +1) Cached Shopping Offer IDs +2) Detailed Query Parameters + + + + + Core Service Price query parameters. + + + + + + FlighSegment information. Contains details flight segment information. + + + + + + + + + + Reservation Booking Designator. If absent, defaults to all classes of service. + + + + + + Class of Service Code. Example: B + + + + + + + + + + Fare basis code. Example: Y26CH + + + + + + + + + + + Offer Details. + + + + + + Reference to the segment for which seat maps are required. Absence of this element is equivalent to an all-segments request + + + + + Reference to the passenger for which seat maps are required. Absence of this element is equivalent to an all-passengers request + + + + + + Reference to the OfferID of the selected Offer (either a standard Offer or an a-la-carte Offer) returned in a previous shopping response. + + + + + Designator of Airline that owns/ assigned these IDs. Examples: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Code + + + + + Reference to unique shopping session response ID, as provided in the airline's previous shopping response. + + + + + + + + + + + Reference to the passenger for which seat maps are required. Absence of this element out is equivalent to an all-passengers request + + + + + Reference to the segment for which seat maps are required. Absence of this element out is equivalent to an all-segments request + + + + + + The airline-assigned unique Order ID. Example: ORDER-c98c-4759-a20b + + + + + Airline Designator of airline that owns/ assigned this ID. Example: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Codes + + + + + + + + + + + + + Existing Flight Itinerary Information. + + + + + Data Lists(s). + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Enumeration: + +CarryOn +Checked + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + + + + + + Description Details + + + + + + + + + + + + List of Flight Segments + + + + + + + + + + List of Flight elements. + + + + + + Journey information describing the travel between an airport/city where travel commences and an airport/city where travel ultimately terminates. A journey may be comprised of one or more segments. Note: This node will be renamed to journey in future releases. + + + + + + Flight journey information. + + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + + + A globally unique identifier for this Flight instance. Example: flight1 + + + + + + + + + + List of Origin/Destination elements. + + + + + + + + + + + + + Price Class list. + + + + + + + + + + Description and characteristics of a Service + + + + + + + + + + + + + + Seat information by aircraft section. + + + + + + + + + + Description value. + + + + + + + + + + + + Mark-up Style. Example: HTML + + + + + + LINK to Description information source. + + + + + Description-associated Media Object(s). + + + + + + Description-associated MEDIA OBJECT ID or Key. Example: IMG1 + + + + + Description-associated MEDIA LINK. + + + + + Description-associated Media Attachment ID. Example: ATT1. + + + + + + + + + + + Images and/or links for the entire section defined by the range of rows. + + + + + + + + + + Refers to aircraft seat characteristics; seat option codes. Examples: E (EXIT ROW), M (Middle Seat), A (Aisle seat), L (Left side of aircraft), Q (Bulk Head). Refer to PADIS code list 9825. + + + + + Associated Keyword Unit of Measure, if relevant. Example: INCH + + + + + Lowest Width Measurement value for this section. Example: 20 + + + + + Lowest Pitch Measurement value for this section. Example: 32 + + + + + Seat Description Key-Value Word Pairs. +Examples: +ReclineDegree - 25 +BedLengthLowEnd - 68 +BedLengthHighEnd - 78 +WidthLowEnd - 20 +WidthHighEnd - 21.5 +PitchLowEnd - 32 +PitchHighEnd - 34.4 + + + + + + + Key-Value detail. + + + + + + + + + + + + + + + + + + Metadata List(s). + + + + + Message Policy information. + + + + + + + + + Seat Availability Request Parameters definition. + + + + + + + Inventory guarantee for Offers in search results. + + + + + + When true, inventory guarantee is requested for applicable Optional Services. + +Note: This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of this capability is not dictated by this specification. + + + + + + + + Group and subgroup code(s) that specify the requested categories of Optional Services to be returned in the results. + + + + + + + + Service group and subgroup code(s). + + + + + + + + + + Pricing Parameters, including Simple Pricing, Award Travel, Auto Exchange, Override Currency and Fee Exemption. + + + + + + Requested override currency code for pricing. +Example: EUR + + + + + Fee exemption application for Offer pricing. + + + + + + + + Exemption(s) based on tax codes plus (optional) tax types within a tax code. + + + + + + Exempt tax code. +Example: YQ/YR + + + + + + + Airport code location for exempt ZP or XF taxes. +Example: MIA + For maximum interoperability, it is recommended that IATA (three character) Airport/ City Code values be used. Use an IATA code or a proprietary string value. + +http://www.iata.org/publications/Pages/code-search.aspx + + + + + + + + + Tax type(s) within the tax code. Examples: I, C + + + + + + + + + + Exempt province(s). + + + + + Entity name. + =notes=: +1. This must be provided for certain exemptions in the Canadian market. + + + + + + + + + + + When true, this request is to be handled by an auto-exchange process. + + + + + When true, award eligible in addition to priced offers and fares is requested. + + + + + When true, only award eligible offers/ fares are requested. + + + + + When true, Simple Pricing for flight offers is requested. + + + + + + + Group-related Offer Information. + + + + + + + + + + + + + + Seat Availability Request Metadata definition. + + + + + Shopping Query-Related Metadata. + + + + + + + + + + Passenger Metadata List(s). + + + + + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/SeatAvailabilityRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/SeatAvailabilityRS.xsd new file mode 100644 index 00000000..680f7558 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/SeatAvailabilityRS.xsd @@ -0,0 +1,1021 @@ + + + + + + + + The SeatAvailability transaction set returns data used to construct respective seat maps with fully integrated fees for any identified premium seats. + +The message also returns multi-media content at the message level with media content references at the individual service level. + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + + + Search Result Parameters that influence overall message results. + +Note: These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Container for standalone optional OfferItems. This supports the shopping basket concept. The main purpose of this structure is to reduce the size of the message by inserting Offer Items which are applicable to multiple flight-related Offers. + + + + + + + + One Service or Service Bundle which is priced per unit. A La Carte Offer Items are optional and variable quantities of these can be selected by any of the eligible passengers for the applicable segments and/or price classes. + + + + + + + + + + + + + + + Returns a list of cabins and the seats within it. + +When the Cabin Layout is returned, this information can be used by the Seller to render a graphical Seat Map. + + + + + + + + + + Flight slice on point. Example: TPA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + Flight slice off point. Example: LHR + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + + + + + + Cabin type. Examples: First Class, Business Class + +Encoding Scheme: PADIS codeset element 9873 - Cabin Class of Service + + + + + + Cabin class marketing name. Example: Premium Economy + + + + + Code value. Example: 003 + + + + + Code Definition. Example: Travel Agency + + + + + Code set table name. + + + + + Codeset location uri. Example: http://anysite.com/codeset + + + + + + + + Row detail. + + + + + + Seat column to identify a particular seat position on an aircraft + + + + + + + Column position in of the seat. +Example: A (AISLE SEAT) + +For maximum interoperability, refer to IATA PADIS Code List for data element 9825 - Seat Characteristic, Coded. + + + + + + + + + Contains rows and seat information for seat display purposes + + + + + + First row number. Example: 08 + + + + + + + + Last row number. Example: 44 + + + + + + + + + + + + + + Last row number. +Example: 16 + + + + + First row number. +Example: 5 + + + + + + + + + + + EXIT row detail. + + + + + + First row number. +Example: 15 + + + + + + + Specifies the exit row position in wide body Aircraft. + + + + + + + + + Last row number. +Example: 16 + + + + + + + Specifies the exit row position in wide body Aircraft. + + + + + + + + + Exit row position. +Examples: +B (Back) +C (Center section) +F (Front) +FB (Front and Back) +FMB (Front, Middle and Back) +L (Left side section) +LC (Left center section) +R (Right side section) +RC (Right center section) + +Encoding Scheme: IATA PADIS Code List for data element 3227 - Place/Location Qualifier + + + + + + + + + + + + + + Non-Seat Cabin Component information. + + + + + + Cabin component. +Examples: +701 (Movable compartment divider) +702 (Convertible seats) +AR (Air phone) +BA (Bar) +BK (Bulkhead) +CL (Closet) +G (Galley) +LA (Lavatory) +LG (Luggage storage) +MV (Movie screen) +SO (Storage space) +ST (Stairs to upper deck) +TA (Table) + +Encoding Scheme: IATA PADIS Code List for data element 9978 - Cabin Facilities Characteristic + + + + + Physicaly location of the cabin component + + + + + + A range of rows covered by a non-seat cabin component for seat map information + + + + + + First row occupied by this item. Example: 13 + + + + + Last row occupied by this item. Example: 17 + + + + + Location of the component relative to the row position defined (use values 'Before' or 'After'). + + + + + All columns covered on the map by this item. + + + + + Orientation of Component in cabin row. + +Examples: +1 Back +2 Front +3 Front and back +4 Front, middle and back +C Center Section +L Left side section +LC Left center section +R Right side section +RC Right center section + +Encoding Scheme: IATA PADIS code list 3227 + + + + + + + + + + + Seat Dimensions. + +Note: Defines the size of this item in actual measurement units or defines how much space in relation to rows and columns the space of this item actually consumes. + + + + + + Component size by number of rows (length) and number of columns (width). + + + + Length in number of ROWS value. Example: 2.5 + + + + + Width in number of COLUMNS value. Example: 2.5 + + + + + + Actual component size information. + + + + + + First row number. +Example: 15 + + + + + Front to back LENGTH measurement value. Example: 70 + + + + + Front to back WIDTH measurement value. Example: 70 + + + + + + + + + + + + + + Seat row, containing individual Seat instances. + + + + + + Seat row number. Example: 2 + + + + + Seat characteristic following PADIS codeset 9864. + + + + + + Row characteristic. Use only if all seats within this row share the same characteristics. + +Examples: +A (Extra Leg Room) +B (Buffer Row) +MV (Row With Movie Screen) + +Encoding Scheme: IATA PADIS Code List for data element 9864 - Row Characteristic + + + + + + + + Seat column to identify a particular seat position on an aircraft + + + + + + + Seat status. + +Encoding Scheme: IATA PADIS Code List for data element 9865 - Seat Occupation + + + + + Seat characteristic following PADIS codeset 9825. + + + + + + Refers to aircraft seat characteristics; seat option codes. Examples: E (EXIT ROW), M (Middle Seat), A (Aisle seat), L (Left side of aircraft), Q (Bulk Head). Refer to PADIS code list 9825. + +This Code may be further described in the SeatCharacteristicsList in DataLists. + + + + + + + + Reference to the price point applicable to this individual seat. Multiple seats can reference the same OfferItem. + + + + + Assign additional propoerties of this seat instance by referencing a SeatDefinition (in DataLists). + + + + + + + + + + + + When true, this seat is on the upper deck. + + + + + + + + + + Metadata List(s). + + + + + Data Lists(s). + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Enumeration: + +CarryOn +Checked + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + + + + + + Description Details + + + + + + + + + + + + List of Flight Segments + + + + + + + + + + List of Flight elements. + + + + + + Journey information describing the travel between an airport/city where travel commences and an airport/city where travel ultimately terminates. A journey may be comprised of one or more segments. Note: This node will be renamed to journey in future releases. + + + + + + Flight journey information. + + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + + + A globally unique identifier for this Flight instance. Example: flight1 + + + + + + + + + + List of Origin/Destination elements. + + + + + + + + + + + + + Price Class list. + + + + + + + + + + Description and characteristics of a Service + + + + + + + + + + + + + + Seat information by aircraft section. + + + + + + + + + + Description value. + + + + + + + + + + + + Mark-up Style. Example: HTML + + + + + + LINK to Description information source. + + + + + Description-associated Media Object(s). + + + + + + Description-associated MEDIA OBJECT ID or Key. Example: IMG1 + + + + + Description-associated MEDIA LINK. + + + + + Description-associated Media Attachment ID. Example: ATT1. + + + + + + + + + + + Images and/or links for the entire section defined by the range of rows. + + + + + + + + + + Refers to aircraft seat characteristics; seat option codes. Examples: E (EXIT ROW), M (Middle Seat), A (Aisle seat), L (Left side of aircraft), Q (Bulk Head). Refer to PADIS code list 9825. + + + + + Associated Keyword Unit of Measure, if relevant. Example: INCH + + + + + Lowest Width Measurement value for this section. Example: 20 + + + + + Lowest Pitch Measurement value for this section. Example: 32 + + + + + Seat Description Key-Value Word Pairs. +Examples: +ReclineDegree - 25 +BedLengthLowEnd - 68 +BedLengthHighEnd - 78 +WidthLowEnd - 20 +WidthHighEnd - 21.5 +PitchLowEnd - 32 +PitchHighEnd - 34.4 + + + + + + + Key-Value detail. + + + + + + + + + + + + + + + + + + Message Policy information. + + + + + + + + + + + + + Seat Availability Response Message Parameters. + + + + + + + Pricing Parameters, including Simple Pricing, Award Travel, Auto Exchange, Override Currency and Fee Exemption. + + + + + + Requested override currency code for pricing. +Example: EUR + + + + + Fee exemption application for Offer pricing. + + + + + + + + Exemption(s) based on tax codes plus (optional) tax types within a tax code. + + + + + + Exempt tax code. +Example: YQ/YR + + + + + + + Airport code location for exempt ZP or XF taxes. +Example: MIA + For maximum interoperability, it is recommended that IATA (three character) Airport/ City Code values be used. Use an IATA code or a proprietary string value. + +http://www.iata.org/publications/Pages/code-search.aspx + + + + + + + + + Tax type(s) within the tax code. +Examples: I, C + + + + + + + + + + Exempt province(s). + + + + + Entity name. + =notes=: +1. This must be provided for certain exemptions in the Canadian market. + + + + + + + + + + + When true, fare information for one or more Offer Items has been returned from an auto-exchanging application. + + + + + When true, award eligible in addition to priced offers and fares is requested. + + + + + When true, only award eligible offers/ fares have been returned. + + + + + When true, Simple Pricing for flight offers has been applied. + + + + + + + Inventory Guarantee information, including Inventory Guarantee Time Limit, Unique ID and Offer/ Offer Item association(s). + +Notes: +1. This is the time that inventory for a specified product offer is guaranteed as available. The inventory held must be converted into a completed order before the time limit expires otherwise the guarantee is lost. +2. If specified, an association to one or more Offers or Offer Items may be specified in the Associations node. If no associations are specified, the inventory guarantee is assumed to apply to the entire Offer. +3. This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of this capability is not dictated by this specification. + + + + + Group-related Offer Information. + + + + + + + + + + + + + + Seat Availability Response Metadata definition. + + + + + Shopping Query-Related Metadata. + + + + + + + + + + Passenger Metadata List(s). + + + + + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/ServiceListRQ.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/ServiceListRQ.xsd new file mode 100644 index 00000000..ae8f94ca --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/ServiceListRQ.xsd @@ -0,0 +1,370 @@ + + + + + + + + The ServiceList transaction set returns a list of all applicable ancillary services that meet request qualifiers and flights. + +The message supports shopping for additional a la carte services to compliment any selected offer, as well as shopping for specialty service items not generally included in an initial offer but rather based on service search filters, e.g. sports equipment specialty baggage and unaccompanied minor fees. + +The message also returns multi-media content at the message level and media references at the individual service level. + + + + + + + + + Parameters that influence overall message results. + +Note: These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Choice between entering: +1) Cached Shopping Offer IDs +2) Detailed Query Parameters + + + + + Core Service List query parameters. + + + + + + Origin and Destination. + + + + + + + + + + + Airline Offers. + + + + + + Offer Details. + + + + + + Globally unique Offer instance ID. It is not recommended to exceed 64, and it is not recommended to use dashes. Example: QWASZXERDFCVTYGHBNUIJKNMF67D5F9GHR567SWER41SD458F9456FMDIRTN34DF + + + + + Offer items. + + + + + + + + + + + + + + + + + + + + + + Existing Flight Itinerary Information. + + + + + + Common NDC Data List choices. + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + + + Metadata List(s). + + + + + + + + + + Message Policy information. + + + + + + + + + Service List Request Message Parameters. + + + + + + + Inventory guarantee for Offers in search results. + + + + + + When true, inventory guarantee is requested for applicable Optional Services. + +Note: This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of this capability is not dictated by this specification. + + + + + + + + Group and subgroup code(s) that specify the requested categories of Optional Services to be returned in the results. + + + + + + + + Service group and subgroup code(s). + + + + + + + + + + Pricing Parameters, including Simple Pricing, Award Travel, Auto Exchange, Override Currency and Fee Exemption. + + + + + + Requested override currency code for pricing. +Example: EUR + + + + + Fee exemption application for Offer pricing. + + + + + + + + Exemption(s) based on tax codes plus (optional) tax types within a tax code. + + + + + + Exempt tax code. +Example: YQ/YR + + + + + + + Airport code location for exempt ZP or XF taxes. +Example: MIA + For maximum interoperability, it is recommended that IATA (three character) Airport/ City Code values be used. Use an IATA code or a proprietary string value. + +http://www.iata.org/publications/Pages/code-search.aspx + + + + + + + + + Tax type(s) within the tax code. Examples: I, C + + + + + + + + + + Exempt province(s). + + + + + Entity name. + =notes=: +1. This must be provided for certain exemptions in the Canadian market. + + + + + + + + + + + When true, this request is to be handled by an auto-exchange process. + + + + + When true, award eligible in addition to priced offers and fares is requested. + + + + + When true, only award eligible offers/ fares are requested. + + + + + When true, Simple Pricing for flight offers is requested. + + + + + + + Group-related Offer Information. + + + + + + + + + + + + + + Service List Request Metadata definition. + + + + + Shopping Query-Related Metadata. + + + + + + + + + + Passenger Metadata List(s). + + + + + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/ServiceListRS.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/ServiceListRS.xsd new file mode 100644 index 00000000..d89c0d8d --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/ServiceListRS.xsd @@ -0,0 +1,619 @@ + + + + + + + + The ServiceList transaction set returns a list of all applicable ancillary services that meet request qualifiers and flights. + +The message supports shopping for additional a la carte services to compliment any selected offer, as well as shopping for specialty service items not generally included in an initial offer but rather based on service search filters, e.g. sports equipment specialty baggage and unaccompanied minor fees. + +The message also returns multi-media content at the message level and media references at the individual service level. + + + + + + + + The presence of the empty Success element explicitly indicates that the message succeeded. + + + + + Used in conjunction with the Success element to define one or more business errors. + + + + + Transaction Processing Results, including processing supplemental marketing messages. + + + + + Offer Expiration Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +Notes: +1. This is the time within which offers must be converted into completed Orders. + +2. On expiry, a new shopping transaction is required. + +3. This time limit is at the OFFER-LEVEL and will apply to all (child) Offer Items. + + + + + + + Offer Time Limit object instance id and metadata instance(s) association. + + + + + + + + + + Container for standalone optional OfferItems. This supports the shopping basket concept. The main purpose of this structure is to reduce the size of the message by inserting Offer Items which are applicable to multiple flight-related Offers. + + + + + + + + One Service or Service Bundle which is priced per unit. A La Carte Offer Items are optional and variable quantities of these can be selected by any of the eligible passengers for the applicable segments and/or price classes. + + + + + + + + + + Search Result Parameters that influence overall message results. + +Note: These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Metadata List(s). + + + + + + + + + + Message Policy information. + + + + + Data Lists(s). + + + + + + Passenger data list definition. + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. + + + + + + + + Contact data list definition. + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Enumeration: + +CarryOn +Checked + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + + + + + + Description Details + + + + + + + + + + + + List of Flight Segments + + + + + + + + + + List of Flight elements. + + + + + + Journey information describing the travel between an airport/city where travel commences and an airport/city where travel ultimately terminates. A journey may be comprised of one or more segments. Note: This node will be renamed to journey in future releases. + + + + + + Flight journey information. + + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + + + A globally unique identifier for this Flight instance. Example: flight1 + + + + + + + + + + List of Origin/Destination elements. + + + + + + + + + + + + + Price Class list. + + + + + + + + + + Description and characteristics of a Service + + + + + + + + + + + + + + Seat information by aircraft section. + + + + + + + + + + Description value. + + + + + + + + + + + + Mark-up Style. Example: HTML + + + + + + LINK to Description information source. + + + + + Description-associated Media Object(s). + + + + + + Description-associated MEDIA OBJECT ID or Key. Example: IMG1 + + + + + Description-associated MEDIA LINK. + + + + + Description-associated Media Attachment ID. Example: ATT1. + + + + + + + + + + + Images and/or links for the entire section defined by the range of rows. + + + + + + + + + + Refers to aircraft seat characteristics; seat option codes. Examples: E (EXIT ROW), M (Middle Seat), A (Aisle seat), L (Left side of aircraft), Q (Bulk Head). Refer to PADIS code list 9825. + + + + + Associated Keyword Unit of Measure, if relevant. Example: INCH + + + + + Lowest Width Measurement value for this section. Example: 20 + + + + + Lowest Pitch Measurement value for this section. Example: 32 + + + + + Seat Description Key-Value Word Pairs. +Examples: +ReclineDegree - 25 +BedLengthLowEnd - 68 +BedLengthHighEnd - 78 +WidthLowEnd - 20 +WidthHighEnd - 21.5 +PitchLowEnd - 32 +PitchHighEnd - 34.4 + + + + + + + Key-Value detail. + + + + + + + + + + + + + + + + + + + + + + + + + + Service List Response Message Parameters. + + + + + + + Pricing Parameters, including Simple Pricing, Award Travel, Auto Exchange, Override Currency and Fee Exemption. + + + + + + Requested override currency code for pricing. +Example: EUR + + + + + Fee exemption application for Offer pricing. + + + + + + + + Exemption(s) based on tax codes plus (optional) tax types within a tax code. + + + + + + Exempt tax code. +Example: YQ/YR + + + + + + + Airport code location for exempt ZP or XF taxes. +Example: MIA + For maximum interoperability, it is recommended that IATA (three character) Airport/ City Code values be used. Use an IATA code or a proprietary string value. + +http://www.iata.org/publications/Pages/code-search.aspx + + + + + + + + + Tax type(s) within the tax code. +Examples: I, C + + + + + + + + + + Exempt province(s). + + + + + Entity name. + =notes=: +1. This must be provided for certain exemptions in the Canadian market. + + + + + + + + + + + When true, fare information for one or more Offer Items has been returned from an auto-exchanging application. + + + + + When true, award eligible in addition to priced offers and fares is requested. + + + + + When true, only award eligible offers/ fares have been returned. + + + + + When true, Simple Pricing for flight offers has been applied. + + + + + + + Inventory Guarantee information, including Inventory Guarantee Time Limit, Unique ID and Offer/ Offer Item association(s). + +Notes: +1. This is the time that inventory for a specified product offer is guaranteed as available. The inventory held must be converted into a completed order before the time limit expires otherwise the guarantee is lost. +2. If specified, an association to one or more Offers or Offer Items may be specified in the Associations node. If no associations are specified, the inventory guarantee is assumed to apply to the entire Offer. +3. This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of this capability is not dictated by this specification. + + + + + Group-related Offer Information. + + + + + + + + + + + + + + Service List Response Metadata definition. + + + + + Shopping Query-Related Metadata. + + + + + + + + + + Passenger Metadata List(s). + + + + + + + + + + Other Metadata Lists(s). + + + + + + Other Metadata List. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/aidm_commontypes.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/aidm_commontypes.xsd new file mode 100644 index 00000000..8ed1f274 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/aidm_commontypes.xsd @@ -0,0 +1,814 @@ + + + + + AIRLINE means: an enterprise operating aircraft for commercial purposes which (i) performs scheduled or non-scheduled air transport services, or both, which are available to the public for carriage of passengers, mail and/or cargo and (ii) is certified for such purposes by the civil aviation authority of the state in which it is established. + + + + + Issuing Airline Name. Example: British Airways + + + + + Airline code assigned to a carrier. Either ICAO-defined 3-character code or IATA-defined 2-character code. Refer to IATA Airline Coding Directory, Section 3. + + + + + + + A code is a character string of letters, numbers, special characters (except escape sequences), and symbols. It represents a definitive +value, a method, or a property description in an abbreviated or language-independent form that is part of a finite list of allowed values. + + + + + + + + + + + Two or more airlines participating in a commercial relationship or joint venture, where a joint and commonly identifiable product is marketed under a single commercial name or brand. + + + + + Used to specify the alliance based on PADIS Code List (code list defined in BDT). + + + + + Alliance information URL. +Example: http://www.oneworld.com/home + + + + + An enterprise operating aircraft for commercial purposes + + + + + + + Specifies the content value(s) for the alliance code BDT based on PADIS Code List. + + + + + + Additional BDT to specify alliance codes. + + + + + + + + Text is a character string such as a finite set of characters generally in the form of words of a language. + + + + + + + + + The electronic or geographic address which a party has provided as the contact channel. For example, contact email, contact postal address, contact phone number. + + + + + Classification for a particular set of contact information (e.g. Primary, Payment, etc.) + + + + + The address used for postal service. Examples are post office boxes address, postal physical address, postal code + + + + + + + + + The email address which should be used for contact purposes. + + + + + A telephone number is a sequence of digits assigned to a fixed-line telephone subscriber station connected to a telephone line or to a wireless electronic telephony device, such as a radio telephone or a mobile telephone, or to other devices for data transmission via the public switched telephone network (PSTN) or other private networks. + + + + + + + + + The presence of the empty ContactNotProvided element indicates that the passenger refused to provide contact information. + + + + + + Other Contact Method information. (i.e. social media handle, website, etc.) + + + + + + Reference to Individual instance(s) + + + + + A single human being as distinct from a group, class, or family. + + + + + + + + Uniquely Identifies a set of Contact Information, within the context of one message. + + + + + + A code is a character string of letters, numbers, special characters (except escape sequences), and symbols. It represents a definitive +value, a method, or a property description in an abbreviated or language-independent form that is part of a finite list of allowed values. + + + + + + A code is a character string of letters, numbers, special characters (except escape sequences), and symbols. It represents a definitive +value, a method, or a property description in an abbreviated or language-independent form that is part of a finite list of allowed values. + + + + + + + + A date is a Gregorian calendar representation in various common resolutions: year, month, week, day. + + + + + + The email address which should be used for contact purposes. + + + + + Used to differentiate multiple email addresses of one contact. + + + + + The email address which should be used for contact purposes. + + + + + + + Form of identification. Typically used to identify that the passenger is who he says he is. + +This is the type of FOID as defined in AIRIMP (FF Number, Credit Card Number, etc.). + + + + + The CC vendor code in case FOID is a Credit Card. + + + + + FOID ID value. Example: NY122345 + + + + + Form of identification type code used for booking/ticketing. Examples: PP (passport), CC (credit card), FF (frequent flyer), DL (drivers license) + + + + + + + Specifies the content value(s) for the gender code BDT. + + + + + + + + + + Additional BDT to specify Gender code list. + + + + + + A code is a character string of letters. It represents the type a passenger like ADT(Adult). + + + + + + Any document which may be used to identify a person or verify aspects of a person's personal identity. If issued in a small, standard credit card size form, it is usually called an identity card. Some countries issue formal identity documents, while others may require identity verification using informal documents. When the identity document incorporates a person's photograph, it may be called photo ID. + +In the absence of a formal identity document, a driver's license may be accepted in many countries for identity verification. Most countries accept passports as a form of identification. + + + + + Uniquely identifies the document from all other identity documents issued by the state or organization. e.g. passport number, drive license number. + + + + + The type of passenger document. +Examples: PT (Passport) + + + + + Issuing country code of the identity document. + + + + + Citizenship Country Code. Examples: US, FR. + + + + + Residence Country Code. Examples: US, FR. + + + + + The date the identity document was issued. + + + + + The date the identity document expires. + + + + + Holder’s date of birth as written on the document. + + + + + Holder's birth location (e.g. city and/or country) as written on the document. + + + + + Holder’s gender as specified on the document (M, F, or X for unspecified). + + + + + Holder's name title as written on the document. Examples: MR, MRS, DRn. + + + + + Holder's first or given name, as written on the document. Example: JOHN. + + + + + Holder's middle name or initial, as written on the document. Examples: G, GEORGE + + + + + Holder's family name, last name as written on the document. Example: SMITH. + + + + + Holder's surname suffixes and letters as written on the document. Examples: Jr., Sr., III, Ret., Esq. + + + + + An official entry in a Passport or other Travel Document made by an official of a government to indicate that the bearer has been granted authority to enter or re-enter the country or region concerned. + + + + + + + A code is a character string of letters, numbers, special characters (except escape sequences), and symbols. It represents a definitive +value, a method, or a property description in an abbreviated or language-independent form that is part of a finite list of allowed values. + + + + + + An indicator is a list of two mutually exclusive Boolean values that express the only possible states of a property. + + + + + + A single human being as distinct from a group, class, or family. + + + + + Individual's birth location (e.g. city and/or country). + + + + + Country Code where the Passenger was born (ISO 3166). For example: DE + + + + + Gender of the individual (M, F, or X for unspecified). + + + + + Individual's name title. Examples: MR, MRS, DRn. + + + + + Individual's first or given name. Example: JOHN. + + + + + Individual's middle name or initial. Examples: G, GEORGE + + + + + Individual's family name, last name. Example: SMITH. + + + + + Individual's surname suffixes and letters. Examples: Jr., Sr., III, Ret., Esq. + + + + + + Uniquely Identifies an Individual within the context of one message. + + + + + + A code is a character string of latters , number, special characters (except escape sequences) , and symbols. It represents a definitive value, a method or a property description in an abbreviated or language-independent form that is part of a finite list of allowed values. + + + + + + 2 character country code as defined in ISO3166 + + + + + + Language Code representation. + + + + + Language Code representation. + +Notes: +1. Language code. Example: en, en-US +2. Encoding Schemes: ISO 639-1 Code OR Microsoft National Language Support (NLS) Code +3. Supports ISO 639-1 (two alpha character) neutral language encoding indicated by a name such as "en" for English. +4. Supports MNLS geographically specific language encoding indicated by a name that includes both locale and country/region information. For example, the locale English (United States) has the language name "en-US" + + + + + Written or Spoken language. + + + + + + + An account set up for a customer within a rewards program which holds funds on behalf of that customer. + + + + + Two or more airlines participating in a commercial relationship or joint venture. + + + + + + An enterprise operating aircraft for commercial purposes + + + + + Non-airline loyalty program provider name. + + + + + + Loyalty Program Name. Example: Miles and More + + + + + Loyalty Program ID: Example: MAM + + + + + Loyalty Program account number. Example: ABC123456 + + + + + Loyalty Program information URL. Example: https://www.britishairways.com/en-gb/executive-club/about-the-club + + + + + Loyalty Program sign-in ID (or username). + + + + + Loyalty Program tier code. + + + + + Loyalty Program tier name. + + + + + Loyalty Program account priority within the tier (e.g. Platinum, executive, etc.) + + + + + + + A measure is a numeric value determined by measuring an object along with the specified unit of measure. + + + + + + The type of unit of measure. + + + + + + + + A mathematical number that is assigned or is determined by calculation. + + + + + + Other Contact Method information. (i.e. social media handle, website, etc.) + + + + + Used to differentiate multiple Other Addresses of one contact. (i.e. social media handle, website, etc.) + + + + + Other Contact Method Value. Example: www.marketingsite.com + + + + + + + Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship. Holds the attributes specific to a one booking, from shopping to fulfilment. + + + + + Type code applying to the Passenger which typically drives pricing (e.g. ADT, CHD, etc). + + + + + + The Age of the Passenger. To be used in NDC Anonymous Shopping requests or when the birthdate (in Individual) is not known. + + + + + The Date of Birth of the Passenger. Anonymous Shopping requests or when the birthdate (in Individual) is not known. + + + + + + Residence Country Code. Examples: US, FR. + + + + + Citizenship Country Code. Examples: US, FR. + + + + + A single human being as distinct from a group, class, or family. + + + + + Passenger Profile ID + + + + + An account set up for a customer within a rewards program which holds funds on behalf of that customer. + + + + + Form of identification. Typically used to identify that the passenger is who he says he is. + +This is the type of FOID as defined in AIRIMP (FF Number, Credit Card Number, etc.). + + + + + + Any document which may be used to identify a person or verify aspects of a person's personal identity. + + + + + Reference to Contact Information, within the context of one message. + + + + + Reference to Passenger instance within the context of one message, associating an infant on lap to this adult passenger. + + + + + Language Code representation. + + + + + Additional, supplementary information about the document or service. + + + + + + + + + + + Uniquely identifies a Passenger within the context of one message. + + + + + When true, passenger authorizes the airline to share his/her profile information or send promotional emails. + + + + + + A telephone number is a sequence of digits assigned to a fixed-line telephone subscriber station connected to a telephone line or to a wireless electronic telephony device, such as a radio telephone or a mobile telephone, or to other devices for data transmission via the public switched telephone network (PSTN) or other private networks. + + + + + Used to differentiate multiple Phone numbers of one contact. +Examples: Work, Home, Mobile + + + + + Numeric telephone dialing prefixes for the member countries of the International Telecommunication Union (ITU). + + + + + Phone number area code. Example: 813 + + + + + Phone number text. +Eg: +1 999-999-9999 ext 1234, +617-9976 +Note: This may be a simple, un-structured phone number, such as +01 999-999-9999 ext 1234 or combined with the additional attributes to create a structured phone number. + + + + + Phone extension number. Example: 1234 + + + + + + + The address used for postal service. Examples are post office boxes address, postal physical address, postal code + + + + + Used to differentiate multiple Postal Addresses of one contact. Examples: AddressAtOrigin or AddressAtDestination + + + + + Street name and number corresponding to the postal address. Examples: Main Street, 100 Main Street + + + + + Additional address information including building name, room, apartment, or suite number. + + + + + Post office box. Example: P.O. Box 21 + + + + + Postal code. Examples: 11001, 11001-2345 + + + + + The name, expressed as text, of the city, town or village. + + + + + The name, expressed as text, of the subdivision of a country. + + + + + The name, expressed as text, of the country. + + + + + ISO Country Code. Examples: US, FR. + + + + + + + A name is a word or a phrase that constitutes a distinctive designation of a person, place, thing or concept. + + + + + + + + + Additional, supplementary information about the document or service. + + + + + Additional, supplementary information about the document or service. + + + + + + When TRUE, this remark should be displayed. Notes: 1. This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specificat + + + + + Remark creation timestamp. + + + + + + An official entry in a Passport or other Travel Document made by an official of a government to indicate that the bearer has been granted authority to enter or re-enter the country or region concerned. + + + + + Visa ID value. Example: NY122345. + + + + + The type of visa. + + + + + ISO Country Code where the visa is valid. For example: DE + + + + + Date at which the VISA expires and is no longer a valid entry document. + + + + + Duration permitted of the Passenger's stay in the visa host country (in days). + + + + + Number of entries permitted by the visa into the host country. + + + + + + + An ordinal number is an assigned mathematical number that represents order or sequence. + + + + + + A short name is a word or a phrase that constitutes a distinctive designation of a person, place, thing or concept. + + + + + + + + + A code is a character string of letters, numbers, special characters (except escape sequences), and symbols. It represents a definitive +value, a method, or a property description in an abbreviated or language-independent form that is part of a finite list of allowed values. + + + + + + A name is a word or phrase that constitutes the distinctive designation of a person, place, thing or concept + + + + + + + + + A string of characters used to identify a resource. Such identification enables interaction with representations of the resource over a network, typically the World Wide Web, using specific protocols. + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/edist_commontypes.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/edist_commontypes.xsd new file mode 100644 index 00000000..f98b16e6 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/edist_commontypes.xsd @@ -0,0 +1,24449 @@ + + + + EDIST XML SPECIFICATION: Common XML Objects shared by all EDIST Domains. + + + + + + Address representation choice. + + + + + + + + + + + Core Address Information. + + + + + CORE ADDRESS representation. + + + + + Address. + + + + + + + + + + + + + + + Detailed Address Information. + + + + + DETAIL ADDRESS representation. + + + + + + + Specifies directions to a given address (I.e. to service fulfilment address, if other than an airport) + + + + + + + + + + + + + + PAYMENT ADDRESS. + + + + + PAYMENT ADDRESS representation. + +Note: This a "relaxed cardinality" representation of Structured Address to support various combinations of Address Verification fields. + + + + + Street. Examples: Main Street, 100 Main Street + + + + + Post office box. Example: P.O. Box 21 + + + + + Building name, room, apartment, or suite number. + + + + + City name. Example: Tampa + + + + + + + + + + State or province code or name. Examples: NY, New York + + + + + Postal code. Examples: 11001, 11001-2345 + + + + + Country name or code. +Examples: US, United States + +Encoding Scheme: ISO 3166-1 (two character) Country Code + + + + + + + + SIMPLE (non-structured) ADDRESS. + + + + + SIMPLE ADDRESS representation. + + + + + Address line text. +Example: +100 Main Street +New York, NY 10100 + + + + + + + + + + + + + STRUCTURED ADDRESS. + + + + + STRUCTURED ADDRESS representation. + + + + + AddressAtOrigin or AddressAtDestination + + + + + + + + + + + Street. Examples: Main Street, 100 Main Street + + + + + Building name, room, apartment, or suite number. + + + + + Post office box. Example: P.O. Box 21 + + + + + City (e.g., Dublin), town, or postal station (i.e., a postal service territory, often used in a military address). + + + + + State or province code. Examples: NY, QUE + + + + + Postal code. Examples: 11001, 11001-2345 + + + + + + + + + + + County that the address is located in. Example: Litchfield + + + + + + + + + + Airport or a city code. Use a three letter location identifier assigned according to the IATA Resolution 763. Refer to IATA Airline Coding Directory . Example: TPA + + + + + + + + + + + + + + S5 Record Attributes information. + + + + + + S5 record attributes definition. + ENCODING: Note, Attributes on the Services Record S5 that can be used as filter criteria for a service. + + + + + Service group information. + + + + + + Service Group code. + +BD (BUNDLED SERVICE) +BG (BAGGAGE) +IE (IN-FLIGHT ENTERTAINMENT) +LG (LOUNGE) + + + + + + Service group description. +Example: BAGGAGE OPTIONS + + + + + + + + Service subgroup information. + + + + + + Service Sub-Group Code(s). + +Group BG: CT (Container), PP (Pre-Paid Excess Baggage) +Group IE: IT (Internet Access), TV (Television) + + ENCODING: Note, Standard Group and Sub Group on the Services Record S5 that can be used as filter criteria for a service. + + + + + + Service subgroup description. +Example: CARRY ON HAND BAGGAGE + + + + + + + + Description 1 codes. + ENCODING: Note, standard Description codes (or text translation for these codes) on the Optional Services Record S5. + + + + + + Description code. +Example: 05 (UP TO 5 KG) + =sample values= +05 = up to 5 kg +1Y = One Year +AI = Aisle +B1 = First Bag + + + + + Description code text. +Example: UP TO 5 KG + + + + + + + + Description 2 codes. + ENCODING: Note, standard Description codes (or text translation for these codes) on the Optional Services Record S5. + + + + + + Description code. +Example: HT (HOT) + + + + + Description code text. +Example: HOT + + + + + + + + + + + + + Carry-on and checked baggage allowances. + + + + + The allowable baggage types and max number. + + + + + The permitted baggage types by RFISC for the applicable baggage allowance. + + + + + The maximum numberof this baggage type. + + + + + + + The charge amount for different baggage types + + + + + The baggage charge type by RFISC for the applicable baggage charge. + + + + + The baggage charge amount which is applied to the 1st and 2nd checked bag. + + + + + The currency code for payment of a baggage charge. Use ISO 4217, three alpha code. + + + + + + + The determining carrier code and the max number for each type of carry-on allowable baggage. + + + + + The determining carrier code of the carry-on allowance baggage type. + + + + + The permitted baggage type by RFISC for the carry-on baggage allowance. + + + + + The maximum number of each allowable baggage type. + + + + + + + The carry on chargeable baggage information. + + + + + + Specifies the embargo information. + + + + + The embargo information + + + + + + + + The permitted baggage type by RFISC for the carry-on baggage allowance. + + + + + The baggage charge amount which is applied to the 1st and 2nd checked bag. + + + + + The currency code for payment of a baggage charge. Use ISO 4217, three alpha code. + + + + + The maximum linear dimensions of the baqggage follwed by centimeters 'C' or inches 'I'. + + + + + The maximum baggage weight followed by kilos 'K' or pounds 'L'. + + + + + + + The maximum bag dimensions and weight for free carry on baggage. + + + + + The maximum linear dimensions of the baqggage follwed by centimeters 'C' or inches 'I'. + + + + + The maximum baggage weight followed by kilos 'K' or pounds 'L'. + + + + + + + The maximum bag dimensions and weight for free checked baggage. + + + + + The maximum linear dimensions of the baqggage follwed by centimeters 'C' or inches 'I'. + + + + + The maximum baggage weight followed by kilos 'K' or pounds 'L'. + + + + + + + The checked chargeable baggage information. + + + + + + Specifies the embargo information. + + + + + The embargo information + + + + + + + + The permitted baggage type by RFISC for the checked baggage allowance. + + + + + The baggage charge amount which is applied to the 1st and 2nd checked bag. + + + + + The currency code for payment of a baggage charge. Use ISO 4217, three alpha code. + + + + + The maximum linear dimensions of the baqggage follwed by centimeters 'C' or inches 'I'. + + + + + The maximum baggage weight followed by kilos 'K' or pounds 'L'. + + + + + + + + The maximum linear dimensions of the baqggage follwed by centimeters 'C' or inches 'I'. + + + + + + A data type for Baggage Allowance by Description. + + + + + Baggage weight restriction application. Examples: Party, Traveler + +Note: Party applies to all Travelers. + + + + + Applicable bag type. +Examples: Carry-On, 1st Checked Bag, 2nd Checked Bag + + + + + + + + Defines the value type. Refer to PADIS Codeset 5463 + + + + + + A data type for Baggage Allowance by Dimensions. + + + + + Baggage weight restriction application. Examples: Party, Traveler + +Note: Party applies to all Travelers. + + + + + Baggage dimension UOM (unit of measure). Example: Centimeter, Inch + + + + + A choice between specifying baggage dimensions as: +- Total linear dimensions +- Individual length, height and/ or width + + + + + Maximum linear dimensions value. Example: 62 + +Notes: +1. Linear measurement = length + width + height +2. Size unit of measure is specified in BagUOM. + + + + + + + + + + + + Minimum linear dimensions value. Example: 20 + +Notes: +1. Linear measurement = length + width + height +2. Size unit of measure is specified in BagUOM. + + + + + + + + + + + + + Maximum baggage dimension category and value. + +Notes: Baggage Size UOM (unit of measure) is specified in BagUOM. + + + + + + Baggage dimensions category. +Examples: Length, Height, Width + + + + + Maximum dimension value. Example: 30 + + + + + Minimum dimension value. Example: 10 + + + + + + + + + + Applicable bag type. +Examples: Carry-On, 1st Checked Bag, 2nd Checked Bag + + + + + + + + + A data type for Baggage Allowance by Piece. + + + + + Baggage weight restriction application. Examples: Party, Traveler + +Note: Party applies to all Travelers. + + + + + Maximum pieces. +Example: 4 + + + + + Type of Bag,. +Example: Golf Equipment, Bag, Fishing, Car Seat + + + + + Applicable bag type. +Examples: Carry-On, 1st Checked Bag, 2nd Checked Bag + + + + + + Provides information on per piece weight and dimensions. + + + + + + BAGGAGE WEIGHT allowance per baggage piece. + + + + + BAGGAGE DIMENSION allowance per baggage piece. + + + + + + Quantity of pieces with these measurements. + + + + + + + + Provides logical combiinaton between allowances pieces. Enumaration with OR and AND as posisble values. + + + + + + + + + + + + + A data type for Baggage Allowance by Weight. + + + + + Baggage weight restriction application. Examples: Party, Traveler + +Note: Party applies to all Travelers. + + + + + Maximum weight value and unit of measure. + + + + + + Maximum weight value. Example: 50 + + + + + Baggage weight unit of measure. + +Encoding Scheme: IATA Padis Codeset - List for data element 6411 + + + + + + + + + + Applicable bag type. +Examples: Carry-On, 1st Checked Bag, 2nd Checked Bag + + + + + + + + + A data type for US Department of Transportation (DOT) Reservation or Disclosure baggage rule. + Select a value from the enumerated list or enter a string value. +=enumerated values= +N = NOT SUBJECT TO US DOT RESERVATION OR DISCLOSURE +Y = SUBJECT TO US DOT RESERVATION AND DISCLOSURE +D = SUBJECT TO DISCLOSURE BUT NOT TO US DOT RESERVATION + + + + + US Department of Transportation (DOT) Reservation or Disclosure baggage rule. +Examples: Y, Disclosure AND US DOT Reservation + + + + + + + + + + + DESCRIPTION of Allowance with application information. + + + + + CARRY-ON ALLOWANCE definition. + + + + + Carry-On Allowance detail. + + + + + + + Defines the maximum number of each allowable baggage type. + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + In concert with BaggageDeterminingCarrier data field, specifies the reason for the carrier code. + +Encoding Scheme: IATA PADIS Code List for data element RES. + + + + + + + + + + + Carry-on Allowance. + + + + + + + + + + CHECKED BAG ALLOWANCE defiition. + + + + + Checked Bag Allowance detail. + + + + + + + Defines the maximum number of each allowable baggage type. + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + In concert with BaggageDeterminingCarrier data field, specifies the reason for the carrier code. + +Encoding Scheme: IATA PADIS Code List for data element RES. + + + + + + + + + + + Checked Baggage Allowance. + + + + + + + + + + BAGGAGE DIMENSION Allowance with application information. + + + + + Defines the maximum number of each allowable baggage type. + + + + + + + + + + BAGGAGE WEIGHT Allowance with application information. + + + + + + + + + + + + + + + + Booking Reference information to include Record Locator, Assigning Airling Identifier, etc. + + + + + + + + + + Booking Reference information to include Record Locator, Assigning Airling Identifier, etc. + + + + + + Booking Reference detail. + + + + + + + + Booking Reference definition. + + + + + Booking Reference Type. Example: 6 (Passenger confirmation number) Encoding Scheme: IATA Padis Codeset - List for data element [1153] Reference Qualifier + + + + + + Existing Booking Reference ID. Example: R1A3SK + + + + + + + + + + + A two-character alpha-numeric code assigned according to the IATA Resolution 762 or a three-letter airline designator assigned by ICAO. Refer to IATA Airline Coding Directory. + + + + + + + + Name. Example: British Airways + + + + + + + + + Other Assigning Entity ID. Example: UID12345 Note: Entity Name may be specified in the @Name property. + + + + + + + + + Object association(s) between this object and any other object or metadata instance(s). + + + + + + + Object Metadata Association(s). Example: meta1 meta3 + + + + + + Entity Name. + + + + + + + + + + + + + + Airport or a city code. Use a three letter location identifier assigned according to the IATA Resolution 763. Refer to IATA Airline Coding Directory . +Example: TPA + + + + + + + + + + Airport or a city code. Use a three letter location identifier assigned according to the IATA Resolution 763. Refer to IATA Airline Coding Directory . +Example: TPA + + + + + + + + + + City (e.g., Dublin), town, or postal station (i.e., a postal service territory, often used in a military address). + + + + + + PADIS/ THIRD-PARTY CODESET definition. + NDC Capability Model: CODESET + +============ +Representation(s) +============ +• IATA PADIS Encoding +• Third-Pary Standard Encoding +• Implementer-Proprietary Encoding + +============ +Feature(s) +============ +• Code value, code definition and code table name may be specified +• URI to codeset information source may be specified +• Supports Language Localization (Alternate Language Values) +• Codeset Source Details (owner, location, etc.) may be specified + +============ +Metadata +============ +• Yes + + + + + Code value. Example: 003 + + + + + Code Definition. Example: Travel Agency + + + + + Code set table name. + + + + + Codeset location uri. Example: http://anysite.com/codeset + + + + + + + + + Address Contact. + + + + + ADDRESS CONTACT definition. + + + + + + + + Contact(s). + + + + + + Contact detail. + + + + + + + Email address details, including application (I.e. home, business, etc.). + + + + + + + Passenger Name information. + +Note: Detailed Name information, such as prefix, title and suffix, are specified in PassengerMetadata. + + + + + + Family name, last name + +Example: SMITH + + + + + + + + + + + + Given name, first name or names + + + + + + + + + + + + Name Title. Examples: MR, MRS, DR + + + + + Surname Suffixes and / or Letters, Examples:Jr., Sr., III., Ret., Esq., Ph.D., M.D. + + + + + Middle name or initial. Examples: G, GEORGE + + + + + + + + + + + + + + + + + Type of contact. For e.g. Primary or Emergency contact. + + + + + + + + + + CONTACT CORE definition. + + + + + + EMAIL ADDRESS helper object. + + + + + Email address application. Examples: Personal, Business, SMS + + + + + The traveler email address for contact. + + + + + + + + + + + + + Email address details, including application (I.e. home, business, etc.). + + + + + Email Address representation. + + + + + + + + + + Phone Contact. + + + + + Provides telephone information, and allows to specify telephone number application (ie Home, Business, etc.). May be used for a simle, unstrucutured number, or, in combination with child attributes allows to create a structured telephone number (ie Country Code number, Area Code numbers, etc.) + + + + + PHONE CONTACT definition. + + + + + + + + PHONE NUMBER helper object. + + + + + Phone number application. Examples: Billing, Business, Home, Mobile + + + + + Phone number text. +Examples: ++01 999-999-9999 ext 1234, +617-9976 + +Note: This may be a simple, un-structured phone number, such as +01 999-999-9999 ext 1234 or combined with child attributes to create a structured phone number. + + + + + + + + Phone number country code. Examples: 1, 01, +1 + + + + + Phone number area code. Example: 813 + + + + + Phone extension number. Examples: 1234, ext 1234 + + + + + + + + + + + + Other Contact Method. + + + + + OTHER CONTACT METHOD definition. + + + + + + + Contact method name. Example: Marketing Website + + + + + Method value. Example: www.marketingsite.com + + + + + Named contact group. Example: John Smith Business + + + + + + + + + + Commission information. + + + + + A data type for Core Commission. + + + + + Choice between specifying +amount value or percentage. + + + + Commission amount. Example: 20.00 USD + + + + + Commission percentage. Example: 20 + + + + + + Commission code. Example: 1000, BFST + + + + + + + + + + Country Code. Examples: US, FR + +Encoding Scheme: ISO 3166-1 (two character) Country Code + + + + + + + + + + COUNTRY CODE representation. + +Notes: +1. Examples: US, FR +2. Encoding Scheme: ISO 3166-1 (two character) Country Code + + + + + + + + + + COUNTRY RADIUS QUERY definition. + + + + + Country Code(s). + + + + + + Country Code. Examples: US, FR + +Encoding Scheme: ISO 3166-1 (two character) Country Code + + + + + + + + Keyword/ Value Search Criteria. + +Notes: This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of this capability is not dictated by this specification. + + + + + + + + + + COUNTRY PROXIMITY representation. + +Notes: This contains either the requested maximum distance search radius values -or- the actual Proximity information, which is typically used to specify the results from the named location radius search. + + + + + + + + + COUNTRY PROXIMITY representation. + +Notes: +1. This contains either the requested maximum distance search radius values -or- the actual Proximity information, which is typically used to specify the results from the named location radius search. + + + + + + + Country Code. Examples: US, FR + +Encoding Scheme: ISO 3166-1 (two character) Country Code + + + + + + + + + + Currency amount. Example: 10000, 100.00, 100 + + + + + Currency code. Example: USD + +Encoding Scheme: ISO 4217 (three alpha character) Currency Code + + + + + + + A globally unique identifier for this object instance. + + + + + Association(s) between this object and any metadata instance(s). + + + + + Object association(s) between this object and any object instance(s). + + + + + Currency code Application. +Examples: Actual, Display, Requested, Conversion, Other + + + + + Decimal position in fare amount. Example: 2 + + + + + + + + + A data type for ISO Currency Code. + +Currency code. Example: USD + +Encoding Scheme: ISO 4217 (three alpha character) Currency Code + + + + + + + + + + A data type for Currency Amount with Mandatory Currency Encoding. + + + + + + + + + + + AMOUNT with OPTIONAL CURRENCY ENCODING representation. + + + + + + + In some markets, commission is VAT-able (ie Taxable) + + + + + + + + Monetary value amount and currency code. + + + + + + Description(s). + + + + + + + + Description detail. + + + + + + + + + + + + + + Association to Description element in DataList. Example: DE1 DE2 + + + + + + DESCRIPTION definition. + NDC Capability Model: Descriptions + +REPRESENTATIONS +============ +• Source URL +• Plain Text +• Marked-Up Text +• Rich Media Object ID and/ or URL to Source (e.g. images and streaming video) +============ +==== +Feature(s) + +a) Rendering Instructions, for converting an attachment into a specified display format, may be included with Media Attachments. +3. Metadata: Yes + +2. Rendering Instructions, for converting an attachment into a specified display format, may be included with Media Attachments. + +3. These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of this capability is not dictated by this specification. + + + + + + Description value. + + + + + + + + + + + + Mark-up Style. Example: HTML + + + + + + LINK to Description information source. + + + + + Description-associated Media Object(s). + + + + + + Description-associated MEDIA OBJECT ID or Key. Example: IMG1 + + + + + Description-associated MEDIA LINK. + + + + + Description-associated Media Attachment ID. Example: ATT1. + + + + + + + + + + Object globally unique Instance ID. Example: obj1 + + + + + + + UNIQUE MEDIA ID representation. + +Unique Media ID. Example: IMG215 + + + + + + + + Media Link (to media source.) + + + + + + + + + + + + MEDIA ATTACHMENT representation. + + + + + + Attachment Uniform Resource Identifier (URI). + + + + + + + + + + + + Attachment Description. + + + + + MIME Type of binary content embedded in FileContent element or referenced by AttachmentURI element, eg. "application/pdf" or "image/png" + + + + + The size of the Attachment in kilobytes. Example: 60 + + + + + Rendered Media Instructions. + + + + + Base 64 binary content. + + + + + + + + A data type for a set of rendering instructions for converting XML data in a designated element into a specified display format or instructions to display a pre-rendered version of the data. + + + + + Rendering Method. Example: Narrative, XSLT, Other + + + + + An identifier for a file format or content type of the rendered output. + + + + + + + + + + Rendering Attachment URI, e.g. for a stylesheet. + + + + + + + + + + Attachment Size Value. Example: 57KB + + + + + Rendering Instruction Parameters. + +Notes: This is typically used for XSLT. + + + + + + + + + + An overview of the rendering method or style. + + + + + + + + + + + + + A data type for a Rendering Parameter, typically for XSLT. + + + + + Rendering Instruction Parameter detail. + + + + + + Rendering Parameter Name. + + + + + Rendering Parameter Value. + + + + + + + + + + + + + + + + + Directions. + + + + + + + + + + Directions detail. + + + + + DIRECTIONS definition. + NDC Capability Model: Directions + +1. Representation(s): URL to source; Plain Text +2. Association(s): Airport, City, x, x and y +3. Feature(s): From/To Context; Named Collection +3. Metadata: Yes + + + + + + Text-based Directions. + + + + + + + + + + Directions source URL. + + + + + + Directions name. Example: Directions to Headquarters + + + + + Directions from location. Example: City Center + + + + + Directions to location. Example: Headquarters + + + + + + + + + Disclosure(s). + + + + + + + + + + Disclosure(s). + + + + + Plain Text or Rich Media Disclosure Description(s). + + + + + + + + + Discount monetary value amount and currency value. + + + + + Discount percentage value. + + + + + DISCOUNT core representation. + +This element is used for informational purposes only and the Total Price already reflects and includes this discount amount/percent. + NDC Capability: Discount + +1. Discount amount value may be represented as a fixed amount or a percentage. +2. Contextual discount application (e.g. category) may be specified. +3. Metadata may be defined. + + + + + + + Discount Application. Example: BAG + + + + + Discount Description. + + + + + + + + + Traveler FQTV ACCOUNT definition. + + + + + FQTV Program Sponsoring Airline. Example: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Code + + + + + Traveler FQTV Account information. + + + + + + Traveler FQTV program sign in (or user) ID. + + + + + + + + + + + + FQTV account number. +Example: FQTV123456 + + + + + + + + + + + + Frequent flyer tier status. Example: "Altitude Elite 100K" + + + + + + + + + The Program ID will be used to specify Frequent Flyer Program. This will be the name of the program + + + + + + + + + Instant purchase type. +Examples: +CC (Ticketless purchase immediately charged to credit card) +NO (Not an instant purchase) +TT (Simultaneous with time of ticketing) + +Encoding scheme: IATA PADIS Codeset IPT - Instant Purchase Type + + + + + + Keyword/ Value Pair Detail. + + + + + + + + + + KEYWORD/ VALUE PAIR object. + + + + + Key Word. Example: SKYC + + + + + + + + + + Key-Word Value(s). Example: SkyCouch + + + + + + + + + + + + + + Language code. Example: en, en-US + +Encoding Schemes: ISO 639-1 Code OR Microsoft National Language Support (NLS) Code + +Notes: +1. Supports ISO 639-1 (two alpha character) neutral language encoding indicated by a name such as "en" for English. + +2. Supports MNLS geographically specific language encoding indicated by a name that includes both locale and country/region information. For example, the locale English (United States) has the language name "en-US". + + + + + Language(s). + + + + + + + + + + Language Code representation. + +Notes: +1. Language code. Example: en, en-US + +2. Encoding Schemes: ISO 639-1 Code OR Microsoft National Language Support (NLS) Code + +3. Supports ISO 639-1 (two alpha character) neutral language encoding indicated by a name such as "en" for English. + +4. Supports MNLS geographically specific language encoding indicated by a name that includes both locale and country/region information. For example, the locale English (United States) has the language name "en-US". + NDC Capability Model: LANGUAGE ENCODING + +============ +Representation(s) +============ +• ISO 639-1 encoding +• Microsoft MNLS geographically specific language encoding + +============ +Feature(s) +============ +• Supports ISO 639-1 (two alpha character) neutral language encoding indicated by a name such as "en" for English. + +• Supports MNLS geographically specific language encoding indicated by a name that includes both locale and country/region information. For example, the locale English (United States) has the language name "en-US". + +• Language application (e.g. usage context) may be specified (Display, Requested, Spoken, Written, etc.) + +============ +Metadata +============ +• LanguageMetadata + + + + + + + + + + + Message Property Path and Tag Name information. + + + + + NODEPATH helper object. + + + + + Message property location. + +Note: This is typically specified in xpath notation. + + + + + + + + + + + Message property tag name. + + + + + + + + + + + + + Bank Account information. + + + + + BANK ACCOUNT Payment Form definition. + +Customer bank accounts for payments, either for paper checks or electronic funds transfer. + + + + + Account Name. Example: JOHN SMITH + +Note: This is the name the bank account is held under. + + + + + + + + + + + + Routing Number. Example: 0260-0959-3 + +Note: This is the code assigned by authorities to financial institutions; sometimes called bank routing number. + + + + + + + + + + + + Account Type. Examples: Checking, Savings, Investment + + + + + Purchaser bank account number. Example: 067014822 + + + + + + + + + + + + + + + When true, checks are accepted. + + + + + + Used to indicate payment in cash. + + + + + When true, payment is being made in cash. + + + + + + + Check (Cheque) Payment + + + + + + Cheque number + + + + + Cheque signed date + + + + + Name of the Payee + + + + + + + + Direct Billing Arrangement information. + + + + + DIRECT BILLING Payment Form definition. + +Company name and location for sending invoice for remittances for travel services. + + + + + Direct billing Organizaqtion ID. Example: IBM + + + + + Remit to Company Name. Example: IBM + +Note: This is the company name to whom remittance should be directed. + + + + + Direct Billing Contact Name. Example: J THOMAS + + + + + Address where remittance should be directed. + + + + + + + + + + + + + + + Loyalty Redemption Arrangement information. + + + + + + The quantity of loyalty units being redeemed. Example: 15000 + + + + + Loyalty Certificates to be Redeemed. + + + + + + The loyalty redemption certificate number. + + + + + + + + + + + + + + + An individual airline identifier assigned to a passenger who is a member of an airline's Frequent Flyer Program. + + + + + + + + + + + + Promotion Code. + +Note: Promotion code is the identifier used by the host to link directly with a specific named advertising campaign. By including the required code, the client is able to gain access to special offers which may have been created for a specifically targeted group via a CRM system or for a wider advertising campaign using Television or press adverts. + + + + + List of vendor codes associated with the promotion. + + + + + + + + + Miscellaneous Charge Order (MCO) information. + + + + + + The ticket number of the miscellaneous charge order (MCO). + + + + + + + + Other Form of Payment information. + + + + + + + + + + Payment Card. + + + + + PAYMENT CARD definition. + + + + + Magnetic striped card type. + + + + + Credit card issuer code. Example: MC + +Note: This is the 2 character code of the credit card issuer. + + + + + The Credit Card Number embossed on the card. Example: 1111222233334444 + + + + + + + + + + + + Debit card issue number + + + + + Verification Digits. Example: 123 + +Note: This is the verification digits printed on the card following the embossed number. This may also accommodate the customer identification/batch number (CID), card verification value (CVV2 ), card validation code number (CVC2) on credit card. + + + + + + + + + + + + Name of credit card holder. Example: JOHN SMITH + + + + + + + + + + + + Credit card issuing company. + + + + + + Issuer Name. Example: Bank of America + +Note: This is the name of bank or organization issuing the card (e.g., alumni association, bank, fraternal organization, etc.). + + + + + + + + Cardholder Address. + + + + + + + + + + Concealed credit card number, Example: xxxxxxxxxxxx9922 + + + + + + + + + + + + Authorized credit card amount. Example: 500 USD + + + + + Surcharge Amount + + + + + + Authorized credit card amount. Example: 500 USD + + + + + + + + + Payment Card Effective and/ or Expiration date(s). + + + + + + Payment Card Effective Date. Example: 0116 + + + + + Payment Card Expiration Date. Example: 0119 + + + + + + + + + AVS Response Code. Example: Y (Street address and 5-digit ZIP code both match) + +Note: This is the address verification response code (AVS) when the ticketing agency performs address verification. + + + + + Tokenized card number. + +Note: This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of this capability is not dictated by this specification. + + + + + Approval Code Method. Example: M (Manual) + +Note: This is used to specify how the approval code for a credit card sale was obtained. + +Encoding Scheme: IATA PADIS Code List for data element 9890. + + + + + + + + Information relating to prepayment vouchers. + + + + + + Voucher ID or Number. Example: XX12345 + + + + + Voucher Effective and/ or Expiration date(s). + + + + + + Voucher Effective Date. Example: 2017-01-13 + + + + + Voucher Expiration date. Example: 2017-06-13 + + + + + + + + Passenger Name information. + +Note: Detailed Name information, such as prefix, title and suffix, are specified in PassengerMetadata. + + + + + + Family name, last name + +Example: SMITH + + + + + + + + + + + + Given name, first name or names + + + + + + + + + + + + Name Title. Examples: MR, MRS, DR + + + + + Surname Suffixes and / or Letters, Examples:Jr., Sr., III., Ret., Esq., Ph.D., M.D. + + + + + Middle name or initial. Examples: G, GEORGE + + + + + + + + + + + + + + + + + + + + Penalty Information. + + + + + PENALTY definition. + NDC Capability Model: PENALTY + +============ +Representation(s) +============ +• Core Penalty +• Detail Penalty + +============ +Feature(s) +============ +• Penalty Indicators (Cancellation fees apply; Change of Itinerary fees apply; Refundable ticket and/ or fare; Reusable ticket and/ or fare; Upgrade fee applies) +• Applicable Fee Remarks +• Penalty Type (Cancellation, No Show, Upgrade, etc.) +• Penalty Application (IATA Padis Codeset FAT - Fare or Application Penalty Type) +• Penalty Amount, represented as percentage or fixed value, with Amount Application (MinimumPenaltyAmount, MaximumPenaltyAmount, Other) and Applicable Fee Remarks + +============ +Metadata +============ +• PenaltyMetadata + + + + + Applicable Fee Remark(s). + + + + + + + + + + Penalty Conditions and Penalty Amount detailed information. + + + + + + Penalty detail. + + + + + + Penalty Type. +Examples: Cancellation, Change, NoShow, Upgrade, Other + + + + + Penalty application type. + +Encoding scheme: IATA Padis Codeset FAT - Fare or Application Penalty Type + + + + + Penalty Amount(s) with Penalty Amount Application and Remarks. + + + + + + Penalty Amount detail. + + + + + + + Penalty monetary value amount and currency code. + + + + + + + Penalty Amount Application. +Examples: MinimumPenaltyAmount, MaximumPenaltyAmount, Other + + + + + Applicable Fee Remark(s). + + + + + + + + + + + + + + + + + + + + + + + + When true, Cancellation fee(s) may apply. + + + + + When true, Change of Itinerary fee(s) may apply. + + + + + When true, this is a refundable ticket and/ or fare. + + + + + When true, this is a reusable ticket and/ or fare. + + + + + When true, Upgrade fee(s) may apply. + + + + + + Object globally unique Instance ID. Example: obj1 + + + + + + PENALTY DETAIL with Application, Description and Amount. + NDC Capability Model: PENALTY + +============ +Representation(s) +============ +• Core Penalty +• Detail Penalty + +============ +Feature(s) +============ +• Penalty indicators (xxxx) +• Free-Text Penalty Remarks + +============ +Metadata +============ +• PenaltyMetadata + + + + + + + + + Geocoding Location/ Position Metadata Associations. + + + + + + + + + + POSITION AND GEOCODING helper object. + + + + + Latitude value. Example: 49.9856 + + + + + + + Latitude sign. Example: SOUTH (South of Meridian) + + + + + + + + + + + Latitude degree minute value. Example: 45 + + + + + Latitude degree second value. Example: 30 + + + + + + + + + Longitude value. Example: 9.1220 + + + + + + + Longitude sign. Example: EAST (East of Meridian) + + + + + + + + + + + Longitude degree minute value. Example: 130 + + + + + Longitude degree second value. Example: 69 + + + + + + + + + Altitude value. Example: 9.1220 + + + + + + + Altitude unit of measure. +Example: Feet, Meters + + + + + Other altitude unit of measure context. Example: MyContext + + + + + + + + + Natural area geocode (NAC). Example: 8KDB PGFD + + + + + + + + + + + + + Geographical search radius. + + + + Search radius application. Example: Driving + + + + + A maximum search radius value, e.g. distance from specified location. Example: 20 + + + + + Distance unit of measure. Examples: Miles, Kilometers + + + + + + + Flight Price definition. + + + + + Total Base Fare Amount. Example: 200000 + +Note: This includes surcharges (if applicable). + + + + + Equivalent Base Fare Amount. Example: 200000 + + + + + Applicable Surcharge(s). + + + + + + Surcharge detail. + + + + + + + + Ticket Tax/fee/charge details to indicate taxes that apply to country of commencement of travel and routing. + + + + + + Individual fee/ surcharge information would appear on the accountable document. + + + + + + + + + + Total price + + + + + + + PARTIAL CURRENCY and AWARD Pricing Combination information. + + + + + + + + + + + + CORE PRICE definition. + + + + + When true, this price is approximate. + + + + + When true, all price amounts are refundable. + + + + + When true, price-associated tax(es) have been specified and included. + + + + + When true, price-associated fee(s)/ surcharge(s) have been specified and included in Price. + + + + + When true, pricing has been returned from an auto-exchanging application . + + + + + + + A (detailed) CURRENCY-based Price with Price Break-down for Tax and/ or Fee information. + + + + + AWARD (Redemption Unit-based) Pricing information. + + + + + AWARD/ REDEMPTION PRICE BASIS UNIT definition. + + + + + Redemption pricing. +Example: 15000 Miles + + + + + + + PARTIAL CURRENCY and AWARD Pricing Combination information. + + + + + COMBINATION PRICE BASIS UNIT: Partial currency and award. + + + + + Element outlining payment for frequent flyer redemption transaction where payment has been made partially with money and partially with frequent flyer miles or points. Monetry value followed by currency code, points or miles value followed by unit name. + + + + + + Currency Pricing information used in combination pricing scenarios (I.e. partial currency and partial airline redemption points) + + + + + + Monetary value amount and currency code. + + + + + + + + + Redemption amount and unit. +Example: 15000 Miles + + + + + + + + + + + COMBINATION PRICE BASIS UNIT: Partial currency and award. + + + + + Element outlining payment for frequent flyer redemption transaction where payment has been made partially with money and partially with frequent flyer miles or points. Monetry value followed by currency code, points or miles value followed by unit name. + + + + + + Currency Pricing information used in combination pricing scenarios (I.e. partial currency and partial airline redemption points) + + + + + + Monetary value amount and currency code. + + + + + + + + + Redemption amount and unit. +Example: 15000 Miles + + + + + + + + + + DETAIL CURRENCY PRICE BASIS UNIT: Price with tax and/ or fee break-down or totals. + + + + + + + + Total price in currency. Example: 16000 USD + +Note: This is the total price INCLUDING base price, taxes and fees/ surcharges. + + + + + Used instead of Total when price is not known (for example in case of BT/IT tickets). Example IT. + + + + + + Details all price break-down item subtotals, which exclude taxes, fees and charges. + + + + + + Price details. + +Note: This price does not include taxes and fee/ surcharges. + + + + + + Price breakdown sub-total. + +Note: This is the total of all price breakdown items, excluding tax and/ or surcharge. + + + + + Price application. Example: Base Fare + + + + + + + When true, this price amount is refundable. + + + + + + + + + + + Ticket Tax/fee/charge details to indicate taxes that apply to country of commencement of travel and routing. + + + + + + + + + + Individual fee/ surcharge information would appear on the accountable document. + + + + + + + + + + + + + + Monetary value amount and currency code. + + + + + PRICE with CURRENCY ENCODING definition. + + + + + + + + SIMPLE CURRENCY PRICE BASIS UNIT: NO price break-down, taxes and/or fees. + + + + + + + + A (simple) CURRENCY-based Price with NO taxes and/ or fees. +Examples: 100.00, 100, 100 (USD) + + + + + + + REDEMPTION helper object. + + + + + Frequent flyer program redemption unit. Example: Miles, Points + + + + + + + + + + + + Value containing the quantity of frequent flyer program redemption units. + + + + + Redemption amount/ unit equivalents. +Unit (Miles, Points) and Quantity (30000). Used on conjunction withNote: A currency value or conversion ratio may be specified. + + + + + + Currency equivalent of redemption amount. Example: 50000 + + + + + Redemption unit to currency ratio. Example: 2:1 (two redemption units = one currency unit.) + + + + + + + + + + + + + + + + + Penalty monetary value amount and currency code. + + + + + Percentage Value relating to acceptable the total amount by which the Order item price can vary; OR the amount of a penalty. + +Example: 20 USD, 2 Percent + + + + + + PROMOTION helper object. + + + + + Promotion code ID or number. Example: PROMO123. Used in conjunction with Link (Promotion URL), Issuer (Promotion Owner or Sponsor) and Remarks (Promotion remarks). + + + + + + + + + + + + Promotion url. Example: http://promos.site.com + + + + + Promotion Owner or Sponsor. +Used in conjunction with Code (Promotion code ID or number), Link (Promotion URL), and Remarks (Promotion remarks). + + + + + + A two-character alpha-numeric code assigned according to the IATA Resolution 762 or a three-letter airline designator assigned by ICAO. Refer to IATA Airline Coding Directory . + + + + + + + + + + + + This is the name of the person holding the voucher." + + + + + + + + + + + A data type for Baggage Detail Association. + + + + + + + + + + + LOCATION PROXIMITY definition. + +Note: This contains either the requested maximum distance search radius values -or- the actual Proximity information, which is typically used to specify the results from the named location radius search. + + + + + Proximity Data Application. Example: SearchRadius, ActualProximity, Other + + + + + The actual distance value from the named location search. Example: 20 + + + + + + + + + + Distance unit of measure. Examples: Miles, Kilometers + + + + + + + + + Remark(s). + + + + + REMARK helper object. + + + + + Remark Text. + + + + + + + When true, this remark should be displayed. + +Notes: +1. This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + Remark creation timestamp. Example: 2017-01-13T13:59:38Z + + + + + + + + + + + + + ORDER CREATION PRICE VARIANCE RULE definition. + + + + + Unique Rule ID. Example: RULE001 + + + + + Acceptable amount and/or percentage of the total amount by which the Order item price can vary. +Example: 20 USD, 2 Percent + + + + + + + + + + + Rule Name. Example: Acceptable Price variance + + + + + + + + + + Entity that owns/ assigned this Rule. Example: BA + +Note: If this is an airline, the IATA/ A4A (two or three character) Airline Designator Code should be used. + + + + + Rule Effective Period. + + + + + + + + + + + + + + + + + + + + + RULE SET definition. + + + + + Unique ID for a set of rules which was applied during transaction processing. Example: PRICERULE001 Note: Optional rule context and name may also be specified. + + + + + + + Rule Set Name. Example: Order Item Price Variance + + + + + + + + + + Rule Set Effective and Expiration Period. Notes: 1.If specified, this applies to all rules within the rule set. 2.Use a Rule Parameter to specify rule-level effective/ expiration periods, e.g.: (Name) EffectiveDate, (Value) 2015-01-15 + + + + + + + + + + + + + + + + + + + Entity that owns/ assigned this Rule Set. Example: BA Note: If this is an airline, the IATA/ A4A (two or three character) Airline Designator Code should be used. + + + + + + Rule(s). + + + + + + + + RULE definition. + + + + + Unique Rule ID. Example: RULE001 + + + + + Rule Value(s). + + + + + + Rule text value. + + + + + Implementer-defined rule values. + + + + + + + + Rule Name. Example: Acceptable Price variance + + + + + + + + + + Entity that owns/ assigned this Rule. Example: BA + +Note: If this is an airline, the IATA/ A4A (two or three character) Airline Designator Code should be used. + + + + + Rule Effective Period. + + + + + + + + + + + + + + + + + + + + + GENERIC/ IATA SPECIAL SERVICE definition. + + + + + Special service/ request code value. + +Example: UMNR (IATA passenger assistance SSR code) + +Encoding Scheme: Use of IATA Special Service Request (SSR) Code encoding is recommended. Any string value up to 15 characters in length is valid. + +Note: Although optional in the schema, some SSR codes may require associated description and description codes. + + + + + + + + + + Code description. Example: Unaccompanied Minor + + + + + + + + + + Description context. Examples: WEIGHT, NUMBER, PEDICURE + + + + + + + + + A collection of shopping session (message response) IDs, including the unique (master) Shopping Response ID, Offer IDs, Offer Item IDs and Service IDs. + +Notes: This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + Notes: +1. This capability supports reduced message payload sizes by providing a mechanism that supports references to cached Shopping Transactions and/ or Offer information so only object identifiers (e.g. Offer, Service) need to be exchanged in a subsequent Shopping request message, versus specifying the full object details. + +2. This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. The technical implementation of this capability is not dictated by this specification. + + + + + SHOPPING RESPONSE object definition. + + + + + Designator of Airline that owns/ assigned these IDs. Examples: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Code + + + + + Unique shopping session response ID. Example: 1F126AF1-7FCF-414F-8A3D-E4FFA408F747 + + + + + + + + + + + + + + + + State or Province Code representation. + + + + + + + + STATE/PROVINCE RADIUS QUERY representation. + NDC Capability Model: STATE OR PROVINCE QUERY + +============ +Feature(s) +============ +• Query by list of State/ Province Codes +• Query by list of State/ Province Keywords +• Preference Level for all or individual Query ParameterGroups +• Proximity information containing either the requested maximum distance search radius values, or the actual Proximity information (which is typically used to specify the results from the named location radius search.) + +============ +Metadata +============ +• Yes + + + + + State Code(s). + + + + + + State or Province Code. Example: NY + + + + + + + + + + + + + + + Keyword/ Value Search Criteria. + +Notes: +1. This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of this capability is not dictated by this specification. + + + + + + Keyword detail. + + + + + + + + + + + + + + + State Proximity. + +Notes: +1. This contains either the requested maximum distance search radius values -or- the actual Proximity information, which is typically used to specify the results from the named location radius search. + + + + + + + + STATE/PROVINCE PROXIMITY representation. + +Note: This contains either the requested maximum distance search radius values -or- the actual Proximity information, which is typically used to specify the results from the named location radius search. + + + + + + + State or Province Code. Example: NY + + + + + + + + + + + + + + + + + + A data type for a Fee/ Surcharge. + + + + Note: Fee/ surcharge information may be specified as: +- A total amount +- A total amount with associated breakdown + + + + Sub-total of all fees and charges. Monetary value and currency code. + + + + + + + When true, all fee/ surcharge amounts are refundable. +Example: true + + + + + + + + + The fee, charge or surcharge amount information per traveler. + + + + + + + Individual fee/ surcharge information would appear on the accontable document. + +Note: Separate structure for individual TAX details is also present. + + + + + + Fee Amount. Example: 500 USD + + + + + Local fee amount. Example: 7 CHF + + + + + Fee designator. Example: USC + + + + + Fee/ surcharge Description. Example: U.S Customs User Fee + + + + + Fee nature. + + + + + + + When true, this fee is approximate. + + + + + When true, this fee amount is refundable. + + + + + + + + + + + + + Exempt Tax Amount(s), Exemption Qualifiers and Total. + + + + + TAX CORE representation. + + + + When true, this tax is approximate. + + + + + When true, this tax must be collected. + + + + + When true, all tax amounts are refundable. + + + + + + + TAX DETAIL representation. + + + + + + Note: Tax information may be specified as: +-A total tax amount +-A total tax amount with associated tax breakdown +-A combination of both + + + + Sub-total of all applicable taxes. Monetary value and currency code. + + + + + + + + + + A collection of detailed taxes. + + + + + + Tax breakdown detail. + + + + + + Indicate whether a tax is paid or new etc. , PADIS codeset, 5305 + + + + + Amount. Example: 15000 USD + + + + + Tax Nation or Designator. Example: US, GB + + + + + Tax Code. Example: AY, GB + + + + + Tax type. Used to specify where the tax was applied. May be nice to have for auditing purposes. Example: 001, 002 + + + + + Tax data breakdown by collection point for XF(Passenger Facility Fee) and ZP(federal tax segment) taxes. + + + + + + + Amount field bythe airport in the currency applicable to the geographical location of the airport. Example: 2789 + + + + + + + + + Local tax amount. Example: 24 CHF + + + + + Tax short description. +Example: $4 per flight segment, per passenger (U.S. domestic segment tax) + + + + + Amount conversion + + + + + + + Define a date of the converion amount + + + + + + + + The tax filed amount. + + + + + The filed ticket tax code assigned by IATA.. + + + + + + + + A qualifier to the Tax Code to distinguish taxes/fees/charges with the same tax code but with different business uses. + + + + + + + + A qualfier to the filed tax code to distinguish taxes/fees/charges with the same tax code but with different business uses. + + + + + + + + + + When true, this tax is approximate. + + + + + When true, this tax must be collected. + + + + + When true, this tax amount is refundable. + + + + + + + + + + + + + + + EXEMPT TAX representation. + + + + + Sub-total of all exempt taxes. Monetary value and currency code. + + + + + + + + + + + Choice between specifying: +- Summary Exemption Information (Company, Country and/ or Territory Codes) +- Detailed Exemption Information + + + + + Name of entity to which passenger belongs, indicating an exemption to the application of a tax. + +Example: Military, Government + + + + + + Exempt tax entity name. Example: Military, IBM + + + + + + + + + + + + + Name or code of state or territory used to identify tax exemptions. + +Codes are published in Appendix C of IATA AIRIMP. + + + + + + Exempt tax territory code. Example: QC + + + + + + + + + + + + + Exempt tax country information. + + + + + + + + + + + Contains information of all taxes for which passenger is exempt. Includes designator, amount, country code, description etc. + + + + + + Tax nature. Example: US2 + + + + + Amount. Example: 15000 USD + + + + + Exempt tax country code. Example: US + +Encoding Scheme: ISO 3166-1 (two character) Country Code + + + + + Tax nature. Example: US2 + + + + + Local tax amount. Example: 24 CHF + + + + + Tax short description. +Example: $4 per flight segment, per passenger (U.S. domestic segment tax) + + + + + + + When true, this tax is approximate. + + + + + When true, this tax must be collected. + + + + + When true, this tax amount is refundable. + + + + + + + + + + + + The applicable code as provided for in A4A SIPP Resolution 110.16 or IATA Resolution 728. Further ticket +designators will be reported at the Fare Component level as matched from a Ticket Discount, ATPCO +Category 35, Category 25 or Category 19-22. + + + + + + AUTO EXCHANGE TICKET object. + + + + + Penalty/ change fee amount and allowable commission amount. + + + + + + Choice between specifying +amount value or percentage. + + + + Commission amount. Example: 20.00 USD + + + + + Commission percentage. Example: 20 + + + + + + Penalty or change fee amount. +Example: 100 USD + + + + + + + + Total original ticket amount. +Example: 200 USD + + + + + + Ticket Number(s). + + + + + + Ticket detail. + + + + + + + Passenger type code. +Example: ADT (ADULT) + +Encoding Scheme: IATA (three character) Passenger Type Code (PTC) + + + + + + + + + + + + + + + Ticket Designator with Application definition. + + + + + + Ticket Designator application. Examples: Requested, Ticketed + + + + + + + + + + Bilateral Time Limits. + +Note: These are bilaterally-agreed upon time limit that is not included in the NDC XML Specification. + + + + + Deposit Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +Note: This is the time by which a deposit must be paid for an Order. + + + + + + + + + + Time limit by which guaranteed inventory for a specified product offer is guaranteed as available and by which the inventory held must be converted into a completed order before the time limit expires otherwise the guarantee is lost. + +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + + + + + + + + + + Naming Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +Note: This is the time by which an Order must be completed with individual passenger names. + + + + + + + + + + Payment Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +Notes: +1. This is the deadline by which a commitment to pay must be made for the confirmed items in an offer as agreed witht he airline. The passenger meets this requirement by making complete payment for the order. + +2. Payment Time Limit and Ticket Time Limit may be the same in most cases; however, Payment Time Limit expands to include ticketless transactions and other accountable documents. + +3. This time limit is at the OFFER-LEVEL and will apply to all (child) Offer Items. + + + + + Price Guarantee Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +Note: This is the period for which an Offer price is guaranteed. On expiry an Offer may be re-priced up to the point an accountable document is issued. A Price Guarantee cannot extend beyond the Offer Time Limit unless the Order has been created. + + + + + Ticketing Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +The time by which passengers must secure tickets (or other accountable documents) for confirmed reservation as agreed with the airline. Passengers meet this requirement by purchasing a ticket (or other accountable document) which indicates the reserved services, or by having previously issued documents revalidated or reissued to reflect the reservation. + + + + + + + + + + + Offer/ Offer Item: BILATERAL (Implementer-Assigned) TIME LIMITS definition. + +Bilateral Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +Note: This is a bilaterally-agreed upon time limit that is not included in the NDC XML Specification. + + + + + Bilateral Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +Note: This is a bilaterally-agreed upon time limit that is not included in the NDC XML Specification. + + + + + + Bilateral Time Limit name. Example: Other Time Limit + + + + + Bilateral Time Limit name. Example: Other Time Limit + + + + + + + + + + + + Order/ Order Item: DEPOSIT Time Limit definition. + +Deposit Must be Paid By Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +Note: This is the time by which a deposit must be paid for an Order. + + + + + Timestamp. Example: 2017-01-13T13:59:38Z + + + + + + Order/ Order Item: NAMING Time Limit definition. + +Naming Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +Note: This is the time by which an Order must be completed with individual passenger names. + + + + + Timestamp. Example: 2017-01-13T13:59:38Z + + + + + + Offer/ Offer Item: PAYMENT Time Limit definition. + +Payment Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +Notes: +1. This is the deadline by which a commitment to pay must be made for the items in an order. This includes ticketless transactions and other accountable documents, such as EMD. + +2. Payment Time Limit and Ticket Time Limit may be the same in most cases; however, Payment Time Limit expands to include ticketless transactions and other accountable documents. + + + + + Timestamp. Example: 2017-01-13T13:59:38Z + + + + + + Offer/ Order: PRICE GUARANTEE Time Limit definition. + + + + + Timestamp. Example: 2017-01-13T13:59:38Z + + + + + + Ticketing Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +The time by which passengers must secure tickets (or other accountable documents) for confirmed reservation as agreed with the airline. Passengers meet this requirement by purchasing a ticket (or other accountable document) which indicates the reserved services, or by having previously issued documents revalidated or reissued to reflect the reservation. + + + + + Timestamp. Example: 2017-01-13T13:59:38Z + + + + + + + Instructions: Commissions definition. + + + + + + + + Instructions: Class of Service Upgrade definition. + + + + + Upgrade-eligible Service Class information. + + + + + + Upgrade-eligible Class of Service. Example: T + + + + + + + + + + Instructions: Free-Text Remark(s). + + + + + + + + + + A data type for Traveler FORM OF IDENTIFICATION representation. + + + + + Passenger Form of Identification detail. + + + + + + ID form. Examples: PT (passport), CC (credit card), FF (frequent flyer), DL (drivers license) + +Encoding Scheme: IATA Padis Codeset - List for data element 7365 - Processing indicator, coded + + + + + FOID ID value. Example: NY122345 + + + + + Owner/ Issuer of FOID. Example: United State Department Of State + + + + + + + + + + + Primary Contact Information. + + + + + + Passenger Name information. + +Note: Detailed Name information, such as prefix, title and suffix, are specified in PassengerMetadata. + + + + + + Family name, last name + +Example: SMITH + + + + + + + + + + + + Given name, first name or names + + + + + + + + + + + + Middle name or initial. Examples: G, GEORGE + + + + + + + + + + + + + + + + Contact(s). + + + + + + + + + + + + + + + + + + + + + Contains information on a Group, such as Group Name, number in party, and contacts for the group. + + + + + Group Name. Example: ABC Tour Club + + + + + PassengerCount. Example: 12 + + + + + + + + + + + NDC XML SPECIFICATION: NDC ACTOR XML OBJECTS + + + Notice: This is NDC Draft Specification provided for pre-review by the members of the relevant governance groups, it is not provided for implementation in a production environment or considered to be the final schema to support NDC business requirements. The draft schema may, at any time up to final specification submission, undergo changes including, but not limited to, specific elements, element names/labels, annotations or message name as a result of the ongoing quality control process, and comments, which may be received following the pre-review. Implementation of this version is done so at the risk of the implementer or implementing company. + + + + + + A data type for Partner Company Type contextual list. +Examples: ServiceProvider, ServiceFulfillment, Merchandise + + + + + + + + + + + + A data type for Partner Company Type. + + + + + + A data type for Agency Seller Type contextual list. +Examples: TravelAgency, OnlineTravelAgency, TravelManagementCompany + + + + + + Travel agency. + + + + + + + + A data type for Agency Seller Type. +Examples: TravelAgency, OnlineTravelAgency, TravelManagementCompany + + + + + + + A two-character alpha-numeric code assigned according to the IATA Resolution 762 or a three-letter airline designator assigned by ICAO. Refer to IATA Airline Coding Directory . + + + + + + + + + + + Unique Retailer ID. Example: LOUNGECO + +Encoding Scheme: Note, if this is an Airline retailer, the IATA/ A4A (two or three character) Airline Designator Code should be used. + + + + + + A data type for Core Airline Representation. + +Notes: +1. This type contains the common properties for all defined Airline Supplier Role definitions, e.g. POA, Operating Carrier. +2. This type is derived from SupplierCoreRepType. + + + + + + + + Airline Name. Example: British Airways + + + + + + + + + A data type for MARKETING CARRIER Supplier Role, Core Representation. + +Notes: +1. This is a representation of common (role-agnostic) properties associated with this Actor definition. +2. This type is used as (derived) base type for all Roles associated with this Actor. +3. This type is derived from AirlineCoreRepType. + + + + + + + + + + + + A data type for MARKETING CARRIER Supplier Role with Mandatory Flight Number. + + + + + + Airline Name. Example: British Airways + + + + + + The Reservation Booking Designator (booking class) of the Marketing Carrier. Example: Y + + + + + + + + The carrier that sells with its own code, and whos code will eventually appear on the relevant coupon on the issued accountable document. + +Note: Marketing Carrier may be differnt from an Operating Carrier, if the flight is actually operated by another carrier within a codeshare agreement. + + + + + A data type for OPERATING CARRIER Supplier Role with Optional Flight Number. + + + + + A two-character alpha-numeric code assigned according to the IATA Resolution 762 or a three-letter airline designator assigned by ICAO. Refer to IATA Airline Coding Directory. + + + + + Airline Name. Example: British Airways + + + + + + The Reservation Booking Designator (booking class) of the Operating Carrier if different from the Marketing Carrier. Example: Y + + + + + + + + A data type for MERCHANDISE RETAILER Supplier Role, Core Representation. + +Notes: +1. This is a representation of common (role-agnostic) properties associated with this Actor definition. +2. This type is used as (derived) base type for all Roles associated with this Actor. +3. This type is derived from SupplierCoreRepType. + + + + + + + + + + + + + A data type for SUPPLIER GROUP, Core Representation. + + + + + + + Additional supplier identification such as federal tax IDs or registry entries. + + + + + + Other ID Unique identifier. Examples: 13-015576, 50014517 + + + + + + + Other identification description. Examples: Federal Tax ID, TICO ID + + + + + + + + + + + + + + + + + A data type for Unique Airline Designator. + + + + + + + + + + A data type for Unique Retailer ID. + + + + + + + + Validating Carrier Airline Designator. +A two-character alpha-numeric code assigned according to the IATA Resolution 762 or a three-letter airline designator assigned by ICAO. Refer to IATA Airline Coding Directory . Example: BA + + + + + + Unique Aggregator ID. Example: F1 + + + + + + A data type for AGGREGATOR Intermediary Role, Core Representation. + +Notes: +1. This is a representation of common (role-agnostic) properties associated with this Actor definition. +2. This type is used as (derived) base type for all Roles associated with this Actor. +3. This type is derived from IntermediaryCoreRepType. + + + + + + + + + + Connection Communication Method. Examples: DirectWithAirline, DirectWithOther, Gateway + + + + + + + + A data type for SYSTEM Intermediary Role, Core Representation. + +Notes: +1. This is a representation of common (role-agnostic) properties associated with this Actor definition. +2. This type is used as (derived) base type for all Roles associated with this Actor. +3. This type is derived from IntermediaryCoreRepType. + + + + + + + + + + + + A data type for INTERMEDIARY GROUP, Core Representation. + + + + + + + Intermediary Name. Example: Farelogix + + + + + Intermediary Category. Example: Aggregator, Consolidator +Encoding Scheme: IATA Padis Codeset - Data element 9972 (Originator Type) + + + + + Contact detail. + + + + + + + Email address details, including application (I.e. home, business, etc.). + + + + + + + + + + + + + + A data type for Intermediary to Intermediary Role Association. + + + + Association link to Supplier object instance. Example: supplier1 + +Note: This is the @id specified in a Supplier object instance. + + + + + + Intermediary association for this (intermediary) role. + + + + + Unique System ID. Example: F1 + + + + + + A data type for Unique Aggregator ID. + + + + + + + + A data type for Unique NDC-Enabled System ID. + + + + + + + + + + SELLER: Agency User. + + + + + Unique Agency Seller ID. Example: CTRV + + + + + Agent User ID. Example: ksmith212 + + + + + A data type for Core Agency (Seller) Group Representation. + +Notes: +1. This type contains the common properties for all defined Agency Seller Role definitions, e.g. TravelAgency, Travel Agent. +2. This type is derived from SellerCoreRepType. + + + + + + + Additional Agency (Seller) identification, such as federal tax IDs or registry entries. + + + + + + Other identifier. Examples: 13-015576, 50014517 + + + + + + + + Other identification description. Examples: Federal Tax ID, TICO ID + + + + + + + + + + + + Pseudo City code. Example: AAA2 + + + + + + + Defines where the PCC was created. For example 1A, 1P, 1S + + + + + + + + + Agency Seller IATA number. Example: 98417900 + + + + + + + + + A data type for (AGENCY) AGENT USER Seller Role, Core Representation. + +Notes: +1. This is a representation of common (role-agnostic) properties associated with this Actor definition. +2. This type is used as (derived) base type for all Roles associated with this Actor. +3. This type is derived from AgencyCoreRepType. + + + + + + + Agent User ID. Example: ksmith212 + + + + + + + + + + Agent role. Example: Authorized User + + + + + + + + + A data type for Core Seller Actor Group Representation. + + + + + + + Agency Seller Name. Example: Carson Travel + + + + + Agency Seller Type. Examples: TravelAgency, OnlineTravelAgency, TravelManagementCompany + + + + + + + + + + A data type for TRAVEL AGENCY Seller Role, Core Representation. + +Notes: +1. This is a representation of common (role-agnostic) properties associated with this Actor definition. +2. This type is used as (derived) base type for all Roles associated with this Actor. +3. This type is derived from AgencyCoreRepType. + + + + + + + + + + + + + A data type for Agency (Seller) ID. + + + + + + + + A data type for Agent User (e.g. Travel Agent) ID. + +User ID. +Example: ksmith212 + + + + + + Agent User Name. Example: Karen Smith + + + + + + + + + Unique Partner Company ID. Example: AIRSTUFF + + + + + + PARTNER ROLE: FULFILLMENT PARTNER, Core Representation. + +Notes: +1. This is a representation of common (role-agnostic) properties associated with this Actor definition. +2. This type is used as (derived) base type for all Roles associated with this Actor. +3. This type is derived from PartnerCoreRepType. + + + + + + + Offer and Order Fulfillment(s). + + + + + + Fulfillment detail. + + + + + + Fulfillment Period. + +Note: This is the start and end date/time period(s) the service may be fullfilled or used. + + + + + + The EARLIEST date the associated optional service is available or may be used. Example: 2017-01-13 + + + + + + + + + + The LATEST date the associated optional service is available or may be used. Example: 2017-03-13 + + + + + + + + + + + + + Information about the location where the service will be fulfilled. + + + + + + + + + + + + + + + + + + + + + + PARTNER ACTOR, common properties. + + + + + + + + Partner Company Name. Example: Flight Stuff. Inc. + + + + + Partner Company Type. Examples: ServiceProvider, ServiceFulfillment, Merchandise + + + + + + + + + + A data type for Unique Partner Company ID. + + + + + + + + + + + + NDC XML Specification: The appinfo schema provides support for high level data model concepts and additional syntax to support the NDC conceptual model and validation of NDC-compliant instances. + + + + + NDC XML SPECIFICATION: XML System/ Application Data Components. + + + Notice: This is NDC Draft Specification provided for pre-review by the members of the relevant governance groups, it is not provided for implementation in a production environment or considered to be the final schema to support NDC business requirements. The draft schema may, at any time up to final specification submission, undergo changes including, but not limited to, specific elements, element names/labels, annotations or message name as a result of the ongoing quality control process, and comments, which may be received following the pre-review. Implementation of this version is done so at the risk of the implementer or implementing company. + + + + + + A data type for Device identification. + + + + + Device Type. Examples: Web Browser, Mobile Device + +Encoding Scheme: IATA Padis Codeset - List for data element TDT (Touchpoint Device Type) + + + + + + + + Device position and geocoding coordinates. + + + + + + + + + + Provides telephone information, and allows to specify telephone number application (ie Home, Business, etc.). May be used for a simle, unstrucutured number, or, in combination with child attributes allows to create a structured telephone number (ie Country Code number, Area Code numbers, etc.) + + + + + Associated IP address. +Examples: 192.0.2.8, 198.51.100.0 + + + + + Device MAC Address. Example: 00:0a:95:9d:68:16 + + + + + Named Device ID. Example: Bonnies iPad + + + + + + + + A data type for Business Object Parameters. + + + + + Requested and/ or Actual Primary and/ or Alternate message content language(s). + +Note: Language context is specified in the @application attribute, e.g. Requested, Display. + + + + + + + + + + Requested search processing and results currency information. + +Notes: +1. Currency context is specified in the @application attribute, e.g. Requested, Display. + + + + + + This group represents fares filed in a currency different from the currency of a point of sale. The content elements represent the original currency and amount as filed. + + + + + + + + Base Fare Amount as originally filed. + + + + + + + + + + Examples: Imperial, Metric + + + + + + + + + NDC Message Document information. + + + + + A data type for Common NDC Message Document Structures. + + + + + Document metadata + + + + + NDC Implementation Name. +Example: ThisAirline Gateway + + + + + NDC Framework Version. Example: SOAP 2015.1 + + + + + + A globally unique identifier for this object instance. + + + + + Object association(s) between this object and any object instance(s). + + + + + + + Pre-defined Message Policy information. + + + + + Policy information. + + + + + + Policy detail. + + + + + + + + + + + + + + + + + + Custom Policy Information augmentation point. + + + + + A data type for Policy Notification and Text, e.g. for sensitive data notification and/or handling. + + + + + Policy Detail. + + + + + + When true, data handling policy(s) apply. + + + + + Policy Code or ID. Example: DATA1 + + + + + Policy Type. Examples: Privacy_PII, Payment_PCI, Credentialing + + + + + + Policy short description. + + + + + + + Message Property Path information for this policy-associated element. + + + + + + Object association(s) between this object and any object instance(s). + + + + + + + + + A data type for Augmented Message Policy information. + + + + + Policy Augmentation Detail. + + + + + + + + Object association(s) between this object and any object instance(s). + + + + + + + + + Policy Location Link. Example: www.anyairline.com/thispolicy + + + + + + Point of Sale information. + + + + + A data type for Point of Sale. + + + + + Point of sale location information. + + + + + + + + + + + Point of sale timestamp value. Example: 2017-01-13T13:59:38Z + +Note: This may be used if the point of sale time zone differs from the message creation timestamp. + + + + + + + Point of sale time zone. +Example: UTC + + + + + + + + + Message Touchpoint information, including initiating device and event. + + + + + + The device from which the request was initiated. Examples: Agent Terminal, Web Browser, Mobile Device + +Encoding Scheme: IATA Padis Codeset - List for data element TDT (Touchpoint Device Type) + + + + + + + + Device position and geocoding coordinates. + + + + + + + + + + The travel event that triggered the request. +Example: Order/Buy, Check-In, In Flight + +Encoding Scheme: IATA Padis Codeset - List for data element TTT (Touchpoint Transaction Type) + + + + + + + + + A globally unique identifier for this object instance. + + + + + Object association(s) between this object and any object instance(s). + + + + + Internally define agent authority to request changes. + + + + + + + A data type for AGENT USER Message Party Representation. + +Notes: +1. Derived from AgentUserType. + + + + + + + + A data type for AGGREGATOR Message Party Representation. + +Notes: Derived from AggregatorType. + + + + + + + + + + + + A data type for Core Airline Message Party Representation. Derived from AirlineCoreRepType. + + + + + + + + + + + + + A data type for NDC-ENABLED SYSTEM Message Party Representation. + +Notes: +1. Derived from EnabledSystemType. + + + + + + + + A data type for Authentication and Notification of NDC Actors participating in the message/ transaction. Note that information about parties is intended for business use, it is not intended for transaction authentication and routing of the message. + + + + + Message Sender information. + + + + + + + + + + + + + + + + + + + Message Participant(s). + + + + + + Participant detail. + + + + + + + + + + + + + + + + + + + + + Named Message Recipient. + + + + + + + + + + + + + + + + + + + + NDC Message/ Transaction Party(s) information. Note that information about parties is intended for business use, it is not intended for transaction authentication and routing of the message. + + + + + A data type for RETAILER Message Party Representation. + +Notes: +1. Derived from RetailerType. + + + + + + + Retail Supplier Agent User information. + + + + + + + + + A data type for TRAVEL AGENCY Message Party Representation. + +Notes: Derived from TravelAgencyType. + + + + + + + + + + + + + SUPPLIER: ORA (Offer Originating Airline) Sender. + + + + + SUPPLIER: POA (Participating Offer Airline) Sender. + + + + + + INTERMEDIARY: Aggregator. + + + + + This specific data field to be used for an UNAFFILATED AGENT USER, rather than anyone linked directly to an IATA Agent user, which is identified in a different element. + + + + + A data type for Aggregator Message Sender Role. Derived from AggregatorMsgPartyCoreType. + + + + + + + + SELLER: Agent User. + + + + + + + + INTERMEDIARY: NDC-Enabled System. + + + + + A data type for Enabled System Message Sender Role. Derived from EnabledSysMsgPartyCoreType. + + + + + + + + A data type for Marketing Carrier Sender Role. Derived from AirlineMsgPartyCoreType. + + + + + + + + SUPPLIER: Marketing Carrier Sender. + + + + + A data type for Operating Carrier Sender Role. Derived from AirlineMsgPartyCoreType. + + + + + + + + A data type for ORA (Offer Originating Airline) Sender Role. Derived from AirlineMsgPartyCoreType. + + + + + + + + SUPPLIER: Operating Carrier Sender. + + + + + A data type for POA (Participating Offer Airline) Sender Role. Derived from AirlineMsgPartyCoreType. + + + + + + + + SUPPLIER: Retailer Sender. + + + + + A data type for Retailer Message Sender Role. Derived from RetailerMsgPartyCoreType. + + + + + + + + SELLER: Travel Agency + + + + + A data type for Travel Agency Message Sender Role. Derived from TrvlAgencyMsgPartyCoreType. + + + + + + + + Corporate Buyer + + + + + + Corporate name +Example: XYZ Corporation + + + + + Corporate ID + + + + + Corporate code used for pricing special fares + + + + + Agency Seller IATA number. Example: 98417900 + + + + + + + + Corporate Participant + + + + + + Corporate name +Example: XYZ Corporation + + + + + Corporate ID + + + + + Corporate code used for pricing special fares + + + + + Agency Seller IATA number. Example: 98417900 + + + + + + + + + + INTERMEDIARY: Aggregator Recipient. + + + + + SELLER: Agent User Recipient. + + + + + A data type for Travel Agency Message Recipient. + +Notes: +1. Derived from TrvlAgencyrMsgPartyCoreType. + + + + + + + + A data type for Aggregator Message Recipient Role. Derived from AggregatorMsgPartyCoreType. + + + + + + + + INTERMEDIARY: NDC-Enabled System Recipient. + + + + + A data type for Enabled System Message Recipient Role. Derived from EnabledSysMsgPartyCoreType. + + + + + + + + SUPPLIER: Marketing Carrier Recipient. + + + + + A data type for Marketing Carrier Recipient Role. Derived from AirlineMsgPartyCoreType. + + + + + + + + SUPPLIER: Operating Carrier Recipient. + + + + + SUPPLIER: ORA (Offer Originating Airline) Recipient. + + + + + A data type for Operating Carrier Recipient Role. Derived from AirlineMsgPartyCoreType. + + + + + + + + A data type for ORA (Offer Originating Airline) Recipient Role. Derived from AirlineMsgPartyCoreType. + + + + + + + + A data type for POA (Participating Offer Airline) Recipient Role. Derived from AirlineMsgPartyCoreType. + + + + + + + + SUPPLIER: POA (Participating Offer Airline) Recipient. + + + + + SUPPLIER: Retailer Recipient. + + + + + A data type for Retailer Message Recipient Role. Derived from RetailerMsgPartyCoreType. + + + + + + + + SELLER: Travel Agency Recipient. + + + + + A data type for Travel Agency Message Recipient Role. Derived from TrvlAgencyMsgPartyCoreType. + + + + + + + + + + INTERMEDIARY: Aggregator Participant. + + + + + A data type for Aggregator Message Participant Role. Derived from AggregatorMsgPartyCoreType. + + + + + + The sequence number of this participating Party within the collection of parties. +Example: 1 + +Notes: +1. A sequence number of 1 indicates that this is the first Participant involved in the transaction. + + + + + + + + A data type for Enabled System Message Participant Role. Derived from EnabledSysMsgPartyCoreType. + + + + + + The sequence number of this participating Party within the collection of parties. +Example: 1 + +Notes: +1. A sequence number of 1 indicates that this is the first Participant involved in the transaction. + + + + + + + + INTERMEDIARY: NDC-Enabled System Participant. + + + + + SUPPLIER: Marketing Carrier Participant. + + + + + A data type for Marketing Carrier Participant Role. Derived from AirlineMsgPartyCoreType. + + + + + + The sequence number of this participating Party within the collection of parties. +Example: 1 + +Notes: +1. A sequence number of 1 indicates that this is the first Participant involved in the transaction. + + + + + + + + SUPPLIER: Operating Carrier Participant. + + + + + A data type for ORA (Offer Originating Airline) Participant Role. Derived from AirlineMsgPartyCoreType. + + + + + + The sequence number of this participating Party within the collection of parties. +Example: 1 + +Notes: +1. A sequence number of 1 indicates that this is the first Participant involved in the transaction. + + + + + + + + A data type for Operating Carrier Participant Role. Derived from AirlineMsgPartyCoreType. + + + + + + The sequence number of this participating Party within the collection of parties. +Example: 1 + +Notes: +1. A sequence number of 1 indicates that this is the first Participant involved in the transaction. + + + + + + + + SUPPLIER: ORA (Offer Originating Airline) Participant. + + + + + SUPPLIER: POA (Participating Offer Airline) Participant. + + + + + A data type for POA (Participating Offer Airline) Participant Role. Derived from AirlineMsgPartyCoreType. + + + + + + The sequence number of this participating Party within the collection of parties. +Example: 1 + +Notes: +1. A sequence number of 1 indicates that this is the first Participant involved in the transaction. + + + + + + + + SUPPLIER: Retailer Participant. + + + + + A data type for Retailer Message Participant Role. Derived from RetailerMsgPartyCoreType. + + + + + + The sequence number of this participating Party within the collection of parties. +Example: 1 + +Notes: +1. A sequence number of 1 indicates that this is the first Participant involved in the transaction. + + + + + + + + SELLER: Travel Agency. + + + + + A data type for Travel Agency Message Participant Role. Derived from TravelAgencyMsgPartyCoreType. + + + + + + The sequence number of this participating Party within the collection of parties. +Example: 1 + +Notes: +1. A sequence number of 1 indicates that this is the first Participant involved in the transaction. + + + + + + + + + + A data type for Marketing Messages in a response message. + + + + + Marketing message. +Example: ONE Traveler MAY BE ELIGIBLE FOR A FREE SEAT + + + + + + + + Marketing Message Association(s). + + + + + + + + + + + + + A data type for Marketing Message Association Base List. + + + + + + + + + + + + + + A data type for Marketing Message Association List. + + + + + + Marketing Message Associations. + + + + + General Marketing Message Association Detail. + +Note: Includes an association type choice (e.g. MediaGroup) and an instance association value (e.g. mediagrp1). + + + + + + Named association type. Examples: Equipment, MediaGroup + + + + + Associated object instance value. Example: mediagrp1 + + + + + + + + + + + + Error(s) that prevented message processing. + + + + + A collection of errors that occurred during the processing of a message. + + + + + + + + Standard way to indicate that an error occurred during the processing of an IATA message + + + + + + The Error element MUST contain the Type attribute that uses a recommended set of values to indicate the error type. The validating XSD can expect to accept values that it has NOT been explicitly coded for and process them by using Type ="Unknown". + + + + + + An XPath expression that selects all the nodes whose data caused this error. Further, this expression should have an additional contraint which contains the data of the node. This will provide the offending data back to systems that cannot maintain the original message. + + + + + + + + Used for codes in the IATA code tables. Possible values of this pattern are 1, 101, EQP + + + + + + + + Used for strings, length 1 to 64. + + + + + + + + + Used to identify an application error by either text, code, or by an online description and also to give the status, tag, and/or identification of the record that may have caused the error. + + + + An error in textual format. + + + + + If present, this refers to a table of coded values exchanged between applications to identify errors or warnings. Refer to IATA PADIS Code List data element 9321. + + + + + If present, this URL refers to an online description of the error that occurred. + + + + + If present, recommended values are those enumerated in the IATA_ErrorRS, (NotProcessed | Incomplete | Complete | Unknown) however, the data type is designated as string data, recognizing that trading partners may identify additional status conditions not included in the enumeration. + + + + + If present, this attribute may identify an unknown or misspelled tag that caused an error in processing. It is recommended that the Tag attribute use XPath notation to identify the location of a tag in the event that more than one tag of the same name is present in the document. Alternatively, the tag name alone can be used to identify missing data [Type=ReqFieldMissing]. + + + + + If present, this attribute allows for batch processing and the identification of the record that failed amongst a group of records. + + + + + Used to specify the owner of the error/warning codelist. + + + + + + Used for strings, length 1 to 32. + + + + + + + + + Textual information to provide descriptions and/or additional information. + + + + + + + + + + Identifies language. + + + + Language identification. + + + + + + A data type for Message Processing Results. + +May include errors, business warnings, alternate offers indicator, supplemental marketing messages and/ or additional information required to complete a transaction. + + + + + Marketing Messages and Information. + +Notes: Marketing messages specified here apply to all message results, e.g. they are at a message-wide level. + + + + + + + + + + Transaction Processing Alert(s). + +Note: Alerts contain processing information have resulted in successful, but incomplete transaction processing and/ or are part of an ongoing transaction. + + + + + PROCESSING ALERT definition. + + + + + + + + + + PROCESSING ALERTS definition. + + + + + Alert detail. + + + + + + + + + + + + Inventory Discrepancy Notice. + +Supports notifying seller systems of discrepancy(s) between offered inventory (from a prior shopping response) and available inventory during order processing. If included in a response message, it may also include alternate offers. + + + + + Inventory Discrepency Alert definition. + +Note: This processing condition occurs when there is a discrepency between offered inventory and available inventory. It may include references to Alternate Offers. + + + + + Inventory Availability Status Code. +IATA Padis Codeset - List for data element 9321. Used in conjunction with Association(s) (Passenger, Group, Order Item, Offer Item and Optional Service) AnternateOffers (Alternate Offer(s) and Remarks (Payment remarks(s)). + + + + + Inventory Discrepency Alert Association(s), including Order, Order Item, Passenger, Group, Offer Item and Service. + + + + + Alternate Offer(s). + + + + + + The total number of Alternate Offers provided by this Airline. Example: 12 + + + + + Airline designator of the owner/ assigner of the Offer ID, typically used for offer ordering purposes. Example: UA, BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Code + + + + + Airline Alternate Offer Detail. + + + + + + + + + + + + + + + + + + + + + + When true, the inventory for the Offer Item is not available to order. + + + + + + + Shopping and Order Multiple Association definition. + + + + + + + + + Traveler Authentication Requested. + +Notes: +1. This processing condition occurs when additional Traveler authentication is required to complete transaction processing, such as access to secure FQTV information to complete Order pricing. + +2. This information contains the authentication scheme request information, e.g. parameters for Pin Phrase factor authentication. + +3. Multiple Travelers may be authentication requests may be specified. + + + + + Passenger Authentication definition. + +Notes: +1. The AuthQuestion is returned as an Alert in a Shopping or Order response message. +2. The AuthAnswer is returned as an Alert in a Shopping or Order request message. +3. Note that the CustomerInputRQ may be used to send an authentication response in lieue of using an alert in a request message. + + + + + + + PIN Phrase Authentication Request. + + + + + + + When true, fulfullment of this Order requires additional Traveler authentication. + + + + + When true, the maximum Authentication attempts have been exceeded. + + + + + When true, the Authentication transaction should be resent. + + + + + + + + + PIN Phrase Authentication Response. + + + + + + + + + Traveler Authentication Challenge Answer definition. + + + + + Traveler Authentication process status. +Examples: +Y- Customer authenticated +N- Customer not authenticated +A- An authentication attempt occurred but could not be completed +U- Unable to perform authentication + + + + + + + Authentication Status Context. + + + + + + + + + PIN Answer. +Example: BTSY + + + + + Original Credentialing Question. Example: What is a memorable place? + + + + + Pre-defined Account information. + + + + + Mobile Device information. + + + + + + + + Device Location geocoding information. + + + + + + + + + + The identifier of the original transaction that initiated this Traveler authentication. Example: TRN12345 + + + + + + + ID or name of the source of this Transaction ID. Examples: UA, ABC123 + +Note: If this is an airline ID, use IATA/ A4A (two or three character) Airline Designator Code Encoding Scheme. + + + + + + + + + + + Traveler Authentication Challenge Question definition. + + + + + Traveler Authentication process status. +Examples: +Y- Customer authenticated +N- Customer not authenticated +A- An authentication attempt occurred but could not be completed +U- Unable to perform authentication + + + + + + + Authentication Status Context. + + + + + + + + + Pin Phrase Challenge information, including source URL and challenge parameters. + + + + + + URL to source location for authentication service, instructions, etc. + + + + + End User Parameters, including challenge question and phrase prompt. + + + + + + Challenge Question. +Example: What is a memorable place? + + + + + Answer Characters Prompt. +Example: Please provide the 1st, 3rd, 4th and the last characters from your memorable place. + + + + + Requested Character Positions. + +Note: This is a character position array that may be used in association with the Prompt. + + + + + + Character Position. Example: 5 + + + + + + + + + + + + + + + + + + + + Traveler Authentication Request Association(s), including Order, Order Item, Passenger, Group, Offer Item and Service. + + + + + Pre-defined Account information. + + + + + Traveler Device information. + + + + + + + + Device Location geocoding information. + + + + + + + + + + The identifier of the original transaction that initiated this Traveler authentication. Example: TRN12345 + + + + + + + ID or name of the source of this Transaction ID. Examples: UA, ABC123 + +Note: If this is an airline ID, use IATA 2 character or ICAO 3 letter Airline Designator Code Encoding Scheme. + + + + + + + + + + + + + 3D Secure Payment Processing information. + + + + + SECURE PAYMENT definiton. + + + + + + + + Payer Authentication Request or Response structure. + + + + + + Payer Authentication Request value. +Example: eNp1UttugzAM/RXE+0gosF5kUkFZtT506rp222sUvJatXBqgtPv6JQzW7WFRIvnY1rF9HJie04NxQlk +meeabtkVNAzO/GAw== + + + + + Payer Authentication Response value. +Example: eJzVWFmzosgSfudXdPQ8Gt1sbkzYRhQ7KCjI/sYOsimgoL/+lp7Tp5c5t2d67tMw8yv/WqiluJXS8WyyVFEQT28qz + +Note: This is the PARes (Payer Authentication Response) to be POSTed back to the TermURL (the URL to which the user will be directed at the conclusion of 3D secure authentication.) + + + + + + + + 3D Secure Transaction Type. +Examples: +Authorize: Authorize amount (no funds transferred) +Complete: Complete a previous authorization (funds are transferred) +Purchase: Purchase (funds are transferred immediately) +Refund: Refund (funds transferred immediately) +Validate: Validation Transaction (a small authorized transaction amount to validate card details including expiry date and address) + + + + + + + Transaction Type context. + + + + + + + + + 3D Secure Program Enrollment Status. Examples: CardNotEnrolled, CardEnrolled, CardMayBeEnrolled, Unknown + + + + + + + Enrollment Status context. + + + + + + + + + Airline 3D Secure Payment Merchant Account information. + + + + + + Airline Merchant Identification Code or Number. Example: BA123 + + + + + + + Airline Merchant ID context. + + + + + + + + + Merchant Name. Example: SecurePay + + + + + + + Airline Merchant Name context. + + + + + + + + + Airline Merchant Country Code. Example: GB + +Encoding Scheme: ISO 3166-1 (two character) Country Code + + + + + + + + + + + + + Transaction Reference(s). + + + + + + + + The identifier of the original transaction that initiated this Traveler authentication. Example: TRN12345 + + + + + + + ID or name of the source of this Transaction ID. Examples: UA, ABC123 + +Note: If this is an airline ID, use IATA/ A4A (two or three character) Airline Designator Code Encoding Scheme. + + + + + + + + + 3DS Transaction Timestamp. Example: 2015-01-13T13:59:38Z + + + + + Transaction description. Example: Air Fare Two PAX + + + + + Other (free form text) Transaction Data(s). + + + + + + Other Transaction Data. + + + + + + + + + + + Airline and 3DS Merchant URL(s). + + + + + + + + + + 3D Secure Payment Details, including 3DS Transaction Client, Customer Device, Input and Settlement Currency, Order Reservation Detail, Transaction Timestamp and Additional Data. + + + + + + 3DS Transaction Timestamp. Example: 2015-01-13T13:59:38Z + + + + + 3DS TransactionClient Type. +Examples: +InteractiveVoiceResponse (IVR) +Internet +MailOrTelephoneOrder (MOTO) +Recurring +Unattended + + + + + + + Client Type context. + + + + + + + + + Device upon which the secure transaction will occur. + + + + + + + + Browser Accept Header. + +Note: This contains MIME types accepted by the device. + + + + + User Agent String. + +Note: This contains the user agent string. + + + + + Device type. Example: Desktop, Mobile + +Note: This is the device that the transaction will occur on. + + + + + + + + + + Input and Settlement Currency Code(s). + + + + + + Input Payment Currency code. Example: USD + +Encoding Scheme: ISO 4217 (three alpha character) Currency Code + + + + + Settlement Payment Currency code. Example: CHF + +Encoding Scheme: ISO 4217 (three alpha character) Currency Code + + + + + + + + 3D Secure Transaction Airline Reservation information. + + + + + Other (free form text) Transaction Data(s). + + + + + + Other Transaction Data. + + + + + + + + + + + Secure Payment-related Processing information, including AVS/ CVV Verification Results and Secure Payment Processing Results. + + + + + + Processing Information detail. + + + + + + Address Verification Status Response information. + + + + + AVS Response Code. + +Examples: +X - Match: Street address and 9-digit ZIP code both match +Y - Match: Street address and 5-digit ZIP code both match +A - Partial Match: Street address matches, but both 5-digit and 9-digit ZIP Code do not match +W - Partial Match: Street address does not match, but 9-digit ZIP code matches +Z - Partial Match: Street address does not match, but 5-digit ZIP code matches +N - No Match: Street address, 5-digit ZIP code, and 9-digit ZIP code all do not match +U - System Unavailable: Address information unavailable. Returned if non-US. AVS is not available or if the AVS in a U.S. bank is not functioning properly. +R - System Unavailable: Retry - Issuer's System Unavailable or Timed Out. +E - Invalid: AVS data is invalid +S - Not Supported: U.S. issuing bank does not support AVS + +Note: This is the address verification response code (AVS) when the ticketing agency performs address verification. + + + + + Additional Response Text from 3DS Provider. + + + + + When true, the specified address was invalid. + + + + + When true, the specified address could not be matched with issuing bank address on record. + + + + + + + The unique Cardholder Authentication Verification Value (CAVV) associated with the transaction, provided by the card issuer. +Example: Q0FWVkNBVlZDQVZWQ0FWVkNBVlY= + +Note: Only returned if card is enrolled and authenticated. + + + + + 3DS Program ACS Customer Authention Status. +Examples: +Y- Customer authenticated. +N- Customer not authenticated. +A- An authentication attempt occurred but could not be completed. +U- Unable to perform authentication. + +Note: Only returned if card is enrolled. + + + + + + + Enrollment Status context. + + + + + + + + + The ECI (E-Commerce Indicator) security level associated with the transaction. +Example: 05 + +Note: Only returned if card is enrolled and authenticated. + + + + + + + + + + + + + + + + + Unique 3D Secure transaction reference number assigned by Access Control System (ACS). +Example: Qzl3WVc1TVpXNW5kR2crUEcxbGMzTmhaMlZKWkQ1UVFWSmxjUzB4TWpnNUSXcKTmprNU5EWThMMjFsYzNOaFoyVkpRDQ4TDAxRVBqd3ZVVEr + +Note: This is typically required for ACS systems that support Status Query. + + + + + + + Transaction Reference context. + + + + + + + + + 3D Secure Transaction Airline Reservation information. + +Note: This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of this capability is not dictated by this specification. + + + + + + + + + + Unique Secure Payment Merchant (SPM)-assigned transaction reference number. Example: VEw4TkFrakFYMmEreXdoZE5xZUU= + + + + + + + Transaction Reference context. + + + + + + + + + + SECURE PAYMENT AIRLINE RESERVATION definition. + + + + + + Airline Carrier(s). + + + + + + A two-character alpha-numeric code assigned by the IATA. Refer to IATA Coding Directory and IATA Resolution 762 for Airlines and 763 for Airports. Application attribute is used to indicate whether the airline is a marketing or an operating carrier. + + + + + + + Airline Carrier Application. Examples: Operating, Marketing + + + + + + + + + + + + Data and time information used to enrich secure payment details. Used in conjunction with application identification attribute, to indicate date/ time application (I.e. departure, arrival, etc.). + + + + + + Date, Time and Application. + + + + + Date. Example: 2017-01-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + Time. Example: 09:15 + +Encoding Scheme: ISO 8601 Military/ 24 Hour Format (HH:MM) + + + + + Date Application. Example: Departure, Arrival, Connection + + + + + + + + + + Class(es) of Service. + + + + + + + + + + Stop Location(s). + + + + + + Stop Location details including arrival date and time, departure date and time and change of gauge. + + + + + + + + + + + + + + A code that gives information regarding the type of fare, class entitlement, minimum and maximum validity, reservations entitlement, seasonality, days of travel and advertising or sales restrictions. + + + + + + + + + + Flight Number(s). + + + + + + + + + + Passenger Name. Example: John Smith + +Note: This is the primary contact on the reservation. + + + + + Passenger Residence country code. Examples: US, FR + +Encoding Scheme: ISO 3166-1 (two character) Country Code + + + + + + + + + + Document Number assigned to this transaction comprised of the following: +• Airline Code - 3-digit Airline identification number (one character reserved for expansion) + +• Form Code - A maximum of 3 digits indicating the type of document, the source of issue and the number of coupons it comprises, + +• Serial No. - A maximum of 8 digits allocated on a sequential basis, provided that the total number of digits allocated to the Form Code and Serial Number shall not exceed ten. + + + + + + Travel Agency Information. + +Note; This typically contains the seller travel agency ID and/ or Name. + + + + + + + + SECURE PAYMENT URL definition. +A data type for Airline and 3DS Merchant URL(s). + + + + + 3DS Access Control System URL. + +Note: This is the URL of the Issuing Bank's ACS, to which the cardholder needs to be re-directed. The browser should simply redirect to this URL. + + + + + Airline URL to which the user will be directed in the event of an secure auhorization failure. +Example: http://ba.com/paymentResultFailure + + + + + Verification Merchant website URL. + +Note: This is the verification source merchant URL. + + + + + The URL to which the user will be directed to at the conclusion of 3D secure authentication. +Example: http://ba.com/paymentResultSuccess + + + + + + + + A data type for Pre-established Account information. + + + + + Account ID. Examples: FQTV1234, jsmith@email.com + + + + + Pre-established Account Name. Example: johns + + + + + First Name on Account. Example: John + + + + + Last Name on Account. Example: Smith + + + + + + + + Transaction Processing Marketing Message(s). Note: Marketing messages specified here apply to all message results, e.g. they are at a message-wide level. + + + + + + + Marketing message. Example: ONE Traveler MAY BE ELIGIBLE FOR A FREE SEAT + + + + + + + + + + Business Warning Association(s), including Order, Order Item, Passenger, Group, Offer Item and Service. + + + + + + + + + + + + + + + + Transaction Processing Notice(s). Note: Notices contain information about specific NDC capabilities being utilized during transaction processing. + + + + + + + Notice detail. Note: These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of the capability is not dictated by this specification. + + + + + + + + + + Price Variance Rule(s) Notice. Note: Supports specifying Payment Processing Rules, including payment failure. Request messages may include defined payment processing rules and an indicator requesting that the rules be applied during payment processing where relevant. Response messages may additionally include notice about if and how payment rule(s) were applied during transaction processing. + + + + + + + + + + + + + + + + Inventory Guarantee Notification. Supports requesting a guarantee for inventory-associated offers in a request message. Notification of any guaranteed inventory (e.g. status, reference number, time limit and associations) may be returned in a response message. Note that the inventory guarantee time limit is the time that inventory for a specified product offer is guaranteed as available and the inventory held must be converted into a completed order before the time limit expires otherwise the guarantee is lost. Held Inventory is referenced by an Inventory Guarantee identifier. + + + + + + + Payment Processing Rule(s) Notice. Note: Supports specifying Payment Processing Rules, including payment failure. Request messages may include defined payment processing rules and an indicator requesting that the rules be applied during payment processing where relevant. Response messages may additionally include notice about if and how payment rule(s) were applied during transaction processing. + + + + + + + Price Variance Rule(s) Notice. Note: Supports specifying Payment Processing Rules, including payment failure. Request messages may include defined payment processing rules and an indicator requesting that the rules be applied during payment processing where relevant. Response messages may additionally include notice about if and how payment rule(s) were applied during transaction processing. + + + + + + + + + + + Pricing Parameters Notice. Note: Supports specifying transaction pricing parameters. Request messages may include indicators requesting that certain methods be applied during payment processing where relevant. Response messages may additionally include notice about if and how pricing parameters were applied during transaction processing. + + + + + + + Optional Service Filter Notice. Note: Supports specifying optional service filters in request messages to inform a receving system of the category(s) of offers being requested. Response messages may additionally include notification of which (if any) service filters were applied during transaction processing. + + + + + + + Tax/ Fee Exemption Notice. Note: Supports notification to receiving system that tax/ fee exemptions are requested during transaction processing, and, if and how the exemptions were applied to message results. + + + + + + + Inventory Guarantee Notice definition. + + + + + Inventory Guarantee Request Notice. + + + + + + When true, inventory guarantee is requested for offers. + + + + + + + + + Inventory Guaranteed during transaction processing. + + + + + + + Inventory Guarantee + + + + + + + Unique Inventory Guarantee ID. Examples: INVREF123456, 68E0-675C Note: This is a unique identifier issued by an Airline to reference that inventory for a specified offer will be guaranteed as available for a period. + + + + + + + + Inventory Guarantee Association(s), including Order, Order Item, Passenger, Group, Offer Item and Service. + + + + + + + + + + When true, no offers have guaranteed inventory . + + + + + + + + + + Information Policy Notice definition. + + + + + Policy Detail. + + + + + + + + + + + + When true, data policy(s) have been specified for payload content. + + + + + + + Payload Content Localization Notice definition. + + + + + + + + Payload Content Language Representation Code(s). Notes: 1. Payload content localized language representation in support of I18N aware systems. 2. Language Code context is specified in the @Application attribute, e.g. Requested, Display. + + + + + + + Payload Content Currency Representation Code(s). Notes: 1. Payload content localized currency representation in support of I18N aware systems. 2. Currency Code context is specified in the @Application attribute, e.g. Requested, Display. 3. This is not the point of sale currency that is specified in the PointOfSale node. + + + + + + + + + + + + + + + COMMON NOTICES definition. + + + + + + Payload Content Localization Notice. Note: Supports i18n-enabled systems by notifying seller systems of language and currency preferences in request messages and language and currency application is response messages. + + + + + + + Information Policy Notice(s). Note: Supports specifying information policy notices at the message and/ or schema node level. + + + + + + + + Payment Processing Rules Notice definition. + + + + + + + Form of Payment Failure Rules. Rule Application Scope: 1. Order ID (entire order) 2. Order Item ID (e.g. flights and ancillary services) + + + + + + + Payment Order Creation Rule(s). + + + + + When true, the Seller wants to proceed with Order creation if one of multiple forms of payment provided fails. Note: This supports multi payment form-enabled systems where one Traveler may provide multiple FOPs, or individual Travelers may each provide their own FOP. + + + + + + + + Payment Order Creation Rule Usage during transaction processing. + + + + + + + + Payment Failure Code (and optional definition.) Encoding Scheme: IATA Padis Codeset - List for data element [9321] Application Error, coded + + + + + + + + + When true, one of multiple forms of payment provided failed. + + + + + + + + + + + + + + + + Acceptable Price Variance Rule definition. Note: This is the acceptable amount and/or percentage of the total amount by which the Order item price can vary from the Offer price for Order creation to proceed, for example to cover minor currency exchange rate fluctuations for taxes quoted in a different currency. + + + + + + + + Price Variance Order Creation Rule(s). + + + + + + Price Variance Rule detail. + + + + + + Rule sequence (or order) number. Example: 1 + + + + + Unique Rule ID. Example: PRICERULE001 Note: Optional rule context and name may also be specified. + + + + + + + + Rule ID Context. + + + + + + Rule Name. Example: Acceptable Order Item Price Variance + + + + + + + + + + + Acceptable amount and/or percentage of the total amount by which the Order item price can vary. Example: 20 USD, 2 Percent + + + + + + + + + + + + Rule Name. Example: Acceptable Price variance + + + + + + + + + + + Entity that owns/ assigned this Rule. Example: BA Note: If this is an airline, the IATA/ A4A (two or three character) Airline Designator Code should be used. + + + + + + Rule Effective Period. + + + + + + + + + + + + + + + + + Price Variance Rule applicable Input and Settlement Currency(s). + +Note: This contains one or multiple input and settlement currency codes that this rule applies to. In addition to the specified currency code, an Application of InputCurrency and/ or SettlementCurrency should be specified. + + + + + + + Input Payment Currency code. Example: USD Encoding Scheme: ISO 4217 (three alpha character) Currency Code + + + + + + + Settlement Payment Currency code. Example: CHF Encoding Scheme: ISO 4217 (three alpha character) Currency Code + + + + + + + + + + + + + + + + When true, price variance rule(s) have been specified. + + + + + + + + + Price Variance Order Creation Rule(s) Usage during transaction processing. + + + + + + + Applied Price Variance Rule(s). + + + + + + Unique Rule ID which was applied during transaction processing. Example: PRICERULE001 Note: Optional rule context and name may also be specified. + + + + + + + Rule ID Context. + + + + + + Rule Name. Example: Acceptable Order Item Price Variance + + + + + + + + + + + Applied Price Variance Amount and/or Percentage. Example: 20 USD, 2 Percent + + + + + + + + + + + + + Order ID, Order Item and other associations where a price variance was applied. + + + + + + + + + + + When true, a pricing variant was applied to the total order price or one or more priced Order Items. + + + + + + + + + + + + Pricing Parameters Notice definition. + + + + + + + Requested Pricing Parameter(s). + + + + + When true, this request is to be handled by an auto-exchange process. + + + + + + When true, award eligible in addition to priced offers and fares is requested. + + + + + + When true, only award eligible offers/ fares are requested. + + + + + + When true, Simple Pricing for flight offers is requested. + + + + + + + + + Pricing Parameter application in transaction processing. + + + + + + When true, this request was handled by an auto-exchange process. + + + + + + When true, award eligible in addition to priced offers and fares are included in the results. + + + + + + When true, only award eligible offers/ fares have been returned. + + + + + + When true, Simple Pricing for flight offers was applied. + + + + + + + + + + + + + Optional Service Filter Notification. Note: Supports ATPCO group and subgroup code(s) that specify the requested categories of Optional Services to be returned in the results. + + + + + + + + Alternate Offer Rules. + + + + + + Optional Service Filter(s). + + + + + + + + + Alternate Offers created during transaction processing. + + + + + + + + Optional Service Filter(s) applied during transaction processing. Note: This is a list of requested optional service filters that apply to returned offers. + + + + + + + Applied Optional Service Filter(s). + + + + + + + + Association(s). + + + + + + Shopping Offer Association(s). + + + + + + Associated Shoppers. Note: Includes Anonymous, Recognized and/or PTC shopper association. + + + + + + Associated Flight(s). + + + + + Associated Price Class information. + + + + + + + + + + Baggage Detail Associations. + + + + + Offer Detail Association(s). + + + + + + Other Named Association(s). Note: Includes an association type choice (e.g. MediaGroup) and an instance association value (e.g. mediagrp1). + + + + + + + Named Instance Association Type. Examples: CarryOnAllowance, MediaGroup + + + + + + + Associated object instance value. Example: mediagrp1 + + + + + + + + + + + Order Association(s). + + + + + + + + + + + + + + + + + + When true, service filters specified in the request message have resulted in offers in this reponse. + + + + + + + + + + + + + Pricing-related Fee and Tax Exemption Notice definition. + + + + + + + + Exemption Rule(s). + + + + + + + Named Tax Exemptions, including Country(s), Entity(s), Territory(s) and Tax Code(s). + + + + + + + Exempt tax country information. + + + + + + + + + + Name of entity to which passenger belongs, indicating an exemption to the application of a tax. + +Example: Military, Government + + + + + + Exempt tax entity name. Example: Military, IBM + + + + + + + + + + + + + Name or code of state or territory used to identify tax exemptions. + +Codes are published in Appendix C of IATA AIRIMP. + + + + + + + Exempt tax province/ territory name or code. Example: QC + + + + + + + + + + + + + + + Exempt Tax Code(s). Note: This contains tax exemption(s) based on tax designator and nature. + + + + + + + Tax Code detail. + + + + + + Tax designator. Example: XY + + + + + + + + + + Tax nature. Example: I + + + + + + + + + + + + + + + + + + + Additional Tax Exemption Rule(s). + + + + + + When true, all pricing is tax/ fee exempt. + + + + + + + + Exemption Rule(s) applied during transaction processing. + + + + + + + Applied Tax Exemption(s). + + + + + + Unique Rule ID which was applied during transaction processing. Example: PRICERULE001 Note: Optional rule context and name may also be specified. + + + + + + + Rule ID Context. + + + + + + Rule Name. Example: Acceptable Order Item Price Variance + + + + + + + + + + + Order ID, Order Item and other associations where a price variance was applied. + + + + + + + + + + + When true, a tax/ fee exemption was applied to the total order price or one or more priced Order Items. + + + + + + + + + + + + + A data type definition for Encoding Scheme. + + + + + Encoding Scheme Characteristics, including name, purpose, type, source uri, version and supported domains. + + + + + + Supported NDC Domains by scheme version. + + + + + Supported NDC Domain Name. + +Examples: Shopping, OrderManagement, PaymentTicketing, AirlineProfile, Utility + +Note: Supports pre-defined enumerated list and/ or bilaterally-agreed upon values. + + + + + Associated Encoding Scheme Version(s). Example: 1.7, 1.0 - 1.7 + + + + + + + + Encoding Scheme Name. Example: Optional Service Encoding + + + + + Vocabulary Purpose. Example: Optional Service Encoding + + + + + Encoding Scheme Source Location URI. + + + + + Encoding Scheme Version. Example: 1.7 + + + + + + + Encoding Scheme Metadata, including timestamp and remark. + +Note: Information and/ or capabilities specified in Metadata may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation is not dictated by this specification. + + + + + + + + Remark(s). + + + + + + Scheme Timestamp. Example: 2017-01-13T13:59:38Z + + + + + + + + + + Encoding Scheme globally unique instance/ class Key. + +Example: 8wOlMeZCT5+kR+mdfzsRlA + + + + + Owner Airline (or other entity) Code. Examples: BA, WIDGETCO + + + + + Scheme Owner Type. + +Examples: Airline, Filed, ThirdParty + +Note: Supports pre-defined enumerated list and/ or bilaterally-agreed upon values. + + + + + Scheme Owner Name. Example: British Airways + + + + + Encoding Scheme Token, e.g. reference association ID. + +Example: jZhJu7SORZeOMNpifElIkA + + + + + + + A data type definition for Policy. + + + + + + + Policy Data Node information. + +Note: Describes schema document node location, including node tag name and path, for data with associated policy. + + + + + + Policy Data Node detail. + + + + + + + + + + + + + Policy Description, including text and link. + + + + + + Policy Description, including text and link. + + + + + + + + Policy Metadata, including policy effective period. + +Note: Information and/ or capabilities specified in Metadata may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation is not dictated by this specification. + + + + + + + + Remark(s). + + + + + Encoding Scheme information. + + + + + + + + + + Policy Effective and Expiration Period. + + + + + + + + + + + Policy Code or ID. Example: DATA1 + + + + + + + + + + Policy Type. Examples: Privacy_PII, Payment_PCI, Credentialing + +Note: Supports pre-defined enumerated list and/ or bilaterally-agreed upon values. + + + + + Policy Version. Example: 2.17 + + + + + + + + + NDC XML SPECIFICATION: NDC DATA LISTS shared by all NDC Domains. + + + Notice: This is NDC Draft Specification provided for pre-review by the members of the relevant governance groups, it is not provided for implementation in a production environment or considered to be the final schema to support NDC business requirements. The draft schema may, at any time up to final specification submission, undergo changes including, but not limited to, specific elements, element names/labels, annotations or message name as a result of the ongoing quality control process, and comments, which may be received following the pre-review. Implementation of this version is done so at the risk of the implementer or implementing company. + + + + + Common NDC Data List choices. + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Checked or Carry-On Baggage Allowance detail. Use BaggageCategory to specify which of the two. + + + + + + Enumeration: + +CarryOn +Checked + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + + + + + + + + Description Details + + + + + + + + + + + + List of flight segments. + + + + + + FlighSegment information. Contains details flight segment information. + + + + + + + + List of Flight elements. + + + + + + Journey information describing the travel between an airport/city where travel commences and an airport/city where travel ultimately terminates. A journey may be comprised of one or more segments. Note: This node will be renamed to journey in future releases. + + + + + + Flight journey information. + + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + + + A globally unique identifier for this Flight instance. Example: flight1 + + + + + + + + + + List of Origin/Destination elements. + + + + + + + + + + + + + + + + + + + + Baggage Disclosure(s). + + + + + US DOT BAGGAGE RULE data list definition. + Select a value from the enumerated list or enter a string value. +=enumerated values= +N = NOT SUBJECT TO US DOT RESERVATION OR DISCLOSURE +Y = SUBJECT TO US DOT RESERVATION AND DISCLOSURE +D = SUBJECT TO DISCLOSURE BUT NOT TO US DOT RESERVATION + + + + + Baggage Disclosure detail. + + + + + + US Department of Transportation (DOT) Reservation or Disclosure baggage rule. +Examples: Y, Disclosure AND US DOT Reservation + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + + If True: Additional Taxes, Fees and Charges may be collected at check-in (regionally determined). + + + + + If True, The ORA advises the POA that the POA is given the Baggage Determining Carrier designation + + + + + Bi-lateral agreement identifier, i.e. - baggage cost, Baggage Determining Carrier, etc. + + + + + Allows POA to tell the ORA if the ORA may alter the POA’s pre-paid baggage charges + +If True: prepaid charge may NOT be altered +If False: prepaid charge MAY be altered + + + + + + + + + + Content Source or Owner. + + + + + CONTENT SOURCE data list definition. + + + + + + + + XPath to element or attribute in the message. +Encoding Scheme: W3C xPath Notation + + + + + Choice of Airline or Other (non-airline) source identifier. + + + + + Other source identifier. +Example: DLX + + + + + + + Other ID name. +Example: Datalex + + + + + + + + + + + + + + + + A data type definition for Plain Text with Link Description. + + + + + Link(s). + + + + + + Description Link. Example: thisairline.com/myLink + + + + + + + + Link Description(s). + + + + + + Description detail. + + + + + + + + + Language Code. Example: en, en-US + + + + + + + + + + Creation Timestamp. Example: 2017-01-13T13:59:38Z + + + + + Title. Example: This Title + + + + + + + A data type definition for URI with Formatting. + + + + + + + Link detail. + + + + + + + Link Context. + + + + + Link Text. Example: Visit Program Benefits + + + + + Link Value. Example: www.thislink.com + + + + + + + + + + + + + + Airline and Offer Disclosures. + + + + + DISCLOSURE data list definition. + + + + + Disclosure Description or Link. + + + + + + Plain Text or Rich Media Disclosure Description(s). + + + + + + + + + + + + Element combining Fare Basis Code and Fare Details. + + + + + + + + + Fare detail. + + + + + + + + + + + Fare Basis Code detail. + + + + + + Fare basis code. Example: Y26 + + + + + Fare basis application. +Examples: Requested, Ticketed, Other + + + + + + + + + + + + + + + + Includes Class of Service details. + + + + + + Flight origin/ destination information. + + + + + + + Marketing Carrier information. + + + + + Operating Carrier Information. + +Operating Carrier is the carrier that operates a flight with a reference to its own prime flight number. + +Note: Operating Carrier may be different from a Marketing Carrier(s), if the flight is actually marketed by another carrier(s) within a codeshare agreement. + +Operating Carrier may not be the AOC holder, in which case, and wherever required, this will need to be disclosed to the customer. + + + + + + + + + + + + + + + + Flight Details. + + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + + + A globally unique identifier for this Flight Segment instance. Example: segment1 + + + + + When true, there are one or more connections for this flight. + + + + + When true, an electronic ticket may be issued. + + + + + When true, the fare can be purchased without issuing a ticket. + + + + + When true, the flight is secure flight. An indicator to disclose when a flight is a "secure flight" + + + + + + A data type for a list of Classes of Service. + + + + + Class of Service. + + + + + + Class of Service. Example: T + + + + + Name. Example: Economy + + + + + Class of Service Association(s). + + + + + + + + + + + + MEDIA data list definition. + + + + + Media Choices. + + + + + + Description-associated MEDIA OBJECT ID or Key. Example: IMG1 + + + + + Description-associated MEDIA LINK. + + + + + Description-associated Media Attachment ID. Example: ATT1. + + + + + + + + + + + + Multi-Media/ Rich Descriptions. + + + + + + Offer/ Order Instruction(s). + + + + + OFFER/OFFER ITEM INSTRUCTIONS data list definition. + + + + + Offer Instruction detail. + + + + + + + + + + + + + + OFFER/OFFER ITEM PENALTY data list definition. + + + + + Penalty detail. + + + + + + + + + + + + OFFER/OFFER ITEM TERMS data list definition. + + + + + Terms detail. + + + + + + + + Offer/ Order Penalty(s). + + + + + Offer/ Order Term(s). + + + + + + PRICE CLASS data list definition. + + + + + + + + Price Class List. + + + + + + OPTIONAL SERVICE BUNDLE Data List definition. + + + + + + + + Individual service items in bundle count. Example: 4 + + + + + Associated Services. + + + + + + + + + + + Minimum and Maximum Bundle Item Selection rules. + + + + + + MINIMUM quantity of bundle items that must be selected. Example: 2 + + + + + MAXIMUM quantity of bundle items that may be selected. Example: 4 + + + + + + + + Unique Bundle ID. Example: BNDL-001 + + + + + + + + + + + + Price for Bundled service + + + + + Name of Bundle + + + + + + + + + + + Optional Service(s) List. + + + + + + + + + + Optional Service Bundle(s) List. + + + + + NDC XML SPECIFICATION: FARE XML OBJECT + + + Notice: This is NDC Draft Specification provided for pre-review by the members of the relevant governance groups, it is not provided for implementation in a production environment or considered to be the final schema to support NDC business requirements. The draft schema may, at any time up to final specification submission, undergo changes including, but not limited to, specific elements, element names/labels, annotations or message name as a result of the ongoing quality control process, and comments, which may be received following the pre-review. Implementation of this version is done so at the risk of the implementer or implementing company. + + + + + + A data type for Fare Amount Type list + +Examples: BT (Bulk); IT (Tour Inclusive) + + + + + Additional collection + + + + + + + + + + A data type for Fare Global Indicator contextual list. + + + + + FareByRule, All fares included (EH/TS) + + + + + + Via Atlantic Pacific + + + + + Via Atlantic + + + + + Within Canada. + + + + + Circle trip. + + + + + Within Eastern Hemisphere + + + + + + Far East + + + + + FareByRule - For int'l incl. + AT/PA/WH/CT/RW + + + + + FareByRule for North America incl + US/CA/TB/PV + + + + + Via Pacific + + + + + Via Pacific and via North America + + + + + + Via Polar Route. + + + + + Russia - Area 3 + + + + + Round The World. + + + + + South Atlantic only + + + + + Via South Polar Route + + + + + Trans-border + + + + + Via Siberia. + + + + + Within the United States. + + + + + + Within Western Hemisphere + + + + + + Any Global + + + + + + + + A data type for Fare Application. + + + + + + A data type for Fare Application list constraint. + +Examples: Requested, Ticketed, Other + + + + + + + + + + A data type for Fare Basis Application. + + + + + + + Fare Type Code. + +Examples: +70J, Published Fares +70K, Dynamic Discounted Fares +749, Negotiated Fares +756, One Way Fare +758, Private Fares + +Encoding Scheme: PADIS codeset element 9910 - Fare Qualifier + + + + + Fare Basis Code with optional application. Example: Y26 + + + + + DETAIL FARE BASIS, including code, price class name and application. + NDC Capability Model: FARE - FARE BASIS CODE + +============ +Feature(s) +============ +• Fare Basis Application (usage context) maybe specified (e.g. Requested, Ticketed, Other). + +============ +Metadata +============ +• FareMetadata + + + + + Fare basis code. Example: Y26 + + + + + Fare basis application. +Examples: Requested, Ticketed, Other + + + + + + + + + Fare information. + + + + + FARE definition. + NDC Capability Model: FARE + +============ +Representation(s) +============ +• Core Fare information +• Detail Fare information (Fare Component, Fare Rules) + +============ +Feature(s) +============ +• Fare Indicators for Cat35 Fare, Reissue Pricing, Auto Exchange Pricing +• Fare Code (PADIS codeset element 9910 - Fare Qualifier) + +============ +Metadata +============ +• FareMetadata + + + + + + + + + + + + Fare Detail, including Fare Component and Fare Rules. + + + + + FARE DETAIL definition. + NDC Capability Model: FARE - FARE DETAIL + +============ +Representation(s) +============ +• Fare Component information +• Fare Rules information + +============ +Feature(s) +============ +• Fare Code Indicator to represent pricing method (IATA PADIS Code List for data element 5387 - Price Type Qualifier) +• Price Class association +• Associated Flight Mileage +• Fare Remarks +• Tour Code support (A special code arranged between the travel agency and the sales representative for a particular airline. When the agent enters the tour code into the reservation and ticketing system, it will input certain information onto the ticket. For example, agent commisions, specific fare fules that supercede the published fare rules etc.) + +============ +Metadata +============ +• FareMetadata + + + + + Fare code indicator. Example: 1 (SYSTEM PRICED WITHOUT MANUAL INTERVENTION) + +Encoding Scheme: IATA PADIS Code List for data element 5387 - Price Type Qualifier + + + + + + + A component of this item has been priced using filed fare data; +True = Partially or All Filed +False or missing = All dynamic + + + + + + + + + Passengers associated with the specific Fare Detail instance. Allows the Price breakdown of the fare for the offeritem per passenger. + + + + + + + + + + Total price of all FareComponent prices. Price reflects a per-passenger price referenced within this FareDetail. + + + + + Fare Component information with Price Breakdown. + + + + + + + + + + + Advance Purchase Restriction Value. Example: P7D (7 days) + + + + + + + Restriction context. Example: EARLIEST, LATEST, Other + + + + + + + + + Information relating to published fare rules that define the time prior to the flight departure that a reservation must be made, or a ticket must be issued. + + + + + + Advance reservation/ ticketing value. Example: P14D + + + + + + + Restriction context. Example: EARLIEST, LATEST, Other + + + + + + + + + Advance departure value. Example: P3D (3 days) + + + + + + + Restriction context. Example: EARLIEST, LATEST, Other + + + + + + + + + + + + Corporate Fare information. + + + + + + + + Company profile index associated with this special fare. Example: COM1234 + + + + + + + + + + + + + Contract ID used for pricing special fares. Example: 675124 + + + + + + + + + + + + Corporate account name or ID used for pricing special fares. Example: 675124 + + + + + + + + + + + + + + + + + + Fare Rules. + + + + + FARE RULES definition. + NDC Capability Model: FARE - FARE DETAIL- FARE RULES + +============ +Feature(s) +============ +• Fare Penalty information +• Corporate Fare information +• Advance Ticketing, Purchase, Minimum and Maximum Stay Requirements +• Ticketing Instructions +• Fare Rule Remarks + +============ +Metadata +============ +• FareRuleMetadata + + + + + + + Advance Ticketing, Advance Purchase, Minimum Stay and Maximum Stay. + + + + + + + + + + + + + Ticketing information. + + + + + + When true, the Fare can be Purchased Without Issuing a Ticket. + + + + + + Remarks provided to ensure common understanding between the passenger and an Airline when a fare is restricted as to time of travel, period of validity, voluntary rerouting, or where any other restricting conditions are applicable which are not otherwise clearly evident from other entries + + + + + + + Ticket endorsement text. +Example: NONREF + + + + + + + + + + + Fare Remark(s). + + + + + + + + Minimum Stay Requirement information. + + + + + + Minimum number of stay days permitted in the fare (offer) rules. +Example: 14 + + + + + + + Restriction context. Example: EARLIEST, LATEST, Other + + + + + + + + + Minimum stay represented as a week day number. Example: 1 (Monday) + + + + + + + + + + + + + + Maximum Stay Requirement information. + + + + + + Maximum number of stay days permitted in the fare (offer) rules. + + + + + + + Restriction context. Example: EARLIEST, LATEST, Other + + + + + + + + + Maximum stay represented as a week day number. Example: 1 (Monday) + + + + + + + + + + + + + + Tour Code. Example: ITGF12 + + + + + + + + + + + FARE COMPONENT definition. + + + + + Fare Component-related parameters. + + + + + The total number of fare components within the fare component calculation. Example: 2 + + + + + + + Fare Component Pricing information. + + + + + Fare Basis information, including Fare Basis Code, Fare Rule Remarks and Fare Basis City Pair. + + + + + + + + + Reservation Booking Designator or Booking Class e.g. T + + + + + + + + + + + + + + + + + + + + + + + Flight Slice ON Point. Example: ORD + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + Flight Slice OFF Point. Example: NYC + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + + + + + Fare Rule Subset for this Fare Component. + +Note: For full fare rule retrieval, use the FareRulesRQ/RS message pair. + NDC Capability Model: FARE - FARE RULES - REMARKS + +============ +Description +============ +Fare Rule collection (group) for an associated Fare Component. + +============ +Representation(s) +============ +• Scheme: IATA PADIS codeset FRC-Fare Rule Category + +============ +Feature(s) +============ +• Fare Basis Code-associated Fare Rule Category Code and Description. + +============ +Metadata +============ +• FareRuleMetadata + + + + + + Category-Related Fare Rule Subset. + + + + + + Fare rule category (associated with FareBasisCode.) +Example: ACC (Accompanied Travel) + +Encoding Scheme: IATA PADIS codeset FRC-Fare Rule Category + + + + + Fare Rule Text. + + + + + + + + + + + + Identified published fare. Origin and destination city codes and two character designator of fare owning airline associated with Fare Basis Code. + +Example: MIANCEDL + + + + + + Fare Filing information. As may be applicable in filed fares scenarios + + + + + FARE FILING definition. + + + + + Filed fare amount. +Example: 2385 USD + +Note: This contains the originally filed base fare amount. + + + + + Fare neutral unit of construction amount. +Example: 4327 + +Note: This contains the fare amount expressed in Neutral Units of Construction (NUC) values rather than in any currency for provisional billing purposes by airline revenue accounting departments. + + + + + Applicable exchange rate. Example: 1 : 0.895 + + + + + Ticket masked value. Examples: IT, BT + + + + + Filed fare information that may contain specific indicators applicable to the use of filed fares scenarios. + + + + + + + + File Fare definition. + + + + + Fare global indicator. +Example: AT (Via Atlantic) + + + + + + + + + + + + When true, this is a Cat35 C-Type Net Fare. + + + + + + Filed fare information that may contain specific indicators applicable to the use of filed fares scenarios. + + + + + + + + + + + The identifier reflecting the method of pricing for the transaction as entered on the ticket. + + 0 = Indicates that a fare has been system computer priced and that no change has been made to the + reservation between pricing and ticket issuance with no manipulation of the fare, or any data filed with + the fare, including taxes, fees and charges and applicable standard fare conditions in accordance with + Tariff Resolutions 100 and 101 with the exception of the Tour Code. +1 = Identifies a manually built fare +2 = Identifies a fare that was auto-priced, but baggage and/or TFC data has been manipulated. + + + + + Fare Qualifier Code(s). + + + + + + + + + + Unique Fare Reference Key. Example: PQ123456 + + + + + + + + + + + + Fare Rule Category. Example: ACC (Accompanied TravelL) + +Encoding Scheme: IATA PADIS code list FRC-Fare Rule Category + + + + + Fare Text Indicator. Examples: A (Full Text), B (Mini Rule) + + + + + + + + + + + + FARE BASE PRICE definition. + + + + + Total price amount. + +Notes: +1. This is typically the lowest price for this alternate lead shopping date. +2. If expressed in currency, this price should include base price, taxes and fees/ surcharges. + + + + + + + + + + + + + + Total Base Fare Amount. Example: 200000 + +Note: This includes surcharges (if applicable). + + + + + + Applicable Surcharge(s). + + + + + + Surcharge detail. + + + + + + + + + AWARD (Redemption Unit-based) Pricing information. + + + + + PARTIAL CURRENCY and AWARD Pricing Combination information. + + + + + + + + FARE PRICE DETAIL definition. + + + + + + + Ticket Tax/fee/charge details to indicate taxes that apply to country of commencement of travel and routing. + + + + + + Actual travel date requested by Traveler. Example: 2017-01-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + Alignment with the actual travel date requested by the Traveler. Example: ADA (AFTER DATE BASED ON ARRIVAL) + +Encoding Scheme: IATA PADIS code list CSD-Calendar Shopping Date + + + + + + + + + + NDC XML SPECIFICATION: FLIGHT XML OBJECT + + + + + + A data type for Class of Service Optional Associations. + + + + + + + + + + + + + A data type for Class of Service Association Type Name. + + + + + + A data type for Flight Class of Service encoding constraint. + + + + + + + + A data type for Flight Duration Application contextual list. +Examples: FlightTime, ConnectionTime, StopTime, TotalJourneyTime + + + + + + + + + + + + A data type for Flight Duration Application. +Examples: FlightTime, ConnectionTime, StopTime, TotalJourneyTime + + + + + + A data type for Flight Segment Type list constraint. + + + + + + + + + + + + A data type for Flight Mileage Application. + + + + + + + Class of Service Associations. + + + + + + + + OtherClass of Service Associations. + + + + + Other Association Detail. + +Note: Includes an association type choice (e.g. MediaGroup) and an instance association value (e.g. mediagrp1). + + + + + + Named association type. Examples: Equipment, MediaGroup + + + + + Associated object instance value. Example: mediagrp1 + + + + + + + + + + + Flight Number. Example: 1234, or OPEN, or ARNK + + + + + + + Flight Operational Suffix + + + + + + + + + + + + + + + Identifies a flight number (1 to 4 numbers) or OPEN or ARNK. + + + + + + + + + + + + Used in lieu of a flight number when a specific flight number is unknown but service is present. + + + + + Used in lieu of a flight number when surface transportation is used when there is a break in the continuity of the flight itinerary. + + + + + + + + + + Class of Service. Example: T + + + + + A data type for Class of Service Core. + +Class of service code. +Example: B + + + + + Class of Service Code. Example: B + + + + + + + Inidcates how many seats are still available in this class of service. + + + + + + + + + Cabin Class Marketing Name. Example: Premium Economy + + + + + + + Designator code for the cabin. Example: Y + + + + + + + + + Fare basis code. Example: Y26CH + + + + + + + + + Stop Location(s). + + +Note: This contains information about the stops for the specified flight number. + + + + + FLIGHT STOP LOCATION definition. + + + + + Stop Location detail. + + + + + + + Airport Name. Example: Tampa International + + + + + Stop Arrival date. Example: 2017-01-14 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + Arrival time. Example: 09:15 + +Encoding Scheme: ISO 8601 Military/ 24 Hour Format (HH:MM) + + + + + Scheduled Departure Date. Example: 2017-01-13 + +Note: This is the date and time of departure in GMT from the unticketed point. + + + + + Departure time. Example: 09:15 + +Encoding Scheme: ISO 8601 Military/ 24 Hour Format (HH:MM) + + + + + + Flight Stop Groundtime. +Example: PT5M (45 minutes) + + + + + + + + + + When true, there has been a Change of Gauge. + + + + + + + Arrival (destination) Airport, Date and Time information. + + + + + Airport or a city code. Use a three letter location identifier assigned according to the IATA Resolution 763. Refer to IATA Airline Coding Directory . Example: TPA + + + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Departure (origin) Airport, Date and Time information. + + + + + + + + + + Departure (origin) Airport Code. + + + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Departure Date. Example: 2017-01-11 + + + + + FLIGHT DEPARTURE definition. + + + + + Airport or a city code. Use a three letter location identifier assigned according to the IATA Resolution 763. Refer to IATA Airline Coding Directory . Example: TPA + + + + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Departure date. Example: 2017-01-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + Departure time. Example: 09:15 + +Encoding Scheme: ISO 8601 Military/ 24 Hour Format (HH:MM) + + + + + Airport Name. Example: Tampa International + + + + + Airport terminal name and gate. +Refer to IATA SSIM Appendix D for terminal codes and terminal names. + + + + + + Terminal name or ID. Example: Terminal C + + + + + Terminal Gate Number. Example: C39 + + + + + + + + + + + FLIGHT ARRIVAL definition. + + + + + Airport or a city code. Use a three letter location identifier assigned according to the IATA Resolution 763. Refer to IATA Airline Coding Directory . Example: TPA + + + + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Arrival date. Example: 2017-01-14 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + Arrival time. Example: 09:15 + +Encoding Scheme: ISO 8601 Military/ 24 Hour Format (HH:MM) + + + + + Number of days between arrival and departure. Example: 1 + + + + + Airport Name. Example: Geneva International Airport + + + + + Airport terminal name and gate. +Refer to IATA SSIM Appendix D for terminal codes and terminal names. + + + + + + Terminal name or ID. Example: Terminal C + + + + + Terminal Gate Number. Example: C39 + + + + + + + + + + + + A data type for a Flight. + + + + + + + Flight origin/ destination information. + + + + + + + Flight-related boolean indicators. + + + + + When true, this flight OD pair should be priced. + + + + + When true, there are one or more connections for this flight. + + + + + When true, an electronic ticket may be issued. + + + + + When true, the fare can be purchased without issuing a ticket. + + + + + + + Current status of the Order Item and related indicators. + + + + + + + Current Order Item status. Example: OK (Confirmed) Encoding Scheme: IATA Padis Codeset - List for data element 4405 (Status, coded) + + + + + + + + When true, the order item cannot be fulfilled due to an aircraft change. + + + + + + + When true, the order item cannot be fulfilled due to a flight schedule change. + + + + + + + + + + Marketing Carrier information. + +Notes: This is the carrier that sells with its own code as part of a code share agreement on a flight that is actually operated by another carrier. + + + + + Operating Carrier Information. + +Operating Carrier is the carrier that operates a flight with a reference to its own prime flight number. + +Note: Operating Carrier may be different from a Marketing Carrier(s), if the flight is actually marketed by another carrier(s) within a codeshare agreement. + +Operating Carrier may not be the AOC holder, in which case, and wherever required, this will need to be disclosed to the customer. + + + + + + + + + + + + + + + + + Flight Details. + + + + + + + + + + + + FLIGHT DETAIL definition. + + + + + + + + Flight Stop Quantity and Location(s). + + + + + + Stop Quantity. Example: 1 + + + + + + + + + + Tour Operator Flight ID. + +Note: This is an ID for the flight as represented by a Tour Operator. This flight is not necessarily in the inventory of an airline as it is a code created by tour operators. + + + + + + + + A data type for a Flight with no O/D information. + +Flight origin/ destination information. + + + + + + + + Marketing Carrier information. + +Notes: This is the carrier that sells with its own code as part of a code share agreement on a flight that is actually operated by another carrier. + + + + + Aircraft Equipment. + +Note: Two instances of aircraft equipment may be specified if there is a change of gauge. + + + + + Operating Carrier Information. + +Operating Carrier is the carrier that operates a flight with a reference to its own prime flight number. + +Note: Operating Carrier may be different from a Marketing Carrier(s), if the flight is actually marketed by another carrier(s) within a codeshare agreement. + +Operating Carrier may not be the AOC holder, in which case, and wherever required, this will need to be disclosed to the customer. + + + + + + + + + + + + + + + + Flight Details. + + + + + + + + + + Flight Distance with application. + + + + + FLIGHT DISTANCE with Application definition. + + + + + Flight distance value and distance unit of measure. +Example: 818, 5467 + + + + + Flight Distance Unit of Measure. +Examples: Kilometers, Miles + + + + + Flight Distance Application. +Examples: FlightSegment, TotalJourney + + + + + + + + Flight Duration with application. + + + + + FLIGHT DURATION with Application definition. + + + + + Flight Segment Duration. +Example: PT6H45M (six hours and forty-five minutes) + +Note: This is the in-flight time duration associated with this segment. Stop duration is specified in the Stops node. + + + + + Flight Duration Application. +Examples: FlightTime, ConnectionTime, TotalJourneyTime + + + + + + + + Total Journey time duration and flight distance. + + + + + TOTAL JOURNEY TIME/ DISTANCE definition. + + + + + Total Journey Time. Example: PT7H45M (7 hours and 45 minutes) + +Note: Total journey time includes the combined air time, connection time and/ or stop information for all specified flight segments. + + + + + Total Journey distance value and distance unit of measurement. + +Note: Total Journey distance includes the combined distances for all specified flight segments. + + + + + + Total Flight Distance Value and distance unit of measure. Example: 8,5467 + + + + + Flight Distance Unit of Measure. Examples: Kilometers, Miles + + + + + + + + + + + + + Flight Status. +Examples: SO, Flight Canceled + +Encoding Scheme: IATA Padis Codeset - List for data element 1245 - Status Indicator + + + + + + Day of the week when a Flight operates +Examples: +1234567 (MON through SUN) +123 (MON, TUE, WED) +467 (THU, FRI, SAT) + + + + + FLIGHT OPERATION FREQUENCY definition. + + + + + + + + On-time performance for this flight Segment. + + + + + Accuracy percentage of on time performance of a leg. + + + + + Month and year for which the on-time performance has been calculated. + + + + + Used if unable to provide information or is not applicable. + + + + + The percentage of arrivals that were more than 30 minutes late. + + + + + The percentage of cancellations. + + + + + When true, the flight was late more than 30 minutes of scheduled arrival more than 50 percent of the time. + + + + + + + Used for percentage values + + + + + + + + + + Flight Mileage with application. + + + + + FLIGHT MILEAGE QUANTITY with Application definition. + + + + + Flight Mileage Value. Example: 2143 + + + + + Flight Mileage Application. +Examples: Segment, Trip, Other + + + + + + + + Flight Reservation (booking/ order) date and time. + + + + + + Reservation (order/ booking) timestamp. Example: 2017-01-13T13:20:00 + + + + + Reservation (order/ booking) Date. Example: 2017-01-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + + + Order Reservation (booking) Time. Example: 13:20 + + + + + + + + + + + + + Flight segment type. Example: P (PASSIVE) + +Encoding Scheme: IATA PADIS 1.4 Codeset FST - Flight Segment Type + + + + + + + The IATA aircraft type 3 character code; use SSIM Appendix A. Example:318. + + + + + + + + + + The IATA aircraft type 3 character code; use SSIM Appendix A. Example:318. + + + + + + + + + + AIRCRAFT CORE representation. + + + + + Equipment Code. Example: 737 + +Encoding Scheme: IATA/ A4A Equipment Code + + + + + + When TUE, this aircraft equipment information is associated with a flight change of gauge. + + + + + + + AIRCRAFT SUMMARY representation. + + + + + + + Equipment name. Example: Boeing 737-800 + + + + + Airline-specific aircraft equipment code. +Example: 737-800 + + + + + + + + + Aircraft Equipment. + + + + + + AIRCRAFT EQUIPMENT CODE QUERY representation. + + + + + The IATA aircraft type 3 character code; use SSIM Appendix A. Example:318. + + + + + + + + AIRCRAFT EQUIPMENT CODE QUERY representation. + + + + + Aircraft Equipment Tail Number. + + + + + + + + AIRCRAFT FEATURES QUERY representation. + + + + + Aircraft feature detail. + +Encoding Scheme: IATA PADIS Codeset - List for data element 9932 - Aircraft Feature Type + + + + + + + + + + + + + + + + Cabin type. Examples: First Class, Business Class + +Encoding Scheme: PADIS codeset element 9873 - Cabin Class of Service + + + + + + + + Cabin class marketing name. Example: Premium Economy + + + + + + + + + + + A data type for Cabin Core. + +Cabin code. +Example: F + + + + + Designator code for the cabin. Example: Y + + + + + + + When true indicates that it applies to all Cabins, otherwise the specified Cabin applies. + + + + + + + + + Cabin Marketing Name. Example: Premium Economy + + + + + + + + + + + + + Aircraft Cabin information. + + + + + + + + + ITINERARY - Existing (known) Flight Information. + + + + + + + + + + + + + + + + Origin/ Destination information. Contains a list of all Flight element that are part of that OD. + + + + + + + + + + + + + + + ORIGIN/ DESTINATION definition. + + + + + Departure Airport Location code. Example: TPA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + Airport or a city code. Use a three letter location identifier assigned according to the IATA Resolution 763. Refer to IATA Airline Coding Directory . Example: TPA + + + + + + + A globally unique identifier for this OriginDestination instance. Example: origDest1 + + + + + + + NDC XML SPECIFICATION: XML Object Keys and Associations shared by all NDC Domains. + + + Notice: This is NDC Draft Specification provided for pre-review by the members of the relevant governance groups, it is not provided for implementation in a production environment or considered to be the final schema to support NDC business requirements. The draft schema may, at any time up to final specification submission, undergo changes including, but not limited to, specific elements, element names/labels, annotations or message name as a result of the ongoing quality control process, and comments, which may be received following the pre-review. Implementation of this version is done so at the risk of the implementer or implementing company. + + + + + + The airline-assigned unique Offer Item ID. Example: OFFER769-A850-4EC4-8F46-02293F72D7E6 + + + + + The airline-assigned unique Order Item ID. Example: ORD769-A850-4EC4-8F46-02293F72D7E6 + + + + + A data type for an order or offer related ID. + +Example: ORDER-c98c-4759-a20b-01 + + + + + + + Airline designator or CRS code of the owner/ assigner of the Offer ID, typically used for offer ordering purposes. Example: UA, BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline or CRS Designator Code + + + + + Deep linking into another site to complete the transaction. + + + + + The POA OrderID should only go to the ORA, not back to the seller. +1. ORA +2. POA + + + + + + + + + + + + + + + + Association to Carry-on Allowance, Checked Bag Allowance and/or Baggage Disclosure. + + + + + + + + + + + + + A globally unique identifier for this Baggage Disclosure instance. Example: bdisclosure1 + + + + + Association to multiple Baggage Disclosure instance(s). Example: bdisclosure1 bdisclosure2 + + + + + + Association to multiple Checked Bag Allowance instance(s). Example: checked1 checked2 + + + + + + Association to multiple Carry-On Allowance instance(s). Example: carryon1 carryon2 + + + + + + A globally unique identifier for this Equivalent ID instance. Example: equiv1 + +Note: This is an equivalent (third-party) ID for the Airline-specified ID. + + + + + + A globally unique identifier for this Origin/Destination instance. Example: od1 + + + + + Association to one Origin/Destination instance. Example: od1 + + + + + Association to multiple Origin/Destination instance(s). Example: od1 od2 + + + + + + Association to multiple Flight instance(s). Example: flight1 flight2 + +Note: Flight Slice On and Off Board Points may also be specified. + + + + + + + Flight slice on point. Example: TPA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + Flight slice off point. Example: LHR + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + + + Association to to single Flight segment instance(s). Example: segment1 + + + + + + + + + + To indicate married segment group number. +Exmple 5 + + + + + + + Object association(s) between this object and any other object or metadata instance(s). + + + + + + + A globally unique identifier for this Flight Segment instance. Example: segment1 + + + + + Association to multiple Flight Segment instance(s). Example: segment1 segment2 + +Note: Flight Slice On and Off Board Points may also be specified. + + + + + + + Flight slice on point. Example: TPA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + Flight slice off point. Example: LHR + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + + + + Association to one Group instance. Example: group1 + + + + + + Association to one Media Group instance. Example: mediagrp1 + + + + + Association to one Media ID or Link instance. Example: media1 + + + + + + Association to multiple Offer instance(s). Example: offer 1 offer2 + + + + + + Association to multiple Offer/ Offer Item Instruction instance(s). Example: instruction1 instruction2 + + + + + + Association to one Offer/ Offer Item Penalty instance. Example: penalty1 + + + + + + Association to multiple Offer/ Offer Item Term instance(s). Example: term 1 term2 + + + + + + Association to one or multiple Passenger instances. Example: pax1 pax2 + + + + + Association to multiple Passenger instance(s). Example: pax1 pax2 + + + + + + Association to one Price Class instance. Example: pclass1 + + + + + + Association to one Seat instance. Example: seat1 + + + + + + Association to one Service instance. Example: srvc1 + + + + + Association to multiple Optional Service instance(s). Example: srvc1 srvc2 + + + + + + Association to one Service Bundle instance. Example: sbundle1 + + + + + + NDC XML SPECIFICATION: METADATA ASSOCIATED WITH XML BUSINESS OBJECTS + + + Notice: This is NDC Draft Specification provided for pre-review by the members of the relevant governance groups, it is not provided for implementation in a production environment or considered to be the final schema to support NDC business requirements. The draft schema may, at any time up to final specification submission, undergo changes including, but not limited to, specific elements, element names/labels, annotations or message name as a result of the ongoing quality control process, and comments, which may be received following the pre-review. Implementation of this version is done so at the risk of the implementer or implementing company. + + + + + Pre-defined and Augmented ADDRESS Metadata. + + + + + + ADDRESS Metadata. + + + + + + + + ADDRESS Metadata. + + + + + Pre-defined and Augmented AIRCRAFT Metadata. + + + + + + AIRCRAFT Metadata. + + + + + + + + AIRCRAFT Metadata. + + + + + Pre-defined and Augmented AIRPORT Metadata. + + + + + + + + + + AIRPORT Metadata. + + + + + Pre-defined and Augmented CITY Metadata. + + + + + + + + + + CITY Metadata. + + + + + Pre-defined and Augmented CODESET Metadata. + + + + + + + + + + PADIS/ CODESET Metadata. + + + + + Pre-defined and Augmented CONTACT Metadata. + + + + + + + + + + CONTACT Metadata. + + + + + Pre-defined and Augmented CONTENT Metadata. + + + + + + + + + + CONTENT SOURCE Metadata. + + + + + Pre-defined and Augmented COUNTRY Metadata. + + + + + + + + + + COUNTRY Metadata. + + + + + Pre-defined and Augmented CURRENCY Metadata. + + + + + + + + + + CURRENCY Metadata. + + + + + + + + + + Pre-defined and Augmented DESCRIPTION Metadata. + + + + + + + + + + DESCRIPTION Metadata. + + + + + Pre-defined and Augmented EQUIVALENT ID Metadata. + + + + + + + + + + EQUIVALENT IDENTIFIER Metadata. + + + + + Pre-defined and Augmented LANGUAGE Metadata. + + + + + + + + + + LANGUAGE Metadata. + + + + + Pre-defined and Augmented MEDIA Metadata. + + + + + + MEDIA Metadata Detail + + + + + + + + MEDIA Metadata. + + + + + Pre-defined and Augmented PAYMENT CARD Metadata. + + + + + + + + + + PAYMENT CARD Metadata. + + + + + Pre-defined and Augmented PAYMENT FORM Metadata. + + + + + + + + + + PAYMENT FORM Metadata. + + + + + Pre-defined and Augmented PRICE Metadata. + + + + + + + + + + PRICE Metadata. + + + + + Pre-defined and Augmented RULE Metadata. + + + + + + + + + + RULE Metadata. + + + + + Pre-defined and Augmented STATE/ PROVINCE Metadata. + + + + + + + + + + STATE/ PROVINCE Metadata. + + + + + Pre-defined and Augmented ZONE Metadata. + + + + + + + + + + ZONE Metadata. + + + + + + A data type for ADDRESS Metadata. + + + + + + + + type of address eg Billing, Business, Home + + + + + list of address fields required by vendor + + + + + + + + + + If this field is required then true, otherwise false. + + + + + + + + + + + + + + + + A data type for AIRCRAFT Metadata. + + + + + + + Aircraft tail number. Example: N387SW + + + + + Aircraft name.Example: N387SW + + + + + + + + + A data type for AIRPORT Metadata. + + + + + + + + Direction(s). + + + + + + + + + + + + + + + A data type for CITY Metadata. + + + + + + + + + + + + + A data type for PADIS/ CODESET Metadata. + + + + + + + Codeset Source. + + + + + + Owner Entity ID. Example: BA + + + + + + + Owner Name. Example: British Airways + + + + + + + + + + + + Codeset file or resource name. Example: PADIS Codeset + + + + + Codeset version. Example: 14 + + + + + + + + Other (alternate) Language Encoding and Code Description. + + + + + + + Codeset table or list name. Example: Data Element 9972-Originator Type + + + + + + + + + + + + A data type for CONTACT Metadata. + + + + + + + + A data type for CONTENT SOURCE Metadata. + + + + + + + + A data type for COUNTRY Metadata. + + + + + + + ICAO location code. +Example: K (CONTIGUOUS UNITED STATES) + + + + + Country name. +Example: United States + + + + + + + + + + A data type for CURRENCY Metadata. + + + + + + + Currency application. Example: Actual Pricing, Display Currency, Requested Pricing + + + + + Number of decimal places. Example: 2. Note this is the number of decimal places normally used when displaying amounts in this currency + + + + + Currency name. Example: US Dollars + + + + + + + + + A data type for DESCRIPTION Metadata. + + + + + + + Description Application. Examples: Marketing, TermsAndConditions + + + + + Description topic. Example: Relax in the Lounge + + + + + Hint. Example: Relax in the Lounge + + + + + Description copyright. Example: (c) ABC CO + + + + + Description Sequence (order) Number. Example: 1 + + + + + + + + + A data type for EQUIVALENT IDENTIFIER Metadata. + + + + + + + Equivalent Identifier detail. + + + + + + + Equivalent ID value. Example: MYSRVC123 + + + + + Airline designator or CRS code of the owner/ assigner of the Offer ID, typically used for offer ordering purposes. Example: UA, BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline or CRS Designator Code + + + + + + + + + + + + + A data type for LANGUAGE Metadata. + + + + + + + Language application. Examples: Display, Requested, Spoken, Written + + + + + Language encoding. Examples: fr + +Encoding Scheme: ISO 639-1 Language Code + + + + + NLS Language encoding. Examples: en-US + +Encoding Scheme: Microsoft National Language Support (NLS) Code + + + + + Language name. Example: English, United States + + + + + + + + + A data type for PAYMENT CARD Metadata. + + + + + Card Schema code eg VI, AX, VD + + + + + Card Schema name eg Visa, American Express, Visa Debit + + + + + Card Type eg Credit, Debit + + + + + List of fields required for this card + + + + + + + + + + If this field is required then true, otherwise false. + + + + + + + + + + + + card surcharge information + + + + + + + + + + + + Object association(s) between this object and any object instance(s). + + + + + A globally unique identifier for this Metadata instance. + + + + + + A data type for PAYMENT FORM Metadata. + + + + + + + Customer Commercial Account. + +Note: This is a reference number to a commercial account used to further identify the holder of the credit card. + + + + + + + + + + Extended Payment Month Quantity. Example: 3 + +Notes: + +1. This is a code to indicate the number of months over which the customer wishes to pay where the credit card issuer permits. +2. This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of this capability is not dictated by this specification. + + + + + Unique Transaction Information. + +Note: This may contain unique transaction information supplied to the airline/system provider by the credit card company. + + + + + Corporate Contract Code. Example: IBM1234 + +Note: This is used to indicate whether the purchase is on behalf of a corporate client that has a contract ith the ticketing agency for the purchase of transportation and related services. + + + + + + + + + A data type for PENALTY Metadata. + + + + + + + + A data type for PRICE Metadata. + + + + + + + + A data type for RULE Metadata. + + + + + + + Unique Rule ID which was applied during transaction processing. Example: PRICERULE001 Note: Optional rule context and name may also be specified. + + + + + + + + + + Rule name. Example: Rule001 + + + + + Rule status. Examples: ActionRequired, RuleExecuted, Other + + + + + + + + + + Rule Value(s). + + + + + + Rule value detail. + + + + + + + Business rule instruction. +Example: [NodePath.r1] {EQ('FR')} [NodePath.r2]{EQ(true)} + + + + + + + + + + + + + + + + + + + + + A data type for STATE/ PROVINCE Metadata. + + + + + + + + + + + + A data type for ZONE Metadata. + + + + + + + + + + + + + Baggage-related Metadata, including Checked Bag, Carry-on Baggage, Baggage Disclosure, Baggage Detail and Baggage Query. + + + + + + + + + + + + + + Flight-related Metadata, including Flight and Itinerary. + + + + + + + + + + + Location-related Metadata, including Directions. + + + + + + + + + + Offer-related Metadata, including Disclosure, General, Instructions, Penalty, Status and Terms. + + + + + + + + + + + + + + Pricing-related Metadata, including Discount. + + + + + + + + + + Qualifier choices. + +These capabilities may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of the capability is not dictated by this specification. + + + + + + + + Contains card type, and Issuer Identification Number. + + + + + + + + + + Contains elements identifying eligibility for special pricing, which may be private or negotiated. + +Notes: +1. Supports pricing discounts and/ or other benefits for Travelers affiliated with companies with private fare and/ or negotiated rate contracts. + +2. Private Fares apply to ALL Travelers. + + + + + + + + + + Seat-related Metadata, including Seat and Seat Map. + + + + + + + + + + + Shopping Metadata choices. + + + + + + + + + Location-related Metadata, including Directions. + + + + + + Pricing-related Metadata, including Discount. + + + + + + + + + + + BAGGAGE DETAIL Metadata. + + + + + Pre-defined and Augmented BAGGAGE DISCLOSURE Metadata. + + + + + + + + + + BAGGAGE DISCLOSURE Metadata. + + + + + BAGGAGE QUERY Metadata. + + + + + Pre-defined and Augmented CARRY-ON BAGGAGE ALLOWANCE Metadata. + + + + + + + + + + CARRY-ON BAGGAGE ALLOWANCE Metadata. + + + + + Pre-defined and Augmented CHECKED BAG ALLOWANCE Metadata. + + + + + + + + + + CHECKED BAG ALLOWANCE Metadata. + + + + + + Pre-defined and Augmented FLIGHT Metadata. + + + + + + + + + + FLIGHT Metadata. + + + + + + + + + + Pre-defined and Augmented ITINERARY Metadata. + + + + + + Pre-defined and Augmented DIRECTIONS Metadata. + + + + + + + + + + DIRECTIONS Metadata. + + + + + + Pre-defined and Augmented DISCLOSURE Metadata. + + + + + + DISCLOSURE Metadata Detail + + + + + + + + DISCLOSURE Metadata. + + + + + Pre-defined and Augmented OFFER ITEM INSTRUCTION Metadata. + + + + + + + + + + OFFER ITEM INSTRUCTION Metadata. + + + + + Pre-defined and Augmented OFFER ITEM Metadata. + + + + + + OFFER ITEM Metadata. + + + + + + + + OFFER ITEM Metadata. + + + + + Pre-defined and Augmented OFFER ITEM PENALTY Metadata. + + + + + + + + + + OFFER ITEM PENALTY Metadata. + + + + + Pre-defined and Augmented OFFER ITEM TERMS Metadata. + + + + + + + + + + OFFER ITEM TERMS Metadata. + + + + + + Pre-defined and Augmented DISCOUNT Metadata. + + + + + + DISCLOSURE Metadata Detail + + + + + + + + DISCOUNT Metadata. + + + + + + Pre-defined and Augmented SEAT Metadata. + + + + + + + + + + SEAT Metadata. + + + + + Pre-defined and Augmented SEAT MAP Metadata. + + + + + + + + + + SEAT MAP Metadata. + + + + + + CARRY-ON BAG Metadata definition. + + + + + + + + CHECKED BAG Metadata definition. + + + + + + + + BAGGAGE DETAIL Metadata definition. + + + + + + + + Tariff. +Example: PF17 + + + + + + + Fare Type. + + + + + + + + + Fare rule code. +Example: EU (ECONOMY UNRESTRICTED) + + + + + Fare category. +Example: CATEGORY 35 + + + + + + + + + BAGGAGE DISCLOSURE Metadata definition. + + + + + + + + BAGGAGE QUERY Metadata definition. + + + + + + + Ticket issue location. +Example: MIA + For maximum interoperability, it is recommended that IATA (three character) Airport/ City Code values be used. Use an IATA code or a proprietary string value. +http://www.iata.org/publications/Pages/code-search.aspx + + + + + Ticket issue country. +Example: CA + + + + + Total number of passengers of all types for the entire itinerary. Example: 4 + + + + + Total price for the entire itinerary for all passengers of all types. Example: 320000 + + + + + + + + + DIRECTIONS Metadata definition. + + + + + + + + DISCLOSURE Metadata definition. + + + + + + + Disclosure creation timestamp. Example: 2017-01-13T13:59:38Z + + + + + + + + + FLIGHT Metadata definition. + + + + + + + Reservation system action code. Example: HK + + + + + A unique flight segment reference that may be used when binding request/ response messages. + + + + + + + + Meal(s) Served. + + + + + + Meal served code. Example: B (Breakfast) + +Encoding Scheme: IATA Padis Codeset - List for data element 7161 - Special Service, Coded + + + + + + + + + + + + + + ITINERARY Metadata definition. + + + + + + + Reservation system action code. Example: HK + + + + + + + + + MEDIA Metadata definition. + + + + + + + Media application. Example: Marketing + + + + + Media object caption. Examples: (image) PREMIUM SEAT, (video) See the New Terminal +(file) Download Terminal Map, (link) Baggage Information + + + + + Media object tip. Example: Envoy Class Seat + +Note: This is typically used in a client GUI, e.g. a mouseover tip. + + + + + Media Dimensions metadata. + + + + + + Dimension Unit of Measure. Example: Pixels + + + + + Height in specified units. Example: 120 + + + + + Width in specified units. Example: 120 + + + + + "The “Format” is the “CREATIVE UNIT NAME”, Example: (Billboard, Filmstrip, Portrait, Pushdown, Medium Rectangle, Rectangle, Half Page ,…) IATA codeset MDF. Please refer to http://www.iab.com/wp-content/uploads/2015/11/IAB_Display_Mobile_Creative_Guidelines_HTML5_2015.pdf" + + + + + + + + Media Source metadata. + + + + + + Media Code. Example: IMG123 + + + + + Media version. Example: 14 + + + + + The media object file name. Example: ThisPlane.swf + + + + + Image barcode symbology applied. Example: PDF417 + + + + + Media object copyright. Example: © COPYRIGHT IATA 2014 + + + + + + + + + + + + OFFER ITEM METADATA definition. + + + + + + + Attributes and S5/ S7 Diagnostics. + + + + + + + + + + + Offer Incentive(s). + + + + + + + + + + Offer Match(s). + + + + + + Offer Match detail. + + + + + + + + + + + + + Offer Terms. + + + + + + + + + + Offer Time Limits. + + + + + + + + + + Offer Rules. + + + + + + + + + + Offer Status. Example: NN (Requested) + + + + + + + + + OFFER ITEM INSTRUCTIONS Metadata definition. + + + + + + + + OFFER ITEM TERMS Metadata definition. + + + + + + + + + SEAT Metadata definition. + + + + + + + Seat status. +Examples: +SA (Seats are available) +WO (Seats waitlist open for segment) +WC (Seats waitlist closed for segment) +OR (Seats on request only to airline) + +Encoding Scheme: IATA PADIS Code List for data element 9865 - Seat Occupation + + + + + + + + + SEAT MAP Metadata definition. + + + + + + + + + Pre-defined PASSENGER Metadata. + + + + + + PASSENGER Metadata definition. + + + + + + + Traveler Name Detail, including Given Name Prefix, Title Suffix, Surname Prefix and Surname Suffix. + + + + + + Given name prefix. Example: MR + + + + + Title degree or honors. Examples: Ph.D., M.D. + + + + + Surname prefix. Examples: van der, von, de + + + + + Surname suffixes and letters. Examples: Jr., Sr., III, Ret., Esq. + + + + + + + + + + + + + NDC XML SPECIFICATION: OFFER XML OBJECT + + + Notice: This is NDC Draft Specification provided for pre-review by the members of the relevant governance groups, it is not provided for implementation in a production environment or considered to be the final schema to support NDC business requirements. The draft schema may, at any time up to final specification submission, undergo changes including, but not limited to, specific elements, element names/labels, annotations or message name as a result of the ongoing quality control process, and comments, which may be received following the pre-review. Implementation of this version is done so at the risk of the implementer or implementing company. + + + + + + + A data type for Offer Match Application. + + + + + + + + + + A data type for Offer Match Results. + +Examples: Full, None, Partial, Others + + + + + + A data type for Offer Match Results. + + + + + + + + + + + A data type for Offer Match Results. + +Examples: Full, None, Partial, Others + + + + + + + A data type for Other Offer Optional Associations. + + + + + + + + + + + + + + + + + A data type Other Offer Association Type Name. + + + + + + + Applicable Flight(s). + + + + + + + + + + Associated Optional Service(s). + + + + + Associated Passengers. + +Note: Includes Passenger and/or PTC Passenger association. + + + + + Flight that the offer applies to. + + + + + + When true, this Simple Fare Offer applies to all specified flight Segments. + + + + + Association to to single Flight segment instance(s). Example: segment1 + + + + + + + When true, this Baggage Offer applies to all specified flight Origin/ Destination Pairs. + + + + + + + + When true, this Simple Fare Offer applies to all specified flights. + + + + + + + + + Baggage Offer Association definition. + + + + + + + + + + + + + Optional Service(s) included with Fare. + + + + + Associated Media definition. + + + + + + Media Item detail. + + + + + + + Associated Media URL. + + + + + + + + + + Offer Detail Association(s). + + + + + Other Association(s). + + + + + Shopping Offer Association(s). + + + + + + + + + + Shopping Offer Association(s) definition. + + + + + + Associated Shoppers. Note: Includes Anonymous, Recognized and/or PTC shopper association. + + + + + + Associated Flight(s). + + + + + Associated Price Class information. + + + + + + + + + + Baggage Detail Associations. + + + + + Offer Detail Association(s). + + + + + Associated Service(s). + + + + + + Associated Service. + + + + + + + + + + + + + + Associated Media. + + + + + Other Association(s). + + + + + + + Associated Offer Detail definition. + + + + + + + + + + Other, Implementer-specified, Offer Associations. + + + + + Other Association Detail. + +Note: Includes an association type choice (e.g. MediaGroup) and an instance association value (e.g. mediagrp1). + + + + + + Named association type. Examples: CarryOnAllowance, MediaGroup + + + + + Associated object instance value. Example: mediagrp1 + + + + + + + + + + Priced Flight Offer Association definition. + + + + + + + Associated Price Class information. + + + + + + + + + + + Included Optional Service(s). + + + + + + + + + Offer-Associated Optional Services definition. + + + + + + + + + Associated Shopper(s) definition. + + + + + + + + When true, this Offer applies to all specified shoppers. + + + + + + + Associated Passenger(s) definition. + + + + + When true, this Offer applies to all specified Passengers. + + + + + Association to multiple Passenger instance(s). Example: Passenger1 Passenger2 + +Note: May be Passenger (by PTC) instance(s). + + + + + + + + + Offer definition. + + + + + Offer-wide parameters, including Traveler Applicability; Total Offer Quantity; Passenger Pricing Method; Inventory Guarantee. + + + + + + Total Offer Items in this Offer. Example: 3 + + + + + Requested and Priced PTC (passenger type code) and associated Traveler quantity. + + + + + + When true, this Offer applies to all Travelers. + + + + + When true, this Offer must be redeemed, e.g. it cannot be purchased. + +Note: Taxes may still apply. + + + + + + + + Offer-Level Time Limits, including Offer Expiration, Payment and Bilateral Time Limits. + +Note: If specified, these time limits are at the OFFER-LEVEL and will apply by default to any relevant (child) Offer Items. These time limits may also be specified at a (child) OFFER ITEM-level where it will apply to that one instance of the Offer Item (and override the Offer-level time limit if one has been specified.) + + + + + The total price for all mandatory OfferItems contained within this Offer. + + + + + + + + + + + + + + + + + + Penalty information. + + + + + + + Airline-assigned unique Offer identifier. + + + + + Airline designator of the owner/ assigner of the Offer ID, typically used for offer ordering purposes. Example: UA, BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Code + + + + + The POA OrderID should only go to the ORA, not back to the seller. +1. ORA +2. POA + + + + + Indicator to specify if the offer relates to requested date. For example in calendar search, this indicator will be set to 'true' if this airline offer is for a requested date and will not be present (or will be set to 'false' if airline offer is for another date than requested one. + + + + + Deep linking into another site to complete the transaction. + + + + + + + Core Baggage Offer definition. + + + + + Total baggage price for a specific offer, excluding taxes and charges. Monetary value and currency code. + + + + + + + + + + + + + + + Validating Carrier Airline Designator. +A two-character alpha-numeric code assigned according to the IATA Resolution 762 or a three-letter airline designator assigned by ICAO. Refer to IATA Airline Coding Directory . Example: BA + + + + + + Baggage Details. + + + + + + Baggage detail. + + + + + + Validating Carrier Airline Designator. +A two-character alpha-numeric code assigned according to the IATA Resolution 762 or a three-letter airline designator assigned by ICAO. Refer to IATA Airline Coding Directory . Example: BA + + + + + + Baggage Offer Association(s), including Shopper, Flight, Baggage Details, Optional Services and other miscellaneous association. + + + + + + + + Baggage Disclosure information. + + + + + Elements relating to baggage charges. + + + + + + AWARD (Redemption Unit-based) Pricing information. + + + + + PARTIAL CURRENCY and AWARD Pricing Combination information. + + + + + A (detailed) CURRENCY-based Price with Price Break-down for Tax and/ or Fee information. + + + + + Monetary value amount and currency code. + + + + + A (simple) CURRENCY-based Price with NO taxes and/ or fees. +Examples: 100.00, 100, 100 (USD) + + + + + + + + + + + + + + + + Core Other Offer definition. + + + + + Other Offer Pricing. + + + + + + AWARD (Redemption Unit-based) Pricing information. + + + + + PARTIAL CURRENCY and AWARD Pricing Combination information. + + + + + A (detailed) CURRENCY-based Price with Price Break-down for Tax and/ or Fee information. + + + + + Monetary value amount and currency code. + + + + + A (simple) CURRENCY-based Price with NO taxes and/ or fees. +Examples: 100.00, 100, 100 (USD) + + + + + + + + + + Core Priced Flight Offer definition. + + + + + Fare Offer and Lead Calendar Pricing information. + + + + + + + + + + + + + When true, this is a lead pricing generated priced flight offer. + + + + + + + When true, additional lead pricing offers are included with this proced flight offer. + + + + + + + + Core Seat Offer definition. + + + + + + + Seat Offer Pricing. + + + + + + + + + + + + + + + + + + + A data type for Offer Instructions. + + + + + Upgrade-eligible Class(es) of Service. + + + + + Free-text Instruction Remark(s). + + + + + Special Need Order booking method. +Examples: +AE (by SSR-Special Service Request) +AF (by OSI-Other Service Information) + +Encoding scheme: PADIS Code List for data element 9750 - Option + + + + + + + + Upgrade-eligible Class(es) of Service. + + + + + Free-text Instruction Remark(s). + + + + + Offer Instructions: Free-Text Remark(s). + + + + + + + + CLASS OF SERVICE UPGRADE definition. + + + + + + + + + Offer/ Offer Item: INVENTORY GUARANTEE definition. + + + + + Time limit by which guaranteed inventory for a specified product offer is guaranteed as available and by which the inventory held must be converted into a completed order before the time limit expires otherwise the guarantee is lost. + +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + + + + + + + + + + Unique Inventory Guarantee ID. +Examples: INVREF123456, 68E0DB2F-675C-44F7-BC1E-653106099FF9 + +Note: This is a unique identifier issued by an Airline to reference that inventory for a specified offer will be guaranteed as available for a period. + + + + + Association(s) to one or more Offers or Offer Items for which the inventory guarantee applies. + + + + + + + + Inventory Guarantee information, including Inventory Guarantee Time Limit, Unique ID and Offer/ Offer Item association(s). + +Notes: +1. This is the time that inventory for a specified product offer is guaranteed as available. The inventory held must be converted into a completed order before the time limit expires otherwise the guarantee is lost. +2. If specified, an association to one or more Offers or Offer Items may be specified in the Associations node. If no associations are specified, the inventory guarantee is assumed to apply to the entire Offer. +3. This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of this capability is not dictated by this specification. + + + + + + LEAD PRICING CALENDAR Pricing definition. + +Price information for alternate dates. + +Notes: +1. This is based on lead pricing specified in the AirShoppingRQ/ AttributeQuery/Flight node Arrival and/ or Departure elements. + +2. This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only.The technical implementation of this capability is not dictated by this specification. + +3. If implemented, the client application will typically send new a new shopping request if any of these window shopping dates are selected. + + + + + Fare Price for the Requested Date. + + + + + + + + Fare Offer Associations. + + + + + + + + + + + + Globally unique OfferItem instance ID. It is not recommended to exceed 64, and it is not recommended to use dashes..Example: QWASZXERDFCVTYGHBNUIJKNMF67D5F9GHR567SWER41SD458F9456FMDIRTN34DF + + + + + POA to ORA only: to indicate that the offer is non-modifiable. This indicates to ORA that its offer is non-modifiable (eg. Regulatory or brand protection reasons). If indicator is set to true, nodifications to the POA’s offer ARE NOT allowed. + + + + + + + Lead Pricing Price Detail definition. + + + + + Price Detail, including total amount, base fare amount and other details. + + + + + + Total price amount. + +Notes: +1. This is typically the lowest price for this alternate lead shopping date. +2. If expressed in currency, this price should include base price, taxes and fees/ surcharges. + + + + + + + + + + + + + + Total Base Fare Amount. Example: 200000 + +Note: This includes surcharges (if applicable). + + + + + + Discount Information + + + + + Applicable Surcharge(s). + + + + + + Surcharge detail. + + + + + + + + Ticket Tax/fee/charge details to indicate taxes that apply to country of commencement of travel and routing. + + + + + + + + AWARD (Redemption Unit-based) Pricing information. + + + + + PARTIAL CURRENCY and AWARD Pricing Combination information. + + + + + + + + + + Individual fee/ surcharge information would appear on the accountable document. + + + + + + + + + + + + + + + + Offer Match to shopping criteria. Examples: Full, None, Partial, Other + +Notes: An additional percentage qualifier, such as 50%, may be specified for a Partial match. + + + + + A data type for Search Query to Results Match. + +Offer match to shopping criteria. Examples: Full, None, Partial, Other + +Note: An additional percentage qualifier, such as 50%, may be specified for a Partial match. + + + + + Match Application. Examples: ATTRIBUTE, AFFINITY, Other + + + + + Offer Match Result. Examples: Full, None, Partial, Other + + + + + + + + + + Match percentage. Example: 60 + +Note: This value may be used to indicate a percentage of a Partial match. + + + + + + + + + Requested to be priced, and actually Priced PTC (Passenger Type Code) and associated Traveler(s) quantity. + + + + + PASSENGER TYPE CODE/ QUANTITY definition. + +Passenger type code and Traveler quantity. Example: ADT +Encoding scheme: IATA (three character) Passenger Type Code + + + + + + Number of Traveler(s) for associated passenger type and country of residence. Example: 2 + + + + + + + + A data type for Requested and Priced Passenger Type Code(s) and Quantity. + +Passenger type code and Traveler quantity. Example: ADT + +Encoding scheme: IATA (three character) Passenger Type Code + + + + + Requested passenger type code for pricing. Example: CHD + +Encoding scheme: IATA (three character) Passenger Type Code + + + + + Actual passenger type code used for for pricing. Example: ADT + +Encoding scheme: IATA (three character) Passenger Type Code + + + + + + + + + OFFER PENALTY definition. + + + + + + + + + + OFFER INCENTIVE information definition. + + + + + Offer Incentive detail. + + + + + + Rules engine offer ID. +Example: 0AR123 + + + + + Offer expiration date. +Example: 2017-01-13 + + + + + + + + + + Offer subcode generated on creation by SQL. + + + + + + + + + + Quantity of available units. Example: 4 + + + + + Distinguishes between choice of discount amount or discount percentage. + + + + + + + + + + + + + + + + + + + An Offer Pricing snapshot that applies to All OFFER (results) from ALL AIRLINES. + +Note: Includes pricing indicators; sub-totaled price for all offer items; and highest/ lowest priced offer amounts. Supports Currency, Redemption, and Combination Pricing. + + + + + An Offer Pricing snapshot that applies to ALL OFFER (results) from THIS AIRLINE. + +Note: Includes pricing indicators; sub-totaled price for all offer items; and highest/ lowest priced offer amounts. + + + + + A data type for Aggregated Optional Service Offer Information for One Airline. + + + + + Total number of Passengers (of the same passenger type) included in this offer. + + + + + + + + + + + Sub-totaled Price for all Travelers (of all types) and all Offer Item(s). + + + + + + + + + + + + + + + Highest Price for all Travelers (of all types) and all Offer Item(s). + + + + + + + + + + + + Lowest Price for all Travelers (of all types) and all Offer Item(s). + + + + + + + + + + + + Total Quantity of Offers that Matched search criteria. Example: 3 + +Note: This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of this capability is not dictated by this specification. + + + + + + + + + OFFER/ OFFER ITEM STATUS definition. + + + + + Status. Examples: NN (Requested); HK (Confirmed) + +Note: This Offer Status may contain any bilaterally-agreed upon status information. + + + + + + + + + + OFFER TERMS definition. + + + + + Earliest and Latest Period that an Option is Available or May be Used. + + + + + Offer Terms Description(s). + + + + + Minimum and Maximum Group Size, e.g. Traveler quantities, associated with the Offer. + + + + + Minimum/ Maximum Option Ordering Quantity(s). + + + + + + + + + MINIMUM/ MAXIMUM GROUP SIZE definition. + + + + + The MINIMUM Group Size (e.g. Traveler quantity) required for the Offer. Example: 2 + + + + + The MAXIMUM Group Size (e.g. Traveler quantity) required for the Offer. Example: 6 + + + + + + + + EARLIEST/LATEST Option Available/ Use definition. + + + + + Offer/ Order term (condition) for the Earliest time an item is Available or May be Used. + +Examples: 2017-01-03T13:20:00, 2017-01-13T13:59:38Z + + + + + + + + + + Offer/ Order term (condition) for the Latest time an item is Available or May be Used. + +Examples: 2017-01-03T13:20:00, 2017-01-13T13:59:38Z + + + + + + + + + + + + + MINIMUM/ MAXIMUM Offer Ordering Quantity definition. + + + + + The MINIMUM Quantity of the Option that may be ordered. Example: 2 + + + + + The MAXIMUM Quantity of the Option that may be ordered. Example: 4 + + + + + + + + + OFFER TIME LIMIT SET (collection) definition. + + + + + Offer Expiration Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +Notes: +1. This is the time within which offers must be converted into completed Orders. + +2. On expiry, a new shopping transaction is required. + +3. This time limit is at the OFFER-LEVEL and will apply to all (child) Offer Items. + + + + + + + Offer Time Limit object instance id and metadata instance(s) association. + + + + + + + + + Payment Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +Notes: +1. This is the deadline by which a commitment to pay must be made for the confirmed items in an offer as agreed witht he airline. The passenger meets this requirement by making complete payment for the order. + +2. Payment Time Limit and Ticket Time Limit may be the same in most cases; however, Payment Time Limit expands to include ticketless transactions and other accountable documents. + +3. This time limit is at the OFFER-LEVEL and will apply to all (child) Offer Items. + + + + + Other Offer Time Limit(s). + + + + + + Other Offer Time Limit detail. + + + + + + + + + Offer Time Limit object instance id and metadata instance(s) association. + + + + + + + + + + + + + OFFER ITEM TIME LIMIT SET (collection) definition. + + + + + Offer Item Time Limit detail. + + + + + + + + + + + + + + Price Guarantee Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +Notes: +1. This is the period for which an Offer price is guaranteed. + +2. On expiry an Offer may be re-priced up to the point an accountable document is issued. + +3. A Price Guarantee cannot extend beyond the Offer Expiration Time Limit unless an Order has been created. + + + + + + + + + + Offer/ Offer Item: PRICE GUARANTEE Time Limit definition. + +Price Guarantee Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +Notes: +1. This is the period for which an Offer price is guaranteed. + +2. On expiry an Offer may be re-priced up to the point an accountable document is issued. + +3. A Price Guarantee cannot extend beyond the Offer Expiration Time Limit unless an Order has been created. + + + + + + Ticketing By Time Limit. + +DEPRECATON NOTICE: This element will be deprecated in the 2015.1 publication. + +Notes: This is not the Offer Expiration Time Limit that applies to offers in a shopping response. This is the date/ time when a ticket-associated offer must be purchased/ ticketed, e.g. applicable to booking versus shopping. It has been left in the specification for backwards compatibility. + + + + + Offer/ Offer Item: TICKET BY Time Limit definition. + + + + + Ticketing By Time Limit. +Example: 2017-05-30T09:00:00 + +DEPRECATON NOTICE: +This element will be deprecated in the 2015.1 publication. + +Notes: This is not the Offer Expiration Time Limit that applies to offers in a shopping response. This is the date/ time when a ticket-associated offer must be ticketed, e.g. applicable to booking versus shopping. It has been left in the specification for backwards compatibility + + + + + + + + + + + + + + + NDC XML SPECIFICATION: ORDER XML OBJECT + + + Notice: This is NDC Draft Specification provided for pre-review by the members of the relevant governance groups, it is not provided for implementation in a production environment or considered to be the final schema to support NDC business requirements. The draft schema may, at any time up to final specification submission, undergo changes including, but not limited to, specific elements, element names/labels, annotations or message name as a result of the ongoing quality control process, and comments, which may be received following the pre-review. Implementation of this version is done so at the risk of the implementer or implementing company. + + + + + + A data type for Other Order Optional Associations. + + + + + + + + + A data type Other Order Association Type Name. + + + + + + + Association(s), including Passenger, Group, Order Item, Offer Item and Optional Service. + + + + + Other Order Associations. + + + + + Other Association Detail. + +Note: Includes an association type choice (e.g. MediaGroup) and an instance association value (e.g. mediagrp1). + + + + + + Named association type. Examples: CarryOnAllowance, MediaGroup + + + + + Associated object instance value. Example: mediaGroup1 + + + + + + + + + + + Order Association(s), including Passenger, Group, Order Item, Offer Item and Optional Service. + + + + + + Order Item association(s). + + + + + Passenger(s). + + + + + + + Association to multiple Passenger instance(s). Example: pax1 pax2 + + + + + + + + + Associated Group detail. + + + + + Flight that the offer applies to. + + + + + + When true, this Baggage Offer applies to all specified flights. + + + + + When true, this Baggage Offer applies to all specified flight Origin/ Destination Pairs. + + + + + When true, this Baggage Offer applies to all specified flight Segments. + + + + + + + + + + + + Associated Order Item(s). + + + + + + + + + + Associated Offer Item(s). + + + + + + + + + + Associated Order Item(s). + + + + + + + + + + Other optional association(s). + + + + + + When true, this applies to all passengers. + + + + + When true, this applies to the whole itinerary, including all passengers. + + + + + + + Additional Order Item Details, including instructions. + + + + + + Order detail. + + + + + + Details of the commission claimed by a Travel Agent for selling air transportation/services on behalf of an airline. + + + + + + + + + + + + + Order Instructions. + + + + + + + + + + Special Need Order booking method. +Examples: +AE (by SSR-Special Service Request) + +Encoding scheme: PADIS Code List for data element 9750 - Option + + + + + + + + + + A data type for Order Instructions. + + + + + + Details of the commission claimed by a Travel Agent for selling air transportation/services on behalf of an airline. + + + + + + Order Instructions: Commission type + + + + + + + + A data type for Shopping Request Business Object: EXISTING ORDER Qualifiers. + + + + + + + + + Order Keys. Contains One Order ID with associated Order Item ID(s). + +Notes: These are Orders that were created from Offers that have already been purchased, booked and/or are being held for a Traveler. + + + + + Order ID and Child Order Item Collection definition. + Shopping CR: This fulfills the requirement to allow previously ordered items to be used as a shopping session qualifiers. + + + + + + Associated Order Item(s), Offer Item(s) and Optional Service(s). + + + + + + Associated ID detail. + + + + + + + + + + + + + + + + + + The airline-assigned unique Order ID. Example: ORDER-c98c-4759-a20b + + + + + A data type for an Order ID. + +The airline-assigned unique Order ID. Example: ORDER-c98c-4759-a20b + + + + + + Policy, object and metadata association. + +Note: Equivalent Keys are specified in Metadata. + + + + + Airline Designator of airline that owns/ assigned this ID. Example: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Codes + + + + + Deep linking into another site to complete the transaction. + + + + + The POA OrderID should only go to the ORA, not back to the seller. +1. ORA +2. POA + + + + + + + + + + + + + + CORE ORDER definition. + + + + + + This may be used when an Order has been sub-divided into associated Orders (eg because a change creates non-homogeneity in a PNR), and serves as a cross reference for the original Order ID. + + + + + + This is pertinent information for an order change involving re-pricing as it provides the order pricing history e.g. indicating that an order has already been priced a number of times and the pricing source and history. + + + + + + + + + Payment Amount + + + + + + + + + + ID or name of the source of this Transaction ID. Examples: UA, ABC123 + +Note: If this is an airline ID, use IATA 2 character or ICAO 3 letter Airline Designator Code Encoding Scheme. + + + + + Airline designator or CRS code of the owner/ assigner of the Offer ID, typically used for offer ordering purposes. Example: UA, BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline or CRS Designator Code + + + + + + + + + + + Order creation timestamp. +Example: 2015-01-13T13:59:38Z + + + + + + + + + + + + Airline Designator of airline that owns/ assigned this ID. Example: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Codes + + + + + The POA OrderID should only go to the ORA, not back to the seller. +1. ORA +2. POA + + + + + + + + + + + Deep linking into another site to complete the transaction. + + + + + Object Metadata Association(s). Example: meta1 meta3 + + + + + + + Total Order Price. Example: 3400 USD + +Note: This is a sub-total of all associated Order Item prices. + Currency, Redemption and Partial Pricing + + + + + + + + + + + + + + Current status of the Order Item and related indicators. + + + + + + + Current Order Item status. Example: OK (Confirmed) Encoding Scheme: IATA Padis Codeset - List for data element 4405 (Status, coded) + + + + + + + + When true, the order item cannot be fulfilled due to an aircraft change. + + + + + + + When true, the order item cannot be fulfilled due to a flight schedule change. + + + + + + + + Payment Processing information. + +Note: This payment information applies to the entire Order. Note that it may also be specified at the Order Item level. + + + + + + Payment Processing detail. + + + + + + + + Order-Level Time Limits. + + + + + + Payment Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +Notes: +1. This is the deadline by which a commitment to pay must be made for the confirmed items in an offer as agreed witht he airline. The passenger meets this requirement by making complete payment for the order. + +2. Payment Time Limit and Ticket Time Limit may be the same in most cases; however, Payment Time Limit expands to include ticketless transactions and other accountable documents. + +3. This time limit is at the OFFER-LEVEL and will apply to all (child) Offer Items. + Although specified as mandatory in the BRD, there may be a case where Payment is already provided in the Order information. + + + + + + + + + + + + + + + + + + Order Keys. Contains one Order ID with associated Order Item ID(s). + +Notes: These are Orders that were created from Offers that have already been purchased, booked and/or are being held for a Traveler. + + + + + + The airline-assigned unique Order ID. Example: ORDER-c98c-4759-a20b + + + + + Airline Designator of airline that owns/ assigned this ID. Example: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Codes + + + + + The POA OrderID should only go to the ORA, not back to the seller. +1. ORA +2. POA + + + + + + + + + + + Deep linking into another site to complete the transaction. + + + + + Object Metadata Association(s). Example: meta1 meta3 + + + + + + CORE ORDER ITEM definition. + + + + + Order Item details. + + + + + + Current Order Item status. Example: OK (Confirmed) Encoding Scheme: IATA Padis Codeset - List for data element 4405 (Status, coded) + + + + + + + + Total price amount. + +Notes: +1. This is typically the lowest price for this alternate lead shopping date. +2. If expressed in currency, this price should include base price, taxes and fees/ surcharges. + + + + + + + + + + + + + + Total Base Fare Amount. Example: 200000 + +Note: This includes surcharges (if applicable). + + + + + + Discount Information + + + + + Applicable Surcharge(s). + + + + + + Surcharge detail. + + + + + + + + Ticket Tax/fee/charge details to indicate taxes that apply to country of commencement of travel and routing. + + + + + + + + AWARD (Redemption Unit-based) Pricing information. + + + + + PARTIAL CURRENCY and AWARD Pricing Combination information. + + + + + + Individual fee/ surcharge information would appear on the accountable document. + + + + + + + + + + + + + The individual instance of a specific Service (as described in DataLists' ServiceDefinitions) or service bundle as it has been offered, and eventually ordered by a specific Passenger. + + + + + + + Create dependencies with parent services to which this particular ServiceItem is linked to (eg. a meal to a flight). Can reference ServiceItems across different OfferItems within the same Offer. + + + + + + Reference a segment being sold as part of this OrderItem/Service. + + + + + + + + + Reference to a segment in the Datalists to restrict the eligibility of the associated ServiceDefinition. + + + + + + + + + The Seat location selected by the Passenger (via SeatAvailability) or assigned by the Airline for a given Segment. + + + + + + Selection of specific seat location, as provided in seat availability messages. + +When used, only a single Passenger must be referenced for a single Segment + + + + + + Seat row number. Example: 2 + + + + + Seat column to identify a particular seat position on an aircraft + + + + + + + + Reference to the Segment on which this Passenger's Seat has been assigned. + + + + + Reference to the ServiceDefinition relating to the Seat assigned to the Passenger. + + + + + + + + + + ID for the Service contained this OrderItem. While the OrderItem would be a direct transference of the originating OfferItem, the Services within are broken down to a more granular level (i.e. a single deliverable unit of a specific service per passenger per flight segment). Therefore, the ServiceIDs in an Order do not reflect a 1-to-1 mapping to the originating Offer’s ServiceIDs. + + + + + Current Service status. + +Encoding Scheme: IATA Padis Codeset - List for data element 4405 (Status, coded) + + + + + + + Order item-associated Time Limit(s). + + + + + Inventory Guarantee + + + + + + + Unique Inventory Guarantee ID. Examples: INVREF123456, 68E0-675C Note: This is a unique identifier issued by an Airline to reference that inventory for a specified offer will be guaranteed as available for a period. + + + + + + + + + + + Penalty information. + + + + + + Fare Detail, including Fare Component and Fare Rules. + + + + + + The airline-assigned unique Order Item ID. Example: ORD769-A850-4EC4-8F46-02293F72D7E6 + + + + + Airline designator or CRS code of the owner/ assigner of the Offer ID, typically used for offer ordering purposes. Example: UA, BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline or CRS Designator Code + + + + + The POA OrderID should only go to the ORA, not back to the seller. +1. ORA +2. POA + + + + + Timestamp. Example: 2017-01-13T13:59:38Z + + + + + Deep linking into another site to complete the transaction. + + + + + + + + + + Baggage Order Item. + + + + + A BAGGAGE OFFER with additional Significant Carrier, Baggage Characteristics (e.g. dimensions/ weight) and Disclosures. + + + + + Price. + + + + + Validating Carrier Airline Designator. +A two-character alpha-numeric code assigned according to the IATA Resolution 762 or a three-letter airline designator assigned by ICAO. Refer to IATA Airline Coding Directory . Example: BA + + + + + Baggage Details. + + + + + + Baggage detail. + + + + + + Validating Carrier Airline Designator. +A two-character alpha-numeric code assigned according to the IATA Resolution 762 or a three-letter airline designator assigned by ICAO. Refer to IATA Airline Coding Directory . Example: BA + + + + + + + Baggage Disclosure information. + + + + + Elements relating to baggage charges. + + + + + + + + + + + + + + + + + + + + + + + + Flight Offer Item. + + + + + FLIGHT Order Item. + + + + + Flight Pricing. + + + + + Flight Origin/ Destination information. + + + + + Fare Detail. + + + + + + + + Other Order Item type, e.g. Lounge Pass and Expedited Boarding. + + + + + OFFER ITEM IN ORDER definition. + + + + + + Offer Item Type. + + + + + + + Flight Offer Item. + + + + + + + + + + + Time Limits, including mandatory Offer Expiration and Payment Time Limits. + + + + + + + + + OTHER ORDER ITEM definition. + + + + + Price. + + + + + Allow specification information of OtherItem. + + + + + + + + PAYMENT STATUS definition. + + + + + Overall Order payment Status Code. + + + + + + + + + + + In-complete Payment information, including partially completed payments, payment verification required and failed payments. + + + + + + In-complete Payment Status Code. + +Encoding Scheme: IATA Padis Codeset - List for data element 9321 (Application error, coded) + +Note: This status includes partially completed payments, payment verification required and failed payments. + + + + + + + + + + + + A Premium Seat Order Item, with seat characteristic details. + + + + + + + + + + A SEAT OFFER with additional Seat Characteristics information. + + + + + Price + + + + + Seat Description. + + + + + + + Seat Location information. + + + + + + + + + + + Order Item-Level Time Limits. + + + + + + Payment Time Limit value. +Examples: 2017-05-30T09:00:00, 2015-01-13T13:59:38Z + +Notes: +1. This is the deadline by which a commitment to pay must be made for the confirmed items in an offer as agreed witht he airline. The passenger meets this requirement by making complete payment for the order. + +2. Payment Time Limit and Ticket Time Limit may be the same in most cases; however, Payment Time Limit expands to include ticketless transactions and other accountable documents. + +3. This time limit is at the OFFER-LEVEL and will apply to all (child) Offer Items. + Although specified as mandatory in the BRD, there may be a case where Payment is already provided in the Order information. + + + + + + + + + + + + + + + + + + + + + Bank Account payment. + + + + + BANK ACCOUNT Payment Method definition. + + + + + Account Name. Example: JOHN SMITH + +Note: This is the name the bank account is held under. + + + + + + + + + + + + Check or draft number. Example: 1234 + + + + + + + + Cash payment. + + + + + CASH Payment Method definition. + + + + + Cash Amount. Example: 67.95 + + + + + Terminal ID where cash was collected. Example: QP776611 + + + + + Cash receipt ID. Example: 121717H47S + + + + + Agent ID that collected the cash. Example: TOM123 + + + + + Location where cash was collected. + + + + + + + + + + + + + + + DIRECT BILLING Payment Method definition. + + + + + Direct billing Organizaqtion ID. Example: IBM + + + + + Remit to Company Name. Example: IBM + +Note: This is the company name to whom remittance should be directed. + + + + + Direct Billing Contact Name. Example: J THOMAS + + + + + Address where remittance should be directed. + + + + + + + + + + + + + + + Direct Bill payment. + + + + + Miscellaneous Charge Order (MCO) payment. + + + + + MCO Payment Method definition. + + + + + The ticket number of the miscellaneous charge order (MCO). + + + + + + + + Other payment. + + + + + OTHER Payment Method definition. + + + + + + + + + PAYMENT PROCESSING Information definition. + + + + + + The form of payment type. Examples: Credit Card, Cash. Encoding Scheme: IATA PADIS code list data element [9888] Form of Payment Identification + + + + + + Payment Status information. + + + + + + + When true, payment for this Order has failed. + +Note: Payment Failure status is specified in the PaymentStatus node. + + + + + When true, this Order has been partially paid. + +Note: Partial Payment status and information is specified in the PaymentStatus node. + + + + + When true, payment for this Order requires additional authentication. + +Note: Payment Verification status and information is specified in the PaymentStatus node. + + + + + When true, a price variance was applied. + + + + + + + + + Payment Amount. + + + + + + + + + + + + + + Payment Method information. + + + + + + + + + + + + + + Check (Cheque) Payment + + + + + + + + Price variance actually applied during payment processing. + + + + + + + Price Variance Amount. Example: .67 USD + + + + + Association(s), including Passenger and Group. + + + + + Price Variance Rule Applied. + + + + + + + + Applied Promotion(s). + + + + + + Promotion Detail. + + + + + + + + Association(s), including Passenger and Group. + + + + + + + + + + + + + + The person who is paying for an Order is not a passenger + + + + + + Ref to Contact Information of the Order's Payer. The information can be a company, or include the name details of the individual paying. + + + + + + + + + + + When true, this is a split form of payment. + + + + + + PAYMENT CARD Payment Method definition. + + + + + Magnetic striped card type. + + + + + Credit card issuer code. Example: MC + +Note: This is the 2 character code of the credit card issuer. + + + + + Concealed credit card number, Example: xxxxxxxxxxxx9922 + + + + + + + + + + + + Tokenized card number. + +Note: This capability may not be supported by all NDC-enabled systems or may be supported by bilateral agreement only. If supported, the technical implementation of this capability is not dictated by this specification. + + + + + + Name of credit card holder. Example: JOHN SMITH + + + + + + + + + + + + Credit card issuing company. + + + + + + Issuer Name. Example: Bank of America + +Note: This is the name of bank or organization issuing the card (e.g., alumni association, bank, fraternal organization, etc.). + + + + + + + + Cardholder Address. + + + + + + + + + + + + + Payment Card Effective and/ or Expiration date(s). + + + + + + Payment Card Effective Date. Example: 0116 + + + + + Payment Card Expiration Date. Example: 0119 + + + + + + + + + Approval Code Method. Example: M (Manual) + +Note: This is used to specify how the approval code for a credit card sale was obtained. + +Encoding Scheme: IATA PADIS Code List for data element 9890. + + + + + + + + Payment Card payment. + + + + + Loyalty Redemption payment. + + + + + REDEMPTION Payment Method definition. + + + + + Loyalty Certificates Redeemed. + + + + + + The loyalty redemption certificate number. + + + + + + + + + + + + + + + An individual airline identifier assigned to a passenger who is a member of an airline's Frequent Flyer Program. + + + + + + + + + + + + The quantity of loyalty units redeemed. Example: 15000 + + + + + Promotion Code. + +Note: Promotion code is the identifier used by the host to link directly with a specific named advertising campaign. By including the required code, the client is able to gain access to special offers which may have been created for a specifically targeted group via a CRM system or for a wider advertising campaign using Television or press adverts. + + + + + List of vendor codes associated with the promotion. + + + + + + + + Voucher payment. + + + + + VOUCHER Payment Form definition. + + + + + Voucher ID or Number. Example: XX12345 + + + + + Voucher Effective and/ or Expiration date(s). + + + + + + Voucher Effective Date. Example: 2017-01-13 + + + + + Voucher Expiration date. Example: 2017-06-13 + + + + + + + + Remaining Amount on Voucher. + + + + + + + + + + + + Alternate Baggage Offer with Order Association definition. + + + + + + + + + Offer Association(s), including Order, Order Item, Passenger, Group, Offer Item and Service. + + + + + + + + + + + Alternate Other Offer with Order Association definition. + + + + + + + + + Offer Association(s), including Order, Order Item, Passenger, Group, Offer Item and Service. + + + + + + + + + + + Alternate Priced Flight Offer with Order Association definition. + + + + + + + + + Offer Association(s), including Order, Order Item, Passenger, Group, Offer Item and Service. + + + + + + + + + + + Alternate Seat Offer with Order Association definition. + + + + + + + + + Offer Association(s), including Order, Order Item, Passenger, Group, Offer Item and Service. + + + + + + + + + + + + An Alternate Baggage Offer. Note: A Baggage Offer may contain additional Validating Carrier and Bag Detail, including Checked and Carry-on Baggage Allowance and Baggage Disclosure(s). + + + + + + + An Alternate Priced Flight Offer. Notes: 1. A Priced Flight Offer may contain Branded Fare information. If it is a Branded Fare, Price Class-association will be specified. 2. Additionally, Lead Pricing Calendar fares (prior to and/ or after the specified departure date) may be specified by passenger type. + + + + + + + A Generic Optional Service Offer. Note: A Generic Optional Service Offer may contain seat details, including Marketing Name; Seat Features; Seat Descriptive Keywords; and Seat Dimensions.Other Optional Service Offer type, e.g. Lounge Pass and Expedited Boarding. + + + + + + + An Alternate Seat Offer. Note: A Seat Offer may contain seat details, including Marketing Name; Seat Features; Seat Descriptive Keywords; and Seat Dimensions. + + + + + + + ORDER PENALTY definition. + + + + + + + + + + Current status of the Order Item. Example: OK (Confirmed) Encoding Scheme: IATA Padis Codeset - List for data element [4405] Status, coded + + + + + + ORDER PROCESSING RESULTS Information definition. + + + + + + + + + + Order Time Limits definition. + + + + + + + + + + + Order Item Time Limits definition. + + + + + + + + + + + + + + NDC XML SPECIFICATION: Common XML Objects shared by NDC Payment and Ticketing Domain. + + + Notice: This is NDC Draft Specification provided for pre-review by the members of the relevant governance groups, it is not provided for implementation in a production environment or considered to be the final schema to support NDC business requirements. The draft schema may, at any time up to final specification submission, undergo changes including, but not limited to, specific elements, element names/labels, annotations or message name as a result of the ongoing quality control process, and comments, which may be received following the pre-review. Implementation of this version is done so at the risk of the implementer or implementing company. + + + + + + Carrier Fee information. + + + + + + CARRIER FEE definition. + + + + + + Carrier Fee detail information to include Type, FeeAmount, FareComponent, ClassCode and Reporting code for Pricing Method. + + + + + + Carrier Fee detail. + + + + + + Carrier Fee Type. +Encoding Scheme: IATA Padis Codeset - List for data element 9750 (Option) + +Note: This is the type of the carrier fee related to a booking or ticketing or service. + + + + + Carrier Fee amount and detail, including fee type, fee application and associated origin/ destination. + + + + + + Carrier fee code type. + + + + + + + + + + Carrier fee amount. Example: 100 USD + + + + + Currency encoding for the Carrier Fee Amount. Example: USD + + + + + Application code. Example: 15 (Not commissionable) + +Encoding Scheme: IATA Padis Codeset - List for data element 9988 (Data Indicator) + +Note: This is used to specify if the fee is not interlineable, not refundable, commissionable or not commissionable. + + + + + Departure Airport Location code. Example: TPA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + + + A series of data elements representing data required to collect non-airport/government fees, store the fee data, +and track the revenue separate from the ticket revenue without requiring a secondary document be issued. + + + + + + + + + + + Fare Component information as may be applicable in filed fares scenarios. + + + + + + Fare Component calculation order (sequence number.) Example: 001 + + + + + + + + + + + Tariff number for where the fare data is filed. Example: 9171 + + + + + + + + + + Rule number. Example: 126 + +Note: This is the rule number within the tariff where the fare data is filed. + + + + + + + + + + Rule Code. Example: 12BE + +Note: This is a system generated code indicating that the ticketed fare is from a specific rule filed fare sent by the issuing system. + + + + + + + + + + + + + A two-character alpha-numeric code assigned according to the IATA Resolution 762 or a three-letter airline designator assigned by ICAO. Refer to IATA Airline Coding Directory. + + + + + + + Carrier Fee Commercial Name. Example: British Airways + + + + + + + + + Fare class code. Example: M + +Note: This is the fare class code that must be used when matching alternate cateory data as specifed by the carrier fee fare rule code, carrier fee rule number, and carrier fee tariff number fields. + + + + + + + + + + + Carrier fee pricing method. Example: A + + + + + + + + + + + + + + + + Ticket Tax/fee/charge details to indicate taxes that apply to country of commencement of travel and routing. + + + + + + + + + + + + + + Additional Reference information. + +Note: Based on the specified Type, this may contain an invoice number, customer file reference, customer id, or airline indexing field. + + + + + Booking and Servicing Agent(s). + + + + + + + + + + Checked-in Airline Flight Segment information. + + + + + Current Airline Flight Segment information. + + + + + FlownAirline Flight Segment information. + + + + + In connection with document number (A document number representing a transaction that is issued in relation to this transaction); and coupon number (the coupon number(s) associated with the 'in connection with' document number.) + + + + + Place of Issue of the agency or airline issuing the document followed by the name of the agency or airline issuing the document. + + + + + + + + + + Original Ticket/ Document Issue information. + + + + + + + + + + Pricing information for the booked itinerary. + + + + + + + + + + Ticket document details. + + + + + + + When true, the credit/debit card used for purchase must be presented. + + + + + When true, a penalty restriction applies. + + + + + When true, the document is non-commissionable. + + + + + When true, the document is non-interlineable. + + + + + When true, the document is non reissuable and/or exchangeable. + + + + + When true, the fare is non refundable. + + + + + When true, a tax has been collected and is due to a local government from the validating carrier. + + + + + When true, this is the ticket/document number for a ticket/document that is being exchanged. + + + + + When true, this is the primary ticket/document number. + + + + + + + + + The number of ticket/ documents to be issued. + +Note: This is used as a checksum for the quantity of instances specified in the TktDocInfo node. + + + + + + COUPON-RELATED ADDITIONAL REFERENCE definition. + + + + + Additional Reference Type. Example: 6 (Customer ID) + +Encoding Scheme: IATA Padis Codeset - List for data element 9958 (Reservation Control Type) + + + + + Additional Reference ID. + +Note: Based on the specified Type, this may contain an invoice number, customer file reference, customer id, or airline indexing field. + + + + + + + + + + + + + COUPON ISSUING AIRLINE definition. + + + + + Issuing Airline Name. Example: British Airways + + + + + The place where the document was issued. Example: New York City NY + + + + + + + COUPON BOOKING/ SERVICING AGENT definition. + + + + + Agency/ Agent Identification Type. Example: 706 (IATA agency numeric code) + +Encoding Scheme: IATA Padis Codeset - List for data element 9893 (Identification Type, coded) + + + + + ID. Example: 98417900 + +Note: The ID correlates to the specified ID Type. + + + + + + + Object association(s) between this object and any other object or metadata instance(s). + + + + + Object Metadata Association(s). Example: meta1 meta3 + + + + + Entity Name. + + + + + + + + + + + COUPON definition. + + + + + Coupon Sequence Number. Example: 2 + +Note: This is the number representing the order in which this coupon was used or is to be used. + + + + + + + + + + + Applicable coupon number. Example: 1234 + + + + + Coupon Refence Number. Example: 1 + +Note: This is the sequential number (segment identifier) of an individual flight segment. + + + + + + + + + + + + Coupon Media Type. Examples: Electronc, Paper, Other + + + + + Coupon Valid date or date/time period. + + + + + Current status of the flight/value coupon. Example: E (Exchanged/reissued) + +Encoding Scheme: IATA Padis Codeset - List for data element 4405 (Status, coded) + + + + + Involuntary Change Transaction Code. Example: I (Involuntary - no reason given) + +Encoding Scheme: IATA Padis Codeset - List for data element 1245 (Status indicator, coded) + + + + + Settlement Authorization Code. Example: AUTH123 + +Note: This is a reference number generated by the validating carrier authorising settlement of a coupon. + + + + + Associated Fare Basis Code. + +Note: This is the applicable code provided for IATA Resolution 728 (for the associated EMD.) + + + + + Promotional code that applies to the fee. Example: PROMO123 + + + + + Date of Service. Example: 2017-01-17 + +Note: This is the scheduled date of service for this coupon of an EMD. + + + + + Service Quantity. Example: 1 + +Note: Thisis the number of services of the same type that are included in an EMD coupon. + + + + + + + + + + + Association to services paid by the EMD Association to multiple Optional Service instance(s). Example: srvc1 srvc2 + + + + + Coupon Value. Example: 100 USD + +Note: This is the value associated to a single coupon of a miscellaneous document. + + + + + Date and time, flight number, stopover indicator, and status code. + + + + + + + + + + + + + + + In connection with document number (A document number representing a transaction that is issued in relation to this transaction); and coupon number (the coupon number(s) associated with the 'in connection with' document number.) + + + + + Name and location of service provider that will perform the service described on an EMD coupon. + + + + + The name of service provider. Example: ??? + + + + + + + + + + The location of the service provider. Example: ??? + + + + + + + + + + + + Reason for Issuance information. + +Note: This contains the Reason for Issuance Code (RFIC) and Reason for Issuance Subcode (RFISC.) + + + + + + + Reason for Issuance Subcode. Example: ??? + + + + + + + + + + Corresponding description to the reason for issuance subcode. Example: ??? + + + + + + + + Filed fee information. + + + + + + Filed Fee Amount. Example: 100 USD + + + + + + Bankers Seller Rate. Example: 1.25 + +Note: This is the BSR and/ or BBR used to convert the tax/fee/charge filed amount from the filed currency into the tax/fee/charge amount in currency of country of payment. + + + + + + + + + + Contains product characteristics of an optional service, for inclusion on EMD. Includes type (Designates an optional service product characteristic type e.g., t-shirt size, color or pre-reserved seat number); and product characteristic value (Text that describes the product sold for the corresponding Product Characteristic Type, e.g. large, blue.) + + + + + + Optional Service Product Characteristic. Example: ??? + +Note: This identifies the type of optional service product characteristic described in description. + + + + + + + + + + Product Characteristic Description. Example: ???? + + + + + + + + + + + + + Identifies the ATPCO additional services information. + + + + + + ATPCO Optional Service Group Code. Example: ??? + +Note: This is a value which specifies the high-level group applicable to the service at the coupon level as defined by ATPCO. + + + + + + + + + + ATPCO Optional Service Sub Group Code. Example: ??? + +Note: This is a value which specifies the sub group (within the specified group) applicable to the service at the coupon level as defined by ATPCO. + + + + + + + + + + RFISC Issuance Type. Example: ZZZ (Mutually Defined) + +Encoding Scheme: IATA Padis Codeset - List for data element 1131 (Code List Qualifier) + +PAULA: Is the right code set? + + + + + ATPCO Service Type Code. Example: ? + +Note: This is a value which specifies the service type. + + + + + + + + + + + + + Excess baggage information for this coupon. + + + + + + Excess Baggage Amount. Example: 100 USD + + + + + Unit of Measure Code. Example: W (Weight) + +Encoding Scheme: IATA Padis Codeset - List for data element 5463 (Allowance or Charge Qualifier) + + + + + Excess Baggage Unit Quantity. Example: 10 + + + + + Excess Baggage Unit of Measure. Example: Pounds + +Note: This is a standard unit of measure name (e.g., it could be generic such as metric or imperial or specific such as inches, feet, yards, miles, millimeters, centimeters, meters, kilometers- according to usage). + + + + + + + + + + + + + + Coupon Validating Airline. Example: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Code + + + + + Free text to provide further information related to the document and/or the coupon. + + + + + + The two/three character designator identifying the Marketing Carrier designated in the new reservation. + + + + + This field contains the scheduled date of departure of the “Reservation Change” flight. + + + + + This field contains the destination Airport/City Code of the “Reservation Change” flight. + + + + + + + + + + This field contains the scheduled departure time of the “Reservation Change” flight. + + + + + + + + + + This field contains the flight number of the “Reservation Change” (Marketing Carrier) flight. + + + + + + + + + + This field contains the origin airport/city code of the “Reservation Change” flight. + + + + + + + + + + This field contains the reservations booking designator (Marketing) of the “Reservation Change” flight. + + + + + This field contains the Reservation Status Code of the “Reservation Change” flight. + + + + + + When true, the coupon is consumed at issuance. + + + + + + COUPON EFFECTIVE PERIOD definition. + + + + + The period in which the applicable coupon on an accountable document may be used for travel or for obtaining a service it entitles the holder to. + + + + + + + + Effective period duration. Example: P3M + +Note: This maybe used in combination with the Effective date, versus specifying an Expiration date. + + + + + + + + + + The period in which the applicable coupon on an accountable document may be used for travel or for obtaining a service it entitles the holder to. + + + + + + + + Effective period duration. Example: P3M + +Note: This maybe used in combination with the Effective date, versus specifying an Expiration date. + + + + + + + + + + + + + COUPON-RELATED ORDER REFERENCE definition. + + + + + + + + + + + + + AIRLINE FLIGHT COUPON definition. + + + + + Scheduled, intended or actual departure date/ time. + + + + + + + + + + Arrival date/ time. + + + + + + + + + + Flight Stop Quantity and Location(s). + + + + + + Stop Quantity. Example: 1 + + + + + + + + + Information Source. Example: BA + + + + + Tour Operator Flight ID. + +Note: This is an ID for the flight as represented by a Tour Operator. This flight is not necessarily in the inventory of an airline as it is a code created by tour operators. + + + + + + + + + + + + + Operating Carrier Information. + +Operating Carrier is the carrier that operates a flight with a reference to its own prime flight number. + +Note: Operating Carrier may be different from a Marketing Carrier(s), if the flight is actually marketed by another carrier(s) within a codeshare agreement. + +Operating Carrier may not be the AOC holder, in which case, and wherever required, this will need to be disclosed to the customer. + + + + + + + + + + + + + + Marketing Carrier information. + +Notes: This is the carrier that sells with its own code as part of a code share agreement on a flight that is actually operated by another carrier. + + + + + Aircraft Equipment. + +Note: Two instances of aircraft equipment may be specified if there is a change of gauge. + + + + + Reservation Status Code. + +Encoding Scheme: IATA Padis Codeset - List for data element 4405 (Status, coded) + + + + + Seat Number. Example: 112B + +Note: This is a seat assignment reserved for a confirmed flight at the time of ticket issuance. + + + + + Baggage related disclosures to passengers as required by several governments. + + + + + + + Unique Metadata Collection Token. + +Example: jZhJu7SORZeO MNpifElIkA + +Note: This token pertains to all specified metadata information, e.g. the metadata collection. + + + + + + COUPON FLIGHT SEGMENT definition. + + + + + Information Source. Example: BA + + + + + Scheduled, intended or actual departure date/ time. + + + + + + + + + + Tour Operator Flight ID. + +Note: This is an ID for the flight as represented by a Tour Operator. This flight is not necessarily in the inventory of an airline as it is a code created by tour operators. + + + + + + + + + + + + + Operating Carrier Information. + +Operating Carrier is the carrier that operates a flight with a reference to its own prime flight number. + +Note: Operating Carrier may be different from a Marketing Carrier(s), if the flight is actually marketed by another carrier(s) within a codeshare agreement. + +Operating Carrier may not be the AOC holder, in which case, and wherever required, this will need to be disclosed to the customer. + + + + + + + + + + + + + + Marketing Carrier and Flight Number information. + +Notes: This is the carrier that sells with its own code as part of a code share agreement on a flight that is actually operated by another carrier. + + + + + Aircraft Equipment. + +Note: Two instances of aircraft equipment may be specified if there is a change of gauge. + + + + + Involuntary Change Transaction Code. Example: I (Involuntary - no reason given) + +Encoding Scheme: IATA Padis Codeset - List for data element 1245 (Status indicator, coded) + + + + + + + + COUPON TICKET DOCUMENT definition. + + + + + Coupon Document Number. + +Note: This is the document number comprised of the airline code, form code, and serial number. + + + + + + + + + + + Coupon Type. Example: Y (EMD-S Standalone) + +Encoding Scheme: IATA Padis Codeset - List for data element 1001 (Document/ Message Name, coded) + + + + + Connected Document Number. + +Note: This is a ticket/ document to which this document is connected. + + + + + + + + + + The number of booklets issued. + + + + + Date of Issue. Example: 2017-01-13 + + + + + Time of Issue. Example: 14:32 + + + + + Airport or City Code. Example: JFK + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + Ticket Routing Code. Example: D + +Note: This is for EMD-A and EMD-S tickets with routing. +- Use D - if all board and off points are within the same country +- Use I - if all board and off points are not within the same country +- For an EMD-S with no routing, do not use. + + + + + + + + Airline Designator. Example: BA + +Note: This is the airline designator representing the carrier whose fee was used on the EMD coupons. + + + + + Carry-on and checked baggage allowances. + + + + + Free text to provide further information related to the document and/or the coupon. + + + + + Coupon information. + + + + + Association to Penalty element in DataList. Example: PN1 PN2 + + + + + For billing and settlement purposes, each time a travel agent requests an airline to perform an action on a document (Issuance, Refund, Exchange), he needs to know how to reconciliate this action: via BSP, via ARC, directly done by the ORA, etc. + + + + + + + + + + + + + + COUPON definition. + + + + + Applicable coupon number. Example: 1234 + + + + + + + + + + + Current status of the flight/value coupon. Example: E (Exchanged/reissued) + +Encoding Scheme: IATA Padis Codeset - List for data element 4405 (Status, coded) + + + + + Previous status of the flight/value coupon. Example: E (Exchanged/reissued) + +Encoding Scheme: IATA Padis Codeset - List for data element 4405 (Status, coded) + + + + + Settlement Authorization Code. Example: AUTH123 + +Note: This is a reference number generated by the validating carrier authorising settlement of a coupon. + + + + + The timestamp of the transaction) + + + + + Date and time, flight number, stopover indicator, and status code. + + + + + + + + + + + + + + + COUPON-RELATED IN CONNECTION DOCUMENT/ COUPON definition. + + + + + In Connection Document Number. Example: ??? + + + + + + + + + + In Connection Document Number. Example: ??? + + + + + + + + + + + + + When true, the document and coupon should be associated. + + + + + + COUPON-RELATED ORIGINAL TICKET/ DOC ISSUE definition. + + + + + Original Issuer ID. Example: 12345 + +Note: This is the ID of the original issuer of the document. + + + + + + + + + + Issue Date. Example: 2017-01-13 + +Note: This is the date the document was originally issued. + + + + + Original Issue Location. Example: JFK + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + Original Ticket/ Document Number. Example: ??? + +Note: This is the document number comprised of the airline code, form code, and serial number. + + + + + + + + + + + + + COUPON-RELATED PRICING definition. + + + + + Booked Itinerary Pricing Date. Example: 2017-01-13 + +Note: This is the date the booked itinerary was priced. + + + + + Booked Itinerary Pricing Time. Example: 09:15 + +Encoding Scheme: ISO 8601 Military/ 24 Hour Format (HH:MM) + + + + + Pricing Location. Example: JFK + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + Booked Itinerary Pricing Country Code. Example: US + +Encoding Scheme: ISO 3166-1 (two character) Country Code + +Note: This is the code used to identify the country in which the booked itinerary was priced. + + + + + + + The document number, type and coupon numbers. + + + + + The ticket/document number. + + + + + The type of ticket/document. + +Encoding Scheme: IATA Padis Codeset - List for data element 1001 (Document/ Message Name, coded) + + + + + Associated Coupon Number(s). + + + + + + Coupon number. + + + + + + + + + + + + + COUPON TICKET DOCUMENT definition. + + + + + Coupon Document Number. + +Note: This is the document number comprised of the airline code, form code, and serial number. + + + + + + + + + + + Coupon Type. Example: Y (EMD-S Standalone) + +Encoding Scheme: IATA Padis Codeset - List for data element 1001 (Document/ Message Name, coded) + + + + + Coupon information. + + + + + + + + + Base Fare information. + +Note: Base, Base Net and Base Sell Amount may be specified. + + + + + Equivalent Fare information detailing conversion of filed fares or taxes from currency of filing to currency of payment. + +Note: Equivalent, Equivalent Net or Equivalent Sell Paid may be specified. + + + + + Fare information, as may be appliable in filed fares scenarios. + +Account code, net reporting code, nonendorsable and nonrefundable indicators, penalty restriction indicator, pricing system, statistical code and tour code. + + + + + Total Fare information. + +Note: Fare Total, Total Net and/ or Total Sell Fare may be specified. + + + + + Fare Calculation(s). + +Note: Fare calculation area, net amount, sell amount, pricing indicator and reporting indicator may be specified. + + + + + + BASE FARE TRANSACTION definition. + + + + + Base Fare Amount. Example 160 USD + + + + + + + + + + Total Fare Amount Type. Examples: ADC (Additional Charge); Bulk; IT (Tour Inclusive); NOADC (No Additional Charge) + + + + + Base Fare Transaction Purpose. Example: Base, Equivalent + +Note: This is used to indicate if this is base or equivalent fare transaction information. + + + + + + + EQUIVALENT FARE TRANSACTION definition. + + + + + Used to specify the equivalent, equivalent net or equivalent sell paid fare. Example 160 USD + + + + + + + + + + Equivalent Fare Transaction Purpose. Example: Base, Net, Refund, Sell + +Note: This is used to indicate if this is base or equivalent fare transaction information. + + + + + + Conversion rate. Example: 1.25 + +Note: This is the BSR and/ or BBR used to convert the tax/fee/charge filed amount from the filed currency into the tax/fee/charge amount in currency of country of payment. + + + + + + + + + COUPON-RELATED FARE INFORMATION definition. + +Account code, net reporting code, nonendorsable and nonrefundable indicators, penalty restriction indicator, pricing system, statistical code and tour code. + + + + + Validating Carrier-assigned Fare Rule Modification or Override information. + + + + + + Fare Rule Waiver Code. + +Note: This is a code assigned by the validating carrier that allows fare rule modification or override. + + + + + + + + + + Fare Waiver Rule Type. Examples: ExchangeReissued, FareComponent + + + + + + + + ATPCO Ticket Fare Category information. + + + + + + ATPCO fare category number. + + + + + + + + + + + + + + Detail information. + + + + + + Net Reporting Code. + +Note: This is a code indicating if the transaction is subject to a net reporting arrangement. + + + + + + + + + + Statistical code. + +Note; This is used for domestic or international sales differentiation. + + + + + + + + + + + Country code where the ticket is issued. Example: US + +Encoding Scheme: ISO 3166-1 (two character) Country Code + + + + + The two/three character IATA assigned code identifying the system used to price the itinerary for the document being issued. + + + + + + + + + + + TOTAL FARE TRANSACTION definition. + + + + + Used to specify the total or total net amount. Example 160 USD + + + + + + + + + + Total Fare Amount Type. Examples: ADC (Additional Charge); Bulk; IT (Tour Inclusive); NOADC (No Additional Charge) + + + + + Total Fare Transaction Purpose. Example: Base, Net, Refund, Sell + + + + + + Conversion rate. Example: 1.25 + +Note: This is the BSR and/ or BBR used to convert the tax/fee/charge filed amount from the filed currency into the tax/fee/charge amount in currency of country of payment. + + + + + + + + Reissue Sequence Number. Example: 2 + +Note: This is the sequence number assigned to each transaction amount. + + + + + + + + + + + COUPON-RELATED UNSTRUCTURED FARE CALCULATION definition. + + + + + Unstructured Fare Calculation Purpose. Example: Base, Net, Refund, Sell + +Note: This is used to indicate if this is base or equivalent fare transaction information. + + + + + Pricing Code. + +Note: This is the primary identifier reflecting the method of pricing for this transaction. + + + + + + + + + + Reporting Code. + +Note: This is a secondary identifier reflecting the method of pricing for this transaction used in the reporting process. + + + + + + + + + + Fare Calculation. + +Note: This is the fare calculation area that is required for ET. + + + + + + + + + + + + + + + Payment information. + + + + + + ACCEPTED PAYMENT FORM definition. + + + + + The form of payment type. Examples: Credit Card, Cash. + +Encoding Scheme: IATA PADIS code list data element [9888] Form of Payment Identification + + + + + The amount for this form of payment. Example: 300 USD + + + + + Used to specify if this is the old, new or orginal form of payment. + +Encoding Scheme: IATA PADIS code list [9988] Data Indicator + + + + + Information relating to prepayment vouchers. + + + + + + + + + + + + + + + + ORDER PAYMENT FORM definition. + + + + + The form of payment type. Examples: Credit Card, Cash. + +Encoding Scheme: IATA PADIS code list data element [9888] Form of Payment Identification + + + + + Payment Form Details. + + + + + + Information relating to prepayment vouchers. + + + + + + + + + + + + Check (Cheque) Payment + + + + + + + + The amount for this form of payment. Example: 300 USD + + + + + + The person who is paying for an Order is not a passenger + + + + + + Ref to Contact Information of the Order's Payer. The information can be a company, or include the name details of the individual paying. + + + + + + + + + + + PAYMENT METHOD definition. + + + + + Payment Method detail. + + + + + + Used to specify if this is the old, new, or orginal form of payment. + +Encoding Scheme: IATA PADIS code list 9988 - Data Indicator + + + + + + + + + + + + + Check (Cheque) Payment + + + + + Applied Promotions for this payment form. + +Note: If specified, this individual payment form information will override any globally specified promotion information. + + + + + + Promotion Detail. + + + + + + + + Association(s), including Passenger and Group. + + + + + + + + + + + + + + + + + + + ORDER PAYMENT METHOD definition. + + + + + + The form of payment type. Examples: Credit Card, Cash. Encoding Scheme: IATA PADIS code list data element [9888] Form of Payment Identification + + + + + + Payment Method detail. + + + + + + + + + + + + + + Check (Cheque) Payment + + + + + + + + + + The amount for this form of payment. Example: 300 USD + + + + + + + Used to specify if this is the old, new, or orginal form of payment. Encoding Scheme: IATA PADIS code list 9988 - Data Indicator + + + + + + + Applied Promotions for this payment form. Note: If specified, this individual payment form information will override any globally specified promotion information. + + + + + + + Promotion Detail. + + + + + + + + Association(s), including Passenger and Group. + + + + + + + + + + + + + Payment Information Association(s). + + + + + + Associated Order ID Example: ORDER7333 + + + + + Associated Order Item ID(s). Example: ORD7333-001 + + + + + + Passenger(s)/ Groups associated with the Offer Item. Note: This contains references to Passenger and Group instance(s) defined in the Passengers node. + + + + + + + + Association to multiple Passenger instance(s). Example: pax1 pax2 + + + + + + + + + + + Other Named Association(s). Note: Includes an association type choice (e.g. MediaGroup) and an instance association value (e.g. mediagrp1). + + + + + + + Named Instance Association Type. Examples: CarryOnAllowance, MediaGroup + + + + + + + Associated object instance value. Example: mediagrp1 + + + + + + + + + + + + + When true, this is a split form of payment. + + + + + + + + NDC XML SPECIFICATION: PRICE CLASS XML OBJECT + + + Notice: This is NDC Draft Specification provided for pre-review by the members of the relevant governance groups, it is not provided for implementation in a production environment or considered to be the final schema to support NDC business requirements. The draft schema may, at any time up to final specification submission, undergo changes including, but not limited to, specific elements, element names/labels, annotations or message name as a result of the ongoing quality control process, and comments, which may be received following the pre-review. Implementation of this version is done so at the risk of the implementer or implementing company. + + + + + + PRICE CLASS definition. + + + + + Price class name. Example: SUPERSAVER + + + + + Price class code. Example: 1, ABC + + + + + + Fare Basis Code with optional application. Example: Y26 + + + + + + The Airline requested default display order (in a client application) for this price class. Example: 2 + + + + + + Object globally unique Instance ID. Example: obj1 + + + + + + + NDC XML SPECIFICATION: NDC SEAT XML Object. + + + Notice: This is NDC Draft Specification provided for pre-review by the members of the relevant governance groups, it is not provided for implementation in a production environment or considered to be the final schema to support NDC business requirements. The draft schema may, at any time up to final specification submission, undergo changes including, but not limited to, specific elements, element names/labels, annotations or message name as a result of the ongoing quality control process, and comments, which may be received following the pre-review. Implementation of this version is done so at the risk of the implementer or implementing company. + + + + + + + CORE SEAT definition. + + + + + Seat Location information. + + + + + + + + DETAIL SEAT definition. + + + + + + + Seat Details, including Marketing Name, Description(s), Feature(s), Size and Keywords. + + + + + + + + + SEAT LOCATION definition. + + + + + Seat column. Example: A + + + + + + + + + + Seat row number and row characterisitcs + + + + + + Seat row number. Example: 2 + + + + + Row characteristic. +Examples: +A (Extra Leg Room) +B (Buffer Row) +MV (Row With Movie Screen) + +Encoding Scheme: IATA PADIS Code List for data element 9864 - Row Characteristic + + + + + Seat Details for the entire Row. + + + + + + + + + + + + + + Seat row Characteristic(s). + + + + + + Refers to aircraft seat characteristics; seat option codes. Examples: E (EXIT ROW), M (Middle Seat), A (Aisle seat), L (Left side of aircraft), Q (Bulk Head). Refer to PADIS code list 9825. + + + + + + + + Additional Seat Remark(s). + + + + + + + + + + + + + + + + SEAT CHARACTERISTICS definition. + + + + + + + Media Content Seat Camera Position information. + + + + + Row information for graphical seat maps, to indicate link or images to the entire section defined by the range. + + + + + + Row number value. +Example: 11 + + + + + Icon placement (in orientation to cabin row or column). + +Examples: +FRO (Place icon before row) +INL (Place icon inline with row or column) +LEF (Place icon left of column) +REA (Place icon behind row) +RIG (Place icon right of column) + +Encoding Scheme: IATA PADIS code list COT - Camera Orientation Type + + + + + + + + Column position information used for graphical seat map constructions (ie image or link to the entire section as indicated by the defined range). + + + + + + Column position value. +Example: C + + + + + Icon placement (in orientation to cabin row or column). + +Examples: +FRO (Place icon before row) +INL (Place icon inline with row or column) +LEF (Place icon left of column) +REA (Place icon behind row) +RIG (Place icon right of column) + +Encoding Scheme: IATA PADIS code list COT - Camera Orientation Type + + + + + + + + + + Seat size and marketing information definition. + + + + + + + Associated Keyword Unit of Measure, if relevant. Example: INCH + + + + + + + Lowest Pitch Measurement value for this section. Example: 32 + + + + + Lowest Width Measurement value for this section. Example: 20 + + + + + + Seat Description Key-Value Word Pairs. +Examples: +ReclineDegree - 25 +BedLengthLowEnd - 68 +BedLengthHighEnd - 78 +WidthLowEnd - 20 +WidthHighEnd - 21.5 +PitchLowEnd - 32 +PitchHighEnd - 34.4 + + + + + + + Key-Value detail. + + + + + + + + + + Images and/or links for the entire section defined by the range of rows. + + + + + + + + + + + + SEAT MAP COMPONENT MEDIA and MESSAGE definition. + + + + + Images applicable to this section + + + + + + Image ID defined in root node MediaContent. +Examples: +IMG713 +SFO_LOUNGE + + + + + Camera position on seat map information. + =notes= +1. This is the desired position where camera icon or equivalent needs to be positioned on a seat map. + + + + + + + + Links applicable to this section + + + + + + + Camera position on seat map information. + =notes= +1. This is the desired position where camera icon or equivalent needs to be positioned on a seat map. + + + + + + + + Marketing message for all seats in this section. + + + + + + + + Aircraft seat row with seat map ghost row metadata definition. + + + + + + + + + NDC XML SPECIFICATION: Transaction Security data components. + + + disclaimer: This is NDC Shopping Draft Specification provided for pre-review by the members of the relevant governance groups, it is not provided for implementation in a production environment or considered to be the final schema to support NDC shopping requirements. The draft schema may, at any time up to final specification submission, undergo changes including, but not limited to, specific elements, element names/labels, annotations or message name as a result of the ongoing quality control process, and comments, which may be received following the pre-review. Implementation of this version is done so at the risk of the implementer or implementing company. + + + + Message Security information. + + + + + + + + + + A data type for Message Security. + + + + + Agent duty code + + + + + Agency IATA number + + + + + Pseudo City code. Example: AAA2 + + + + + + + Defines where the PCC was created. For example 1A, 1P, 1S + + + + + + + + + LNIATA Number – CRT Address/Terminal ID + + + + + ERSP Number: The eight digit IATA +assigned ERSP code. + + + + + Department/Identifier + + + + + Carrier/GDS Department Code + + + + + Airline specific codes applicable for the Services record owner or the carrier specified in bytes 23-25, defined as follows: +Code Definition +RES = all reservation centers +ATO = all airline ticket offices +CTO = all city ticket offices +WEB = website + + + + + + + + + + + + + + + + NDC XML SPECIFICATION: OPTIONAL SERVICE XML OBJECT + + + + + + A data type forService Combination Rule constrained list. + + + + + + + + + + A data type for Service Combination Rule. + +Examples: CombinationOK, DoNotCombine, Other + + + + + + A data type for Service Coupon Type constrained list. + + + + + + + + + + + + + A data type for Service Coupon Type. + +Examples: E-Ticket, Flight, No_EMD, Standalone, Ticket, Other + + + + + + A data type for Service Associations. + + + + + + + + + + + + + + A data type Service Association Type Name. + + + + + + + Service Associations. + + + + + Passenger and/or PTC that the offer applies to. + + + + + + When true, this Baggage Offer applies to all specified Passengers. + + + + + Association to multiple Traveler instance(s). Example: Traveler1 Traveler2 + +Note: May be Recognized or Anonymous Traveler (by PTC) instance(s). + + + + + + + + Flight that the offer applies to. + + + + + + When true, this Baggage Offer applies to all specified flights. + + + + + When true, this Baggage Offer applies to all specified flight Origin/ Destination Pairs. + + + + + When true, this Baggage Offer applies to all specified flight Segments. + + + + + + + + + + + + Offer Item Association. + + + + + + + + + + Other association(s). + + + + + + + + Other Service Associations. + + + + + Other Association Detail. + +Note: Includes an association type choice (e.g. MediaGroup) and an instance association value (e.g. mediagrp1). + + + + + + Named association type. Example: MediaGroup, SSR + + + + + + + Value of the SSR code. + + + + + + + + + Associated object instance value. Example: mediagrp1 + + + + + + + + + + + Reason For Issuance Code +Examples: +A (Air Transportation) +C (Baggage) +E (Airport Services) +F (Merchandise) +G (In-flight Services) +Refer to PADIS Codeset for data element 4183 - Special Condition. + + + + + OPTIONAL SERVICE CORE definition. + + + + + + Service name. Example: Lounge Pass + + + + + + + + + + Service Codes and Reason for Issuance. + + + + + + Two character generic code to identify ticket level charges, fees and taxes. + + + + + + + + + + SERVICE Description. + +Note: Supports plain text, multimedia and code and link references. + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + Optional SERVICE PRICE. + +Notes: This Price amount may be set to zero if pricing has been applied at the Offer Item level. + + + + + Optional service booking instructions to include SSR, OSI and Upgrade Method. + + + + + + Passenger assistance SSR code value. +Examples: +EXST (EXTRA SEAT REQUIRED) +INFT (INFANT ACCOMPANYING ADULT PASSENGER) +PETC (PASSENGER TRAVELING WITH PET IN CABIN) +UMNR (UNACCOMPANIED MINOR) + +For maximum interoperability, it is recommended that IATA (four character) Special Service Request (SSR) Code values be used. Select an enumerated value from the list of enter a four character SSR code string. + +=notes= +1. Although optional in the schema, some SSR codes may require associated description elements. + + + + + Other service information (OSI) text. +Example: PAX VIP MEMBER OF PARLIAMENT + + + + + PNR booking method. +Example: AE (BY SSR - SPECIAL SERVICE REQUEST) + +For maximum interoperability, refer to IATA PADIS Code List for data element 9750. Select a code value or enter a value that is bilaterally agreed upon between trading partners. + + + + + Upgrade method. +Example: AE (BY SSR - SPECIAL SERVICE REQUEST) + +For maximum interoperability, refer to IATA PADIS Code List for data element 9750. Select a code value or enter a value that is bilaterally agreed upon between trading partners. + + + + + + + New class of service. +Example: B + + + + + + + + + Data center instructions. + + + + + Aircraft equipment information. + + + + + + + + Validating Carrier Airline Designator. +A two-character alpha-numeric code assigned according to the IATA Resolution 762 or a three-letter airline designator assigned by ICAO. Refer to IATA Airline Coding Directory . Example: BA + + + + + Other Service Association(s). + + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + In concert with BaggageDeterminingCarrier data field, specifies the reason for the carrier code. + +Encoding Scheme: IATA PADIS Code List for data element RES. + + + + + + + Object globally unique Instance ID. Example: obj1 + + + + + + OPTIONAL SERVICE DETAIL definition. + + + + + + + Detailed Service information, including Service Bundle, Service Combinations, Service Coupon, Service Fulfillment and Service Quantity Rules. + + + + + + + + + + + + + + + + + OPTIONAL SERVICE TO BE PRICED definition. + + + + + Service Codes and Reason for Issuance. + + + + + Fulfillment detail. + + + + + + Service Fulfillment Period. + +Note: This is the start and end date/time period(s) the service may be fullfilled or used. + + + + + + The EARLIEST date the associated optional service is available or may be used. Example: 2017-01-13 + + + + + + + + + + The LATEST date the associated optional service is available or may be used. Example: 2017-03-13 + + + + + + + + + + + + + Information about the company or party that will fulfill the service. + + + + + Information about the location where the service will be fulfilled. + + + + + + . + + + + + + + + + + + + + Flight, Flight Segment and/ or Traveler association(s). + + + + + + + + + + + Exclude=false , Include=true, Default value is true + + + + + + + + OPTIONAL SERVICE ENCODING definition. + +Note: Includes IATA Optional Service Reason for Issuance Code (RFIC) code and Issuance Sub Code. + + + + + + Indicator if this option is a discount or a surcharge or a fee formula calculation. Refer to PADIS Codeset SFB for Service Fee Basis + + + + + Service code. Examples: +XLEG (Extra Leg Room Seat, implementer encoding) +XBAG (Extra Bag, implementer encoding). +Used in conjunction with SubCode (Associated Reason For Issuance SubCode). + + + + + + + + + + Associated Reason For Issuance Sub Code. + +Examples: +0CC (First Checked Bag) +0B1 (In-flight Entertainment) +0BX (Lounge) +0B3 (Meal/ Beverage) +0B5 (Pre-reserved Seat Assignment) +0G6 (Priority Boarding) + +Are these on an IATA Codelist or do they need to be added via FastTrack? + + + + + + + + + + + + + + A data type for Optional Service Descriptions. + + + + + Service Description detail. + + + + + + + + Description Application. Examples: SEAT 3B, Discount 15P + + + + + + + + + + + + + + OPTIONAL SERVICE FILTER definition. + + + + + Identifies additional services codes, and may refer to ATPCO additional services information or airline specific/ bilaterally agreed codes. + + + + + + + + + + Service Sub-Group Code(s). + +Group BG: CT (Container), PP (Pre-Paid Excess Baggage) +Group IE: IT (Internet Access), TV (Television) + + + + + + + + + + + + + + + + Service Fulfillment Airport Location. + + + + + Physical address where service fulfillment will occur. + + + + + OPTIONAL SERVICE FULFILLMENT representation, including Date/ Time Period, Location, Fulfillment Company. + + + + + Service Fulfillment Period. + +Note: This is the start and end date/time period(s) the service may be fullfilled or used. + + + + + + The EARLIEST date the associated optional service is available or may be used. Example: 2017-01-13 + + + + + + + + + + The LATEST date the associated optional service is available or may be used. Example: 2017-03-13 + + + + + + + + + + + + + Information about the company or party that will fulfill the service. + + + + + Information about the location where the service will be fulfilled. + + + + + + + + + + + + + + OPTIONAL SERVICE AIRPORT LOCATION representation. + +Airport Location Code. Example: TPA + +Encoding Scheme: IATA/ A4A (three character) Airport or City Code + + + + + + + + + OPTIONAL SERVICE ADDRESS LOCATION representation. + + + + + + + + + A data type for Optional Service Price. + + + + + Total price. Example: 6000 USD + +Note: This is the total price INCLUDING base price, taxes and fees/ surcharges. + + + + + Amount or Percent value indicating the refund value of the service. + + + + + + Price breakdown amount in currency. Example: 800 USD + +Note: This is the individual price excluding base price, taxes and fees/ surcharges. + + + + + Commission percentage. Example: 20 + + + + + + + + Price breakdown details. + + + + + + Price breakdown sub-total. + +Notes: +1. This is the total all price breakdown items, excluding tax and/ or surcharge. +2. Subtotal may be specified as Currency (simple and detail); Award/ Redemption; or combination of Partial Currency and Award Redemption. + + + + + + + + + + + + + + Price details. + +Note: This price does not include taxes and fee/ surcharges. + + + + + + Price application. Example: Base Fare + + + + + Price breakdown amount. Example: 60 USD + +Notes: +1. This is the individual price excluding base price, taxes and fees/ surcharges. + + + + + + + + + + + Ticket Tax/fee/charge details to indicate taxes that apply to country of commencement of travel and routing. + + + + + Individual fee/ surcharge information would appear on the accountable document. + + + + + + + + + + Optional SERVICE COMBINATIONS. + +Note: This contains Optional Services that may or may not be combined with one another. + + + + + + + + + + Optional SERVICE FULFILLMENT, including Date/ Time Period, Location, Fulfillment Company. + + + + + Optional SERVICE COUPON Information, including Fee Basis and Coupon Type. + + + + + Minimum and Maximum Service Ordering Quantity. + + + + + SERVICE COMBINATION RULES representation. + + + + + Service Combination detail. + + + + + + Service Combination Rule. +Examples: Permitted, NotPermitted, Other + + + + + + + + + + + + + + A data type for Optional Service Coupon. + + + + + Instant purchase type. +Examples: +CC (Ticketless purchase immediately charged to credit card) +NO (Not an instant purchase) +TT (Simultaneous with time of ticketing) + +Encoding scheme: IATA PADIS Codeset IPT - Instant Purchase Type + + + + + Service fee basis. +Examples: +DIS (Option directly applied to fare) +FEE (Baggage only) +FNA (Item is not available/ applicable) +INC (Item is free of charge) +NAP (Item not applicable/ available) +SUR (Surcharge) + +Encoding Scheme: IATA Padis Codeset - List for data element SFB - Service Fee Basis + + + + + Contains instruction on what type of traffic document should be issued for an optional service. + +Examples: +EMD Associated +EMD Standalone +No EMD +Electronic Ticket + + + + + + + + + + + + MINIMUM/ MAXIMUM Service Ordering Quantity definition. + + + + + The MINIMUM Quantity of the Service Item that may be ordered. +Example: 2 + + + + + The MAXIMUM Quantity of the Service Item that may be ordered. +Example: 4 + + + + + + + + "A unique Service ID that has been returned in the Shopping results, and identifies an airline service item (ie a product or a service) that can be separately delivered and uniquely described by an airline. + +Example: SRVC-2B88-4C33-9787-9461114BC9BE" + + + + + UNIQUE SERVICE ID representation. + +The airline-assigned unique Service ID. Example: SRVC_ccecc4aa-791867b9b2e6 + + + + + + + Airline designator or CRS code of the owner/ assigner of the Offer ID, typically used for offer ordering purposes. Example: UA, BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline or CRS Designator Code + + + + + + + + + NDC XML SPECIFICATION: Base Structures, including base types for NDC XML data objects, utility xml objects and core simple type definitions. + + + Notice: This is NDC Draft Specification provided for pre-review by the members of the relevant governance groups, it is not provided for implementation in a production environment or considered to be the final schema to support NDC business requirements. The draft schema may, at any time up to final specification submission, undergo changes including, but not limited to, specific elements, element names/labels, annotations or message name as a result of the ongoing quality control process, and comments, which may be received following the pre-review. Implementation of this version is done so at the risk of the implementer or implementing company. + + + + + + + A data type for Flight Origin with Additional Location Preference and Date/Time Qualifiers. + + + + + Airport or a city code. Use a three letter location identifier assigned according to the IATA Resolution 763. Refer to IATA Airline Coding Directory . Example: TPA +Notes: + +1. A proximity search, e.g. within 25 miles, may be specified using the Radius attributes. + +2. A preference level for the specified location code may specified using the Preference attributes. + + + + + + + Preference Level for specified Airport or City code. + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Departure date. Example: 2017-01-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + Departure time. Example: 09:15 + +Encoding Scheme: ISO 8601 Military/ 24 Hour Format (HH:MM) + + + + + Lead Pricing information used in calendar shopping scenarios. + + + + + + + + + + + + + + A data type for Flight Destination with Additional Location Preference and Date/Time Qualifiers. + + + + + Airport or a city code. Use a three letter location identifier assigned according to the IATA Resolution 763. Refer to IATA Airline Coding Directory . Example: TPA +Notes: + +1. A proximity search, e.g. within 25 miles, may be specified using the Radius attributes. + +2. A preference level for the specified location code may specified using the Preference attributes. + + + + + + + Preference Level for specified Airport or City code. + + + + + Search Radius for specified Airport or City code. + + + + + + + + + Arrival (destination) date. Example: 2017-02-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + Arrival (destination) time. Example: 09:15 + +Encoding Scheme: ISO 8601 Military/ 24 Hour Format (HH:MM) + + + + + Lead Pricing information used in calendar shopping scenarios. + + + + + + + + + + + + + + Affinity Shopping Query FLIGHT DEPARTURE (Origin) AIRPORT/ CITY information. + + + + + A data type for Affinity Query State or Province Flight Departure (Origin) information. + + + + + State or Province Departure (origin) information. + + + + + + + A data type for Affinity Query State or Province Flight Arrival (Destination) information. + + + + + State or Province Arrival (destination) information. + + + + + + + A data type for Affinity Query Country Flight Departure (Origin) information. + + + + + Country Departure (Origin) information. + + + + + + + A data type for Affinity Query Country Flight Arrival (Destination) information. + + + + + Country Arrival (Destination) information. + + + + + + + A data type for Affinity Query Reference Point Flight Departure (Origin) information. + + + + + Reference Point Departure (Origin) information. + + + + + + + A data type for Affinity Query Reference Point Flight Arrival (Destination) information. + + + + + Reference Point Arrival (Destination) information. + + + + + + + Affinity Shopping Query FLIGHT ARRIVAL (Origin) AIRPORT/ CITY information. + + + + + Affinity Shopping Query FLIGHT DEPARTURE (Origin) COUNTRY information. + + + + + Affinity Shopping Query FLIGHT ARRIVAL (Origin) COUNTRY information. + + + + + Affinity Shopping Query FLIGHT DEPARTURE (Origin) REFERENCE POINT information. + + + + + REFERENCE POINT RADIUS QUERY representation. + + + + + Reference Point(s), e.g. Cities and Metro Areas. + + + + + + Reference Point Name or Code. Examples: TAMPA, TPA + + + + + + + + + + + + + + + Reference Point Proximity. + +Notes: +1. This contains either the requested maximum distance search radius values -or- the actual Proximity information, which is typically used to specify the results from the named location radius search. + + + + + + Reference Point Name or Code. Examples: TAMPA, TPA + + + + + + + + + + + + Proximity Data Application. Example: SearchRadius, ActualProximity, Other + + + + + The actual distance value from the named location search. Example: 20 + + + + + + + Distance unit of measure. Examples: Miles, Kilometers + + + + + + + + + + + + + + + Affinity Shopping Query FLIGHT ARRIVAL (Origin) REFERENCE POINT information. + + + + + Affinity Shopping Query FLIGHT DEPARTURE (Origin) STATE or PROVINCE information. + + + + + Affinity Shopping Query FLIGHT ARRIVAL (Origin) STATE or PROVINCE information. + + + + + + DATE-based Lead Period(s). + + + + + TIME-based Lead Period(s). + + + + + LEAD DATE PERIOD representation. + +Notes: Supports Calendar Shopping. Days, Months, etc. before and/ or after the specified date. + + + + The period duration to be applied BEFORE (prior to) the specified date. Examples: +P3D (three days) +P7D (seven days) + + + + + The period duration to be applied AFTER the specified date. Examples: +P3D (three days) +P7D (seven days) + + + + + + + LEAD TIMES PERIOD helper object. + +Notes: Supports Calendar Shopping and Departure/ Arrival Time preferences. + + + + The period duration to be applied BEFORE (prior to) the specified time. Examples: +P3D (three days) +PT2H (two hours) + + + + + The period duration to be applied AFTER the specified time. Examples: +P3D (three days) +PT2H (two hours) + + + + + + + + + Discount Program Qualifiers; fare type for this PTC. +Notes: +1. Supports pricing discounts and/ or other benefits from membership in Travel Discount Programs, such as AARP and AAA. +2. Discount Programs may be associated to individual Travellers but will apply to ALL Travellers if no associations are specified. + + + + + A data type for a Discount Program Qualifier. + + + + + Membership account or ID number. Example: 0956301007 + + + + + + + + + + + + Code for an organization or assocIation which owns or sponsors a particular discount program which an airline may support (discount progam support could be in on a bilateral basis). + +Examples: AARP, AAA. + + + + + + + + + + Program name. +Example: AARP MEMBERSHIP + + + + + + + + + + + + + + AIRLINE INCENTIVE Program Qualifiers. + +Notes: +1. Supports pricing discounts and/ or other benefits from membership (business, group and individual) in an airline-sponsored Incentive Program. + +2. Incentive Programs ARE NOT Frequent Traveler Loyalty (FQTV) programs. + +3. Incentive Programs may be associated to individual Travelers but will apply to ALL Travelers if no associations are specified. + + + + + + + + + + A data type for Incentive Program Qualifier. + + + + + Incentive program name. +Example: RFSB (Reward for small businesses) + + + + + Corporate or individual membership account identification for an airline sponsored incentive program (Incentive Programs are NOT Frequent Traveler Loyalty (FQTV program). Example: IBM123 + + + + + + + + + + + + + Designator of airline offering the incentive program. Example: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Code + + + + + Member or participant status within the program. Examples: VP, DIRECTOR, EXEC + + + + + + + + + + + + + + + + PRE-PAID TRAVEL Programs. + +Notes: +1. Supports pricing flight offers and/ or other benefits from non-revenue and Air Pass Program certificates. + +2. Each Prepaid Travel Program MUST be associated to ONE individual Traveler. + + + + + + A document which can be prepaid or book of coupons to be purchased up-front + + + + + + + Program issuing airline designator code. Example: BA + +Encoding Scheme: IATA/ A4A (two to three character) Airline Designator Code + + + + + Certificate information. + + + + + + Unique certificate number. Example: 12345678 + + + + + + + + + + + + Certificate Application. Example: Billing + + + + + Certificate Effective/ Expiration Period. + + + + + + + + + + + + + + + + + + + + + + + Program Name. Example: PASSPRO + + + + + + + + + + Program Code. Example: PP01 + + + + + Agency or Corporate Certificate holder or program owner information. + + + + + + + + + + + + + + + + + + + Programs Status Qualifier. + +Example: Elite status. + + + + + + Program status name. + + + + + + + + + + A data type for Credit Card Qualifier. + + + + + The two letter payment card type. Examples: MC, VI + + + + + + + + + + + Payment card IIN/ BIN number. Example: 401123 + +Note: This is the first 6 digits of a credit card number known as the Issuer Identification Number (IIN), previously known as bank identification number (BIN), that identifies the institution that issued the card to the card holder. + + + + + + + + + + + + + + If True, the amount value represents a percentage. + + + + + + + A data type for Social Media Qualifier. + + + + + Social media service/ program name. Examples: FACEBOOK, TWITTER + + + + + + + + + + User or profile identification. +Example: JOHNSMITH2367 + + + + + + + + + + + + Email address. Example: John.Smith@Here.com + + + + + + + + + + + + + + Start and End Date Range with Minimum/ Maximum Stay Duration. + + + + + A data type for Start and End Date Range with Minimum/ Maximum Stay Duration. + + + + + Starting Date of the stay period range. Example: 2016-01-13 + + + + + Ending Date of the stay period range. Example: 2016-03-13 + + + + + Minimum Stay Period within the specified date range. +Examples: P5D (five days) + + + + + Maximum Stay Period within the specified date range. +Example: P10D (ten days) + + + + + + + + Season (Months/ Quarters) with Minimum/ Maximum Stay Duration. + + + + + A data type for Season (Months/ Quarters) with Minimum/ Maximum Stay Duration. + + + + + + + + + Minimum Stay Period within the specified calendar season. +Examples: P5D (five days) + + + + + Maximum Stay Period within the specified calendar season. +Example: P10D (ten days) + + + + + + + + + GROUP (ALL TravelerS) Budget information. + + + + + A data type for GROUP BUDGET Qualifier. + + + + + Budgeted amount for ALL TravelerS. +Example: 17000 USD + + + + + + + + + + + + Allows to specify travel budget in a shopping request, on per individual traveler baisis, mainly in "affinity" type shopping requests. + + + + + A data type for PER PERSON BUDGET Qualifier. + + + + + Budgeted amount PER PERSON. +Example: 1700 USD + + + + + + + + + + + + + BAGGAGE PRICING Qualifiers. + + + + + BAGGAGE PRICING Qualifier. + + + + + Qualifier to specific the type of Baggage pricing. +Example: Checked Bag + +Encoding Scheme: IATA PADIS Code List for data element OPT. + + + + + Request action. Example: 131 (DISPLAY ONLY) + +Encoding Scheme: IATA PADIS Code List for data element 1225 + + + + + Allowance catalog requested. Example: C (CATALOG ONLY) + + + + + + Allows POA to tell the ORA if the ORA may alter the POA’s pre-paid baggage charges + +If True: prepaid charge may NOT be altered +If False: prepaid charge MAY be altered + + + + + Bi-lateral agreement identifier, i.e. - baggage cost, Baggage Determining Carrier, etc. + + + + + If True, The ORA advises the POA that the POA is given the Baggage Determining Carrier designation. + + + + + + If True, POA is requested to return the settlement value for the baggage. + + + + + + EXISTING ORDER Qualifier. + + + + + + + + + Existing Booking Reference (e.g. PNR Record Locator). Example: R1A3SK + + + + + + + + + + A data type for Shopping Request Business Object: SPECIAL FARE Qualifiers. + + + + + + Company profile index associated with this special fare. Example: COM1234 + + + + + + + + + + + + + Contract ID used for pricing special fares. Example: 675124 + + + + + + + + + + + + Corporate account name or ID used for pricing special fares. Example: 675124 + + + + + + + + + + + + + + + + Contains card type, and Issuer Identification Number. + + + + + DISCOUNT, INCENTIVE and PRE-PAID PROGRAM Qualifer. + + + + + + Program Qualifier detail. + + + + + + + + + Promotion(s) Information. + +Notes: +1. Supports pricing discounts and/ or other benefits for Travelers with Promotion Codes issued (or sponsored by) Airlines, Travel Agencies and/ or Companies. + +2. Promotion Codes may be associated to individual Travelers but will apply to ALL Travelers if no associations are specified. + + + + + + + Country where the Credit Card was issued. + + + + + + + + + A data type for Shopping Request Business Object: PROGRAM Qualifiers. + + + + + Discount Program Qualifiers; fare type for this PTC. +Notes: +1. Supports pricing discounts and/ or other benefits from membership in Travel Discount Programs, such as AARP and AAA. +2. Discount Programs may be associated to individual Travellers but will apply to ALL Travellers if no associations are specified. + + + + + + + + + + A data type for Shopping Request Business Object: PROMOTION CODE Qualifiers. + + + + + + + + A data type for Shopping Request Qualifiers. + + + + + Qualifier choices. + + + + + + + + + + + + + + + SEAT Qualifier. + + + + + + Seat assignment information. + + + + + + + + + + + + + + + + + Element to associate seat to a Traveler and s flight segment. + + + + + + + + + + + Optional Services to INCLUDE/ EXCLUDE in Pricing Qualifiers. + + + + + Social Media Account information. + +Notes: +1. Supports benefits for social media account holders. + +2. Each Social Media Account MUST be associated to ONE Traveler. + + + + + Special fares, which may be private or negotiated fares. + +Notes: +1. Supports pricing discounts and/ or other benefits for Travelers affiliated with companies with private fare and/ or negotiated rate contracts. + +2. Private Fares apply to ALL Travelers. + + + + + Passenger Special Needs Attributes. + +Notes: +1. Supports specification of Traveler special needs in both IATA SSR encoding and non-IATA encoding. + +2. Special Needs may be associated to individual Travelers but will apply to ALL Travelers if no associations are specified. + +3. Special Needs may be associated to flight segments but will apply to ALL flight segments if no associations are specified. + + + + + A data type for Shopping Request Business Object: SOCIAL MEDIA Qualifiers. + + + + + + + + A data type for Shopping Request Business Object: SPECIAL NEED Qualifiers. + + + + + + + + TRIP PURPOSE Qualifier. + + + + + + + AIRLINE SUPPLIER Preferences. + + + + + AIRLINE ALLIANCE PROGRAM Preferences. + + + + + AIRLINE SUPPLIER Preferences. + + + + + Airline Supplier information. + + + + + + + Geographical indicator type. Example: DOM (DOMESTIC/ DOMESTIC) + +Encoding Scheme: IATA Padis Codeset - List for data element 9970 (Product Details Qualifier) + + + + + Flight haul length type. Example: LH (LONG-HAUL 6 HRS PLUS) + +Encoding Scheme: IATA Padis Codeset - List for data element FHT (Flight Haul Type) + + + + + + + + + + + + + AIRLINE ALLIANCE PROGRAM Preferences. + + + + + Used to specify the alliance CodeSet. Refer to IATA PADIS Code List for data element 9906. + + + + + + + + Geographical indicator type. Example: DOM (DOMESTIC/ DOMESTIC) + +Encoding Scheme: IATA Padis Codeset - List for data element 9970 (Product Details Qualifier) + + + + + Flight haul length type. Example: LH (LONG-HAUL 6 HRS PLUS) + +Encoding Scheme: IATA Padis Codeset - List for data element FHT (Flight Haul Type) + + + + + + + + + + + + + + A data type for Best Pricing Method Preference. + + + + + Best Available Fare Pricing Method. +Examples: +Y (BEST FARE IN SAME CABIN CLASS) +C (BEST FARE ACROSS ALL CABIN CLASSES) +N (PRICE ACCORDINGLY TO OTHER DESIGNATED PRICING PARAMETERS) + + + + + + BEST FARE IN SAME CABIN CLASS + + + + + BEST FARE ACROSS ALL CABIN CLASSES + + + + + PRICE ACCORDINGLY TO OTHER DESIGNATED PRICING PARAMETERS + + + + + + + + + + Cabin Preferences. + + + + + A data type for Cabin Preferences. + + + + + + + + + A data type for Fare Preferences. + + + + + Fare Type(s) with preference level. + + + + + + Fare type. Examples: 70J-Published Fares, 749-Negotiated Fares, 756-One Way Fare, +758-Private Fares + +Encoding Scheme: PADIS codeset element 9910 - Fare Qualifier + + + + + + + + + + + + + + + A code that gives information regarding the type of fare, class entitlement, minimum and maximum validity, reservations entitlement, seasonality, days of travel and advertising or sales restrictions. + + + + + + Fare Basis Code with optional application. +Example: Y26 +Used in conjunction with Application (Requested, Ticketed, Other) + + + + + + + + + + + + + + + + The applicable code as provided for in A4A SIPP Resolution 110.16 or IATA Resolution 728. Further ticket +designators will be reported at the Fare Component level as matched from a Ticket Discount, ATPCO +Category 35, Category 25 or Category 19-22. + + + + + + + Ticket designator detail. + + + + + + + + + + + + + + + + Contains indicators allowing for different restricted fare types to be be excluded. + + + + + + + When true, do not return fares with minimum stay restrictions. + + + + + When true, do not return fares with maximum stay restrictions. + + + + + When true, do not return fares with advance purchase restrictions. + + + + + When true, do not return fares with penalties. + + + + + + + + Group Fare preferences by passenger type. + + + + + + + + + A data type for Flight Preferences. + + + + + Aircraft Features, including Equipment, Cabin Type, Class of Service, Seats, Rows and Tail Number. The IATA aircraft type; use SSIM Appendix A. + + + + + + Aircraft Equipment. + + + + + + + + + + + Cabin Class. + + + + + + Cabin type. Examples: First Class, Business Class + +Encoding Scheme: PADIS codeset element 9873 - Cabin Class of Service + + + + + + + + + + + + + + + + Desired Class(es) of Service. +Example: Y + + + + + + Class of Service. Example: Y + + + + + + + + + + + + + + + + + Seat(s). + + + + + + Seat characteristic value. Example: L (LEG SPACE SEAT). Refer to PADIS code list 9825. + + + + + + + + + + + + Refers to position on the aircraft; seat option codes. Examples: E (EXIT ROW), M (Middle Seat), A (Aisle seat), L (Left side of aircraft), Q (Bulk Head). Refer to PADIS code list 9825. + + + + + + + + + Seat Row Number. Example: 3 + + + + + + + + + + + + + + Cabin Row Number(s) and Row Feature(s) to specify in preferences. + + + + + + Row feature value. Example: E (EXIT ROW) + +Encoding Scheme: IATA PADIS Code List for data element 9864 + + + + + + + + + + + + Preferred row number. Example: 10 + + + + + + + + + + + + + + + Aircraft Features. + + + + + Aircraft Tail Number(s). + + + + + + + + + Flight Characteristics, e.g. non-stop, red eye, etc. + + + + + + Non-Stop Flight preference level. Examples: Preferred, Exclude + + + + + + + Preference Level Context. Example: MyContext + + + + + + + + + Shopping preference for unticketed stop flight preference + + + + + + + Preference Level Context. Example: MyContext + + + + + + + + + Flights with overnight lodging preference. + + + + + + + Preference Level Context. Example: MyContext + + + + + + + + + Flights with change of airport preference. + + + + + + + Preference Level Context. Example: MyContext + + + + + + + + + Red eye flight preference. + + + + + + + Preference Level Context. Example: MyContext + + + + + + + + + + + + + Wait Listing. + + + + + + Wait-Listing Shopping preference level. + + + + + + + Preference Level Context. Example: MyContext + + + + + + + + + + + + + + + + FLIGHT Preferences, including Aircraft, Flight Characteristics, Connections and Wait Listing. + + + + + FARE Preferences, including Fare Type, Fare Basis Code, Ticket Designator and Fare Exclusions. + + + + + A data type for Maximum Flight Segment Travel Time. + + + + + Maximum Flight Segment Time Preference. + + + + + + Travel time (unit) Value. + Example: 45, 45 (Minutes) + + + + + + + + Travel time unit of measure. Example: Minutes, Hours, Days + + + + + + + + + + + + + + + + + + + A data type for Shopping Request Business Object: GROUP FARE Preferences. + + + + + Group Fare Preference detail. + + + + + + Fare basis detail for fare selection at flight and O/D levels. + + + + + + + + + + + + + + Passenger Type Code. Example: ADT + +Encoding Scheme: IATA (three character) Passenger Type Code (PTC) + + + + + + + + + + + Contains Shopping Preference choices, ie allowing to specify Airline, Alliance, Flight, Transfer and other shopping preferences. + + + + + + + + + + Contains information to identify how reservation was re-priced to obtain best published fare (Eg. best fare in same cabin, best fare in all cabins, other parameters to select best fare). + + + + + + + + + + + Contains information to identify how reservation was re-priced to obtain best published fare (Eg. best fare in same cabin, best fare in all cabins, other parameters to select best fare). + + + + + Total Journey TRAVEL TIME preference. + +Note: Based on sum of all flight times plus ground times in connecting airports. + + + + + Total Journey TRAVEL DISTANCE preference. + + + + + A data type for Travel Distance Preference. + + + + + Travel Distance (unit) Value. Example: 20 + + + + + + + + Travel distance application. +Examples: TotalJourneyDistance, MaximumTravelDistance + + + + + Distance unit of measure. Example: Kilometers, Miles, Other + + + + + + + + + A data type for Travel Time Preference. + + + + + Travel Distance (unit) Value. Example: 20 + + + + + + + + Travel time application. +Examples: TotalJourneyTime, MaximumTravelTime + + + + + + + Travel time unit of measure. Example: Minutes, Hours, days + + + + + + + TRANSFER/ CONNECTION POINT Preferences. + + + + + Maximum travel time preference for this flight segment. Example: 3 Hours + + + + + Service Pricing Only Preference. + + + + + + When true, Service Pricing Only is requested. + + + + + + + + A data type for Airline Transfer/ Connection Preferences. + + + + + Connection(s). + + + + + + Airport Code(s) optional preference level. + + + + + + Airport Code. Example: TPA + +Encoding Scheme: IATA/ A4A Aiport or City Code + + + + + + + + + + + + + + + Maximum number of connections. Example: 2 + + + + + Maximum connection time preference. Example: PT360M + + + + + Minimum connection time preference. Example: PT90M + + + + + Flight connection preference - online/ interline +Example: 0 (Online) + +Encoding Scheme: IATA PADIS Code List for data element 9885 - Online/ Interline Indicator + + + + + + + + + + + + + + + + Contains indicator of when Connection Pricing should be applied. When true, Connection Pricing should be applied. + + + + + When true, apply selected CONNECTION PRICING. + + + + + + + + + + Standard way to indicate successful processing of an IATA message. Returning an empty element of this type indicates success. + + + + + A collection of warning information. + + + + + Used in conjunction with the Success element to define a business error. + + + + + + + Standard way to indicate successful processing of an IATA message, but one in which warnings are generated + + + + + + The Warning element MUST contain the Type attribute that uses a recommended set of values to indicate the warning type. The validating XSD can expect to accept values that it has NOT been explicitly coded for and process them by using Type ="Unknown". + + + + + + + + + + Used to specify tax information for a coupon. + + + + + The ticket/document number to which the tax coupon data applies. + + + + + + The applicable coupon number. + + + + + + The tax information for a coupon. + + + + + The sold cabin of passenger travel for the coupon. + + + + + The standard code of the equipment used for the coupon flight. + + + + + + + The tax/fee charge for this coupon. + + + + + + + The airport code identifying the airort to which the coupon tax applies. + + + + + The tax amount aplicable to the coupon as published in the IATA TTBS or other applicable filing mechanism. + + + + + The ISO currency code representing the currency code in which the coupon tax applicable amount was published or filed in. Use ISO 4217, three alpha code. + + + + + The tax amaount applicable to a coupon expressed in the currency of payment. + + + + + The origin airport code identifyng multiple segment taxes. + + + + + The destination airport code identifying multiple segment taxes. + + + + + + + + + The airport or city code identifying an unticketed point which occurs between the coupon origin and destination. Unticketed point refers to a physical location at which the passenger makes a (potentially taxable) arrival and departure which does not appear in the good for Passage Area of the ticket. Used for the application of coupon level taxes. + + + + + + The airport or city code identifying an unticketed point which occurs between the coupon origin and destination. + + + + + The date and time of arrival in GMT at the unticketed point. + + + + + The date and time of depature in GMT from the unticketed point. + + + + + The standard code of the quipment used for the coupon flight departing from the unticketed point. + + + + + + + + The coupon number. + + + + + + + + The ticket/document number for this transaction. + + + + + The date of issue of the document. + + + + + + + + The date of birth of the passenger. + + + + + The airport/city code which has been assumed to be the journey turnaround point in the construction of the itinerary by the pricing system. + + + + + + Used for strings, length 1 to 8. + + + + + + + + + Used for strings, length 1 to 16. + + + + + + + + + Used for strings, length 1 to 5. + + + + + + + + + Use for numeric values, from 1 to 4 inclusive. + + + + + + + + + + The reissued flown flight coupon information. + + + + + Departure, date, time, arrival, RPH, flight number information. + + + + + + + + An intermediate airport/city code stop. + + + + + Airport city code. + + + + + + + + + + + When true, a stopover is permitted. + + + + + Used to indiccate when a transaction occurred due to a diversion en route. Refer to IATA PADIS Code List for data element 1245. + + + + + + + + + + Coupon number. + + + + + The number representing the order in which this coupon was used or is to be used. + + + + + The applicable fare basis code. + + + + + Document number comprised of the airline code, form code, and serial number. + + + + + The date the ticket was issued. + + + + + A validating carrier assigned code allowing a fare rule modification or override applied to a flown coupon from the ticket being reissued. + + + + + The applicable code as provided for in ATA SIPP Reso 110.16 or IATA Reso 728, for each flown coupon from the ticket being reissued. + + + + + + Used for Alpha-Numeric Strings, length 1 to 19 + + + + + + + + + The IATA_PayloadStdAttributes defines the standard attributes that appear on the root element for all IATA payloads. + + + + A reference for additional message identification, assigned by the requesting host system. When a request message includes an echo token the corresponding response message MUST include an echo token with an identical value. + + + + + Indicates the creation date and time of the message in UTC using the following format specified by ISO 8601; YYYY-MM-DDThh:mm:ssZ with time values using the 24 hour clock (e.g. 20 November 2003, 1:59:38 pm UTC becomes 2003-11-20T13:59:38Z). + + + + + Used to indicate whether the request is for the Test or Production system. + + + + + + + + + + + For all IATA versioned messages, the version of the message is indicated by a decimal value. + + + + + A unique identifier to relate all messages within a transaction (e.g. this would be sent in all request and response messages that are part of an on-going transaction). + + + + + Used to identify the sequence number of the transaction as assigned by the sending system; allows for an application to process messages in a certain order or to request a resynchronization of messages in the event that a system has been off-line and needs to retrieve messages that were missed. + + + + + This indicates where this message falls within a sequence of messages. + + + + + + This is the first message within a transaction. + + + + + This is the last message within a transaction. + + + + + This indicates that all messages within the current transaction must be ignored. + + + + + This is any message that is not the first or last message within a transaction. + + + + + Specifies that this is a followup request asking for more of what was requested in the previous request. + + + + + This request message is a subsequent request based on the previous message sent in this transaction. + + + + + + + + + + + When true, indicates the message is being re-sent after a failure. It is recommended that this attribute is used (i.e., set to true) only when a message is retransmitted. + + + + + Allow end-to-end correlation of log messages with the corresponding Web service message throughout the processing of the Web service message. + + + + + When true, indicates that the client can accept asynchronous processing. + + + + + + Used for strings, length 1 to 128. + + + + + + + + + Identifes the primary language preference for the message. + + + + Identifes the primary language preference for the message. The human language is identified by ISO 639 codes. + + + + + + Identifies the alternate language for a customer or message. The human language is identified by ISO 639 codes. + + + + Identifies the alternate language for a customer or message. The human language is identified by ISO 639 codes. + + + + + + + Geographic Specification information + + + + + Indicates whether a system may or may not send NDC requests based on geographic specifications. Users may enter a location here which is further defined by the @Type. Valid area values include 1 = Western Hemisphere 2 = Europe, Africa, and the Near East 3 = Far East, Australia, and Pacific Valid sub areas are Standard ISO/IATA sub area code Valid airport and city codes are a three letter location identifier assigned according to the IATA Resolution 763. Refer to IATA Airline Coding Directory . Example: TPA + + + + + + Coordinates (Latitude, Longitude, as defined in the Data Dictionary) + + + + + + + + Radius (in miles) to use in conjunction with coordinates above + + + + + + + Unit of measure to specify Kilometers and miles. + + + + + + + + + + + + + + + + Non Geographic Specification information + + + + + Indicates whether a system may or may not send NDC requests based on whether the request is coming from a travel agency. + + + + + + Indicates whether a system may or may not send NDC requests based on whether the request is coming from a specific agency, department or CRT address. + + + + + + + Further defines the type of PointOfSaleCode Values include the following: T = Pseudo Code/Travel Agency Code I = IATA Travel Agency No. H = Home IATA Agency No. U = Home Travel Agency Code X = Department/Identifier V = CRS/CXR Department Code L = LNIATA Number (CRT Address) A = Airline Specific Codes Blank = No application + + + + + + + + + + + + + + + + + + + + + + + + Offer Geographic Specification information + + + + + + 1 = From LOC 1 to LOC 2 2 = To LOC 1 from LOC 2 3 = Both + + + + + + + + + + + + Identifies the Offer Origin Point. + + + + + Identifies the Offer Destination Point. + + + + + + + Specifies that all travel on the itinerary must be wholly within the specified location. + + + + + + + + A data type for Unique Airline Designator. + + + + + + + + + + + + + + + + + + Further defines GeoSpecCode as Airport, City, State, Country, Sub-Area, Area A = Area S = State Z = Sub Area C = City P = Airport N = Country + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Used for strings, length 1 to 255. + + + + + + + + + + Baggage Determining Carrier as defined in resolution 722 (f), and who’s baggage rules apply. + + + + + + Airline Name. Example: British Airways + + + + + US Department of Transportation (DOT) Reservation or Disclosure baggage rule. +Examples: Y, Disclosure AND US DOT Reservation + + + + + In concert with BaggageDeterminingCarrier data field, specifies the reason for the carrier code in the AirlineID element. + +Encoding Scheme: IATA PADIS Code List for data element RES. + + + + + + + Enumeration of why this carrier is the BDC. +1. Regulatory [Application of regulation or Resolution] +2. Deferral [Example: Deferral by ORA] +3. Bilateral [Bilateral agreement] + + + + + + + + + + + + + + + + Applicable Surcharge(s). + + + + + + Surcharge detail. + + + + + + + + Individual fee/ surcharge information would appear on the accountable document. + + + + + + + + + + + + Unique image ID. Examples: IMG713, SFO_LOUNGE + + + + + + + Airline Designator of airline that owns/ assigned this ID. Example: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Codes + + + + + "The “Format” is the “CREATIVE UNIT NAME”, Example: (Billboard, Filmstrip, Portrait, Pushdown, Medium Rectangle, Rectangle, Half Page ,…) IATA codeset MDF. Please refer to http://www.iab.com/wp-content/uploads/2015/11/IAB_Display_Mobile_Creative_Guidelines_HTML5_2015.pdf" + + + + + + + + + + + Entity that owns ticket identification. It could be an airline, CRS or GDS code, + +Note: If this is an airline, the IATA/ A4A (two or three character) Airline Designator Code should be used. + + + + + Contains security details: viewing (display)/booking/sales location(s). + + + + + Date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25 + + + + + Time in ISO 8601 format (hh:mm). Example: 14:00 + + + + + Identifies location where ticket was issued. Normally a 3-letter airport/city code. + + + + + + + + + + Identifies country where ticket was issued by a two letter country code. +Example: CA + + + + + + + + + + Ticket or EMD Number + + + + + + + + + Recursive element to allow nested selections of services from a bundle of services. + + + + + Id to defined a selected ServiceDefinition from the selected bundle. + + + + + Reference to the Service Definition selected by the passenger + + + + + + + + + + Total price reflecting all services for all passengers across all segments referenced within this Offer Item. + + + + + + Total price amount. + +Notes: +1. This is typically the lowest price for this alternate lead shopping date. +2. If expressed in currency, this price should include base price, taxes and fees/ surcharges. + + + + + + + + + + + + + + Total Base Fare Amount. Example: 200000 + +Note: This includes surcharges (if applicable). + + + + + + Discount Information + + + + + Applicable Surcharge(s). + + + + + + Surcharge detail. + + + + + + + + Ticket Tax/fee/charge details to indicate taxes that apply to country of commencement of travel and routing. + + + + + + + AWARD (Redemption Unit-based) Pricing information. + + + + + PARTIAL CURRENCY and AWARD Pricing Combination information. + + + + + + Individual fee/ surcharge information would appear on the accountable document. + + + + + + + + + + + + + The individual instance of a specific flight, service or service bundle (as found in DataLists) as it has been offered, and eventually ordered and consumed by, a specific Passenger in the context of an Offer. + + + + + + References the ID of the Service Definition in DataLists. + + + + + + + + + + + ID for the Service unique across the entire XML document. + + + + + + + + Unique identifier for this OfferItem instance. Must be unique within XML message. Exceeding 64 characters or use of dashes is not recommended. + + + + + If set to 'true', indicates mandatory Offer Items which cannot be removed from the Offer. Mandatory Offer Items transition into Order Items. If not present or 'false', the Offer item is optional. The aggregate price at the Offer level initially reflects the sum of the prices for all Mandatory Offer Items within it. + + + + + POA to ORA only: to indicate that the offer is non-modifiable. This indicates to ORA that its offer is non-modifiable (eg. Regulatory or brand protection reasons). If indicator is set to true, nodifications to the POA’s offer ARE NOT allowed. + + + + + + + ORDER INPUT SHOPPING RESPONSE object definition. + + + + + Offer selected by the Passenger for requesting an Order to be created. Multiple Offers can be requested at the same time, each of which could originate from different shopping responses (each with their own ResponseIDs). + +Each Offer selected could reference (via the OfferID) either standard Offers from an AirShoppingRS message (potentially with Flight-related services) or A-La-Carte Offers (containing optional ancillary services). These standard Offers and “a-la-carte” Offers would need to be consistent with the applicability rules defined by their relations (passengers or segments eligible for the enclosed OfferItems) and would be combined to produce a single Order, returned by the OrderViewRS message. + + + + + + The total price for all selected Offer Items (and respective quantities) for all passengers and segments associated with the respective Offer(s), as calculated by the seller system. Without adding any optional Offer Items, the value of this TotalOfferPrice should be that of the TotalPrice of the Offer(s) being referenced. + + + + + OfferItem selected by the Passenger for inclusion in the requested Order. Repeat occurrence of OfferItem (once per passenger) if different passengers want to select different service options, different quantities of a-la-carte items or different seat locations. + +As a minimum, all mandatory OfferItems from a desired Offer should be explicitly defined within these selections and should repeat the same Passenger and Flight Segment associations defined in the originating OfferItems. Optional OfferItems may then be appended as further items selected by the Passenger. + +OfferItems from the originating Offers may take on two different forms, which in turn drives how the ALaCarteSelection element is to be used - If the OfferItem referenced comes originally from an a-la-carte Offer, then the use of the ALaCarteSelection element should be used to defined the Quantity of said OfferItem. On the other hand, if the OfferItem comes from a standard type of Offer in the previous shopping response, the ALaCarteSelection element should not be used, as the quantity is explicitly driven by what is defined in that OfferItem’s associations (to passengers and/or flight segments). + + + + + + Reference to passenger(s) for which this OfferItem and selected Services (in case of Service Bundles) applies. + + + + + Use to select the quantity of Offer Items from the A La Carte Offer Items. + + + + + + Quantity to allow the ordering of more than one instances of the related a la carte OfferItem. + + + + + Reference to segment proposed in original Offer Item's elibigility rules. + + + + + + + + For service bundle selection - only to be used for bundles with optional choices (e.g. pick 2 out of 4) + + + + + + + Reference to the Service (within the OfferItem) from which the bundling begins + + + + + + + + + Selection of specific seat location, as provided in seat availability messages. + +When used, only a single Passenger must be referenced for a single Segment + + + + + + Seat row number. Example: 2 + + + + + Seat column to identify a particular seat position on an aircraft + + + + + + + + + Reference to the OfferItemID of the selected OfferItem (contained in either a standard Offer or an a-la-carte Offer) returned in a previous shopping response. + + + + + + + + Reference to the OfferID of the selected Offer (either a standard Offer or an a-la-carte Offer) returned in a previous shopping response. + + + + + Designator of Airline that owns/ assigned these IDs. Examples: BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline Designator Code + + + + + Reference to unique shopping session response ID, as provided in the airline's previous shopping response. + + + + + + + Used for selling by value (long sells) rather than selling by reference. + + + + + + + + OPTIONAL SERVICE CORE definition. + + + + + Service name. Example: Lounge Pass + + + + + + + + + + Choice to determine if the information of this ServiceDefinition needs to be extended with specific Bag or Seat characteristics, or whether the ServiceDefinition is used as a bundle of further ServiceDefinitions. + + + + + Reference to Seats within SeatList to further define the characteristics of the seat product. In a shopping scenario, reference one instance of a seat, for further description. May be used in SeatAvailability messages to reference multiple seats to reflect availability of physical seats of this product type. + + + + + + + + Reference to further Service Definitions which form part of this Service Bundle + + + + + + + Set to 'true' when this Service Definition is optional (i.e. can be selected or not by the passenger) + + + + + + + + + + Maximum quantity of bundle services that can be selected by each passenger referenced in the Offer + + + + + + + + Service Codes and Reason for Issuance. + + + + + + Two character generic code to identify ticket level charges, fees and taxes. + + + + + + + + + + SERVICE Description. + +Note: Supports plain text, multimedia and code and link references. + + + + + Interline Settlement information between airlines, including method of settlement, interline settlement value and currency. + + + + + + Service settlement method. +Examples: +AD (Internal Airline Document) +DS (Direct Settlement) +EA (EMD Associated or Internal Airline Document) +ES (EMD Standalone ) +FI (Fare Integrated) +MA (Flight Associated, Settled via MCO) +MS (Standalone, Settled via MCO) + +Encoding Scheme: IATA PADIS Codeset SST (Service Settlement Type) + + + + + Settlement (Price) Value. Example: 300 (USD) + +Note: This represents a Settlement value that is only used between the POA and ORA. + + + + + + + + Optional service booking instructions to include SSR, OSI and Upgrade Method. + + + + + + Passenger assistance SSR code value. +Examples: +EXST (EXTRA SEAT REQUIRED) +INFT (INFANT ACCOMPANYING ADULT PASSENGER) +PETC (PASSENGER TRAVELING WITH PET IN CABIN) +UMNR (UNACCOMPANIED MINOR) + +For maximum interoperability, it is recommended that IATA (four character) Special Service Request (SSR) Code values be used. Select an enumerated value from the list of enter a four character SSR code string. + +=notes= +1. Although optional in the schema, some SSR codes may require associated description elements. + + + + + Other service information (OSI) text. +Example: PAX VIP MEMBER OF PARLIAMENT + + + + + PNR booking method. +Example: AE (BY SSR - SPECIAL SERVICE REQUEST) + +For maximum interoperability, refer to IATA PADIS Code List for data element 9750. Select a code value or enter a value that is bilaterally agreed upon between trading partners. + + + + + Upgrade method. +Example: AE (BY SSR - SPECIAL SERVICE REQUEST) + +For maximum interoperability, refer to IATA PADIS Code List for data element 9750. Select a code value or enter a value that is bilaterally agreed upon between trading partners. + + + + + + + New class of service. +Example: B + + + + + + + + + Data center instructions. + + + + + Aircraft equipment information. + + + + + + + + Validating Carrier Airline Designator. +A two-character alpha-numeric code assigned according to the IATA Resolution 762 or a three-letter airline designator assigned by ICAO. Refer to IATA Airline Coding Directory . Example: BA + + + + + Detailed Service information, including Service Bundle, Service Combinations, Service Coupon, Service Fulfillment and Service Quantity Rules. + + + + + + + + + + + + + + "A unique Service ID that has been returned in the Shopping results, and identifies an airline service item (ie a product or a service) that can be separately delivered and uniquely described by an airline. + +Example: SRVC-2B88-4C33-9787-9461114BC9BE" + + + + + Airline designator or CRS code of the owner/ assigner of the Offer ID, typically used for offer ordering purposes. Example: UA, BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline or CRS Designator Code + + + + + + + + + Refers to the Passengers, Price class or Segments for which this offer item is eligible. + + + + + + Reference to the passengers who are elibigle for this Offer Item + + + + + + + If 'true', this service applies to any passenger + + + + + + + + + Reference to the flight segments on which this Offer Item can be provided. + + + + + + + If 'true', this service applies to any segment + + + + + + + + + + + + + Flat price for an individual unit of the referenced Service. + + + + + + Total price amount. + +Notes: +1. This is typically the lowest price for this alternate lead shopping date. +2. If expressed in currency, this price should include base price, taxes and fees/ surcharges. + + + + + + + + + + + + + + Total Base Fare Amount. Example: 200000 + +Note: This includes surcharges (if applicable). + + + + + + Discount Information + + + + + Applicable Surcharge(s). + + + + + + Surcharge detail. + + + + + + + + Ticket Tax/fee/charge details to indicate taxes that apply to country of commencement of travel and routing. + + + + + + + AWARD (Redemption Unit-based) Pricing information. + + + + + PARTIAL CURRENCY and AWARD Pricing Combination information. + + + + + + Individual fee/ surcharge information would appear on the accountable document. + + + + + + + + + + + + + One or more instances of a service definition (as found in DataLists) as it has been offered, and eventually ordered and consumed by a specific Passenger in the context of an Offer. + + + + + + Create dependencies with parent services to which this particular Service is linked. Can reference ServiceItems across different OfferItems within the same Offer. + + + + + + + Unique identifier for this Service instance. + + + + + + + + Unique identifier for this OfferItem instance. Must be unique within XML message. Exceeding 64 characters or use of dashes is not recommended. + + + + + + + + + Total price reflecting all services for all passengers across all segments referenced within this Offer Item. + + + + + + Total price amount. + +Notes: +1. This is typically the lowest price for this alternate lead shopping date. +2. If expressed in currency, this price should include base price, taxes and fees/ surcharges. + + + + + + + + + + + + + + Total Base Fare Amount. Example: 200000 + +Note: This includes surcharges (if applicable). + + + + + + Discount Information + + + + + Applicable Surcharge(s). + + + + + + Surcharge detail. + + + + + + + + Ticket Tax/fee/charge details to indicate taxes that apply to country of commencement of travel and routing. + + + + + + + AWARD (Redemption Unit-based) Pricing information. + + + + + PARTIAL CURRENCY and AWARD Pricing Combination information. + + + + + + Individual fee/ surcharge information would appear on the accountable document. + + + + + + + + + + + + + The individual instance of a specific flight, service or service bundle (as found in DataLists) as it has been offered, and eventually ordered and consumed by, a specific Passenger in the context of an Offer. + + + + + + Reference to the PassengerID of one or more Passengers in DataLists. The Passenger is the recipient entitled to receive/consume the Service(s) offered by the Airline, whether the Service(s) are flight-related or not. + + + + + Create dependencies with parent services to which this particular Service is linked. Can reference Services across different OfferItems within the same Offer. + + + + + + Reference to one or more flights in the Datalists that are being sold as part of this OfferItem/Service. + + + + + References the ID of the Service Definition in DataLists. + + + + + + + Reference to one or more segments in the Datalists to restrict the eligibility of the associated ServiceDefinition. + + + + + + + + + The Seat location selected by the Passenger (via SeatAvailability) or assigned to the Passenger by the Airline for a given Segment. + + + + + + Selection of specific seat location, as provided in seat availability messages. + +When used, only a single Passenger must be referenced for a single Segment + + + + + + Seat row number. Example: 2 + + + + + Seat column to identify a particular seat position on an aircraft + + + + + + + + Reference to the Segment on which this Passenger's Seat has been assigned. + + + + + Reference to the ServiceDefinition relating to the Seat assigned to the Passenger. + + + + + + + + + + ID for the Service unique across the entire XML document. + + + + + + + Fare Detail, including Fare Component and Fare Rules. + + + + + + Unique identifier for this OfferItem instance. Must be unique within XML message. Exceeding 64 characters or use of dashes is not recommended. + + + + + If set to 'true', indicates mandatory Offer Items which cannot be removed from the Offer. Mandatory Offer Items transition into Order Items. If not present or 'false', the Offer item is optional. The aggregate price at the Offer level initially reflects the sum of the prices for all Mandatory Offer Items within it. + + + + + POA to ORA only: to indicate that the offer is non-modifiable. This indicates to ORA that its offer is non-modifiable (eg. Regulatory or brand protection reasons). If indicator is set to true, nodifications to the POA’s offer ARE NOT allowed. + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/edist_structures.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/edist_structures.xsd new file mode 100644 index 00000000..dd341073 --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/edist_structures.xsd @@ -0,0 +1,2257 @@ + + + + EDIST XML Specification Base Structures. Includes base types for EDIST XML data objects, utility xml objects and core simple type definitions. + + + + + + + Actor object instance id and association(s). + + + + Association between this object and metadata instance(s). + + + + + Object association(s) between this actor object and any object instance(s). + + + + + + A data type for NDC Actor Object Base Type. + + + + + + A data type definition for Globally Unique XML Instance or Other Class ID size constraint. + + + + + + + A base type definition for Core Entity Object. + + + + + Object Augmentation Point(s). + + + + + + Globally Unique Object instance/ class Key. + +Example: 2B75C565-5BB0- 4DCE-8DE6-67CB7B4F25A7 + + + + + Source Entity Code or ID. Examples: BA, WIDGETCO + + + + + Sequence ID. Example: 1 + + + + + + A base type definition for Data List Object. + + + + Unique List Token. + +Example: jZhJu7SORZeO MNpifElIkA + +Note: This token pertains to all specified List instances, e.g. the list collection. + + + + + Source Entity Code or ID. Examples: BA, WIDGETCO + + + + + Sequence ID. Example: 1 + + + + + + A base type definition for Metadata Object. + + + + + A data type definition for Airline Carrier or Entity Owner. + + + + + + A data type definition for Owner Entity size constraint. + + + + + + + + + A base type for an Object with Instance Associations. + + + + + When true, this fee is approximate. + + + + + When true, all fee amounts are refundable. + + + + + When true, price is exempt from all taxes. + + + + + When true, ALL associated inventory has been guaranteed for this and the guarantee information specified in the InventoryGuarantee node. + + + + + When true, one or more associated Offer Item(s) are subject to regulatory disclosure. + + + + + When true, the attachment can be displayed in a browser. + + + + + + Policy and other object association. + + + + + Object association(s) between this object and any other object or metadata instance(s). + + + + + + A data type definition for Reference Association Token type and size constraint. + + + + + + + + + + Augmentation Point. + + + + + A data type definition for Augmentation Point. + + + + + Implementer-Augmented Structure. + + + + + + Globally Unique Object instance/ class Key. + +Example: 2B75C565-5BB0- 4DCE-8DE6-67CB7B4F25A7 + + + + + Source Entity Code or ID. Examples: BA, WIDGETCO + + + + + Sequence ID. Example: 1 + + + + + + A data type definition for Augmentation Point Association. + + + + + Augmentation Point Association detail. + + + + + Reference to globally unique AUGMENTATION POINT instance/ class Key. + +Example: 2B75C565-5BB0- 4DCE-8DE6-67CB7B4F25A7 + + + + + Owner Airline (or other entity) Code. Examples: BA, WIDGETCO + + + + + Sequence ID. Example: 1 + + + + + + + + Owner Airline (or other entity) Code. Examples: BA, WIDGETCO + + + + + + A data type definition for Augmentation Point List. + + + + + + + Augmentation Point List detail. + + + + + + Associated Augmentation Point(s). + + + + + Reference to globally unique AUGMENTATION POINT instance/ class Key. + +Example: 2B75C565-5BB0- 4DCE-8DE6-67CB7B4F25A7 + + + + + Source Entity Code or ID. Examples: BA, WIDGETCO + + + + + Sequence ID. Example: 1 + + + + + + + Augmentation Point List Named Association(s). + +Note: This capability supports implementer-specified, or "Named", reference associations to other (target) instantiated objects with @Key, @GroupKey, @GroupTokenKey, @ListKey and @ListTokenKey attributes. + + + + + + Globally Unique Group instance/ class Key. + +Example: {CA2016A0-0AE1-4E65-8EA6-0A16AE906596} + + + + + List Name. Example: MyList + + + + + Source Entity Code or ID. Examples: BA, WIDGETCO + + + + + Sequence ID. Example: 1 + + + + + + + + + + + A data type definition for Augmentation Point Definition and List. + + + + + Augmentation Point Definition. + + + + + Augmentation Point Reference/ Association Lists. + + + + + + + A data type definition for Named Association Type. + +Named Association(s). + +Note: This capability supports implementer-specified, or "Named" reference associations to other (target) instantiated objects with @Key, @GroupKey and/ or @ListKey attributes. + + + + + Association detail, including: + +- Target object name +- Group instance/ class key reference +- Object instance/ class key reference +- From object name +- Sequence id + + + + + + Associated Target Group Key and/ or Token. + + + + + Reference to globally unique TARGET GROUP instance/ class Key. + +Example: A3E9CF38-B140-4E03-A550-493A817A2BC9 + + + + + Reference to globally unique TARGET GROUP COLLECTION instance/ class Key. + +Example: {AEF93466-0464-46C6-89B5-487DF5007D3E} + + + + + Sequence ID. Example: 1 + + + + + + + Associated Target List Key and/ or Token. + + + + + Reference to globally unique TARGET LIST instance/ class Key. + +Example: {E7A28E6D-045C-4BE1-B85E-304262911773} + + + + + Reference to globally unique TARGET LIST COLLECTION instance/ class Key. + +Example: E20C732E-17AE-40E8-B3DB-FCC04585DD4C + + + + + Sequence ID. Example: 1 + + + + + + + Object Unique Key ID. + + + + + A reference to a Unique (string-based) Object ID. Example: OBJ001 + + + + + Sequence ID. Example: 1 + + + + + + + + Target Object Source Name. + +Example: PolicyList + + + + + A reference to the @Target OBJECT instance/ class Key. + +Example: 23D20750-1FFE-4EA7-A5CD-A4B9733A491B + + + + + From Object Name. + +Example: FlightSegmentList + + + + + Sequence ID. Example: 1 + + + + + + + + + + Policy and object association(s). + + + + Object association(s) between this object and any object instance(s). + + + + + Globally unique id for this Data List instance. + + + + + + + Metadata object instance id and association(s). + + + + Association(s) between this metadata object and any metadata instance(s). + + + + + Object association(s) between this metadata object and any object instance(s). + + + + + A globally unique identifier for this Metadata instance. + + + + + + Base type for NDC Metadata Representation. + +Notes: Within NDC, metadata is defined as data about data. This may include information such as the security of a piece of data or the source of the data. These pieces of metadata may be composed into a metadata type. The types of data to which metadata may be applied may be constrained. + + + + + Augmentation Point for this Metadata Structure. + + + + + + Object association(s) between this object and any object instance(s). + + + + + A globally unique identifier for this Metadata instance. + + + + + + + A base type for a Keyed Object. + + + + + When true, Corporate Fare Information was used for Pricing. + + + + + + Policy, unique instance id and other object associations. + + + + Object association(s) between this object and any other object or metadata instance(s). + + + + + Object globally unique Instance ID. Example: obj1 + + + + + + Policy, unique instance id, object metadata and other object associations. + + + + Object association(s) between this object and any other object or metadata instance(s). + + + + + Object globally unique Instance ID. Example: obj1 + + + + + + Policy, object metadata and other object associations. + + + + Object association(s) between this object and any other object or metadata instance(s). + + + + + Object Metadata Association(s). Example: meta1 meta3 + + + + + + + + A data type definition for Commonly Used Date Representation Formats: Short Date, Date and Time, Timestamp + + + + Date and time. Example: 2017-01-03T13:20:00 + + + + + Short date. Example: 2017-01-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + Timestamp. Example: 2017-01-13T13:59:38Z + + + + + Time. Example: 14:00 + +[Encoding Scheme] ISO 8601 Military/ 24 Hour (HH:MM) + + + + + + A data type definition for Commonly Used Date Representation Formats: Short Date, Date and Time, Timestamp + + + + Date and time. Example: 2017-01-03T13:20:00 + + + + + Short date. Example: 2017-01-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + Timestamp. Example: 2017-01-13T13:59:38Z + + + + + Time. Example: 14:00 + +[Encoding Scheme] ISO 8601 Military/ 24 Hour (HH:MM) + + + + + + + Policy and object association(s). + + + + + Object association(s) between this object and any object instance(s). + + + + + + + Globally unique id for this Transaction Processing object instance. + + + + + + + A base type for a Transaction Processing Object. + + + + Unique instance ID and object association(s). + + + + + When true, Payer Authentication Response information is specified in the PayerAuth node. + + + + + When true, the maximum payment authentication attemps have been exceeded. + + + + + When true, the Payment information has not been processed. + + + + + When true, the payment transaction should be resent. + + + + + When true, Payer Authentication Request information is specified in the PayerAuth node. + + + + + + + Preference level and context. + + + + Preference Level. Example: Preferred, Required, Exclude, Other + + + + + Preference Level Context. Example: MyContext + + + + + + + A data type definition for Named NDC Domain list constraint. + +Examples: Shopping, OrderManagement, PaymentTicketing, AirlineProfile, Utility + +Note: Supports pre-defined enumerated list and/ or bilaterally-agreed upon values. + + + + + + A data type definition for Encoding Scheme Source Provider Type list constraint. + + + + + + + + + + A data type definition for Encoding Scheme Source Provider Type. + +Examples: Airline, Filed, ThirdParty + +Note: Supports pre-defined enumerated list and/ or bilaterally-agreed upon values. + + + + + + A data type definition for Globally Unique XML Instance or Other Class Reference Association size constraint. + + + + + + A data type for an xsd:ID unique instance identifier. + + + + + + A data type definition for List Application size constraint. + + + + + + + + + A data type for an InstanceClassRefSimpleType Association. + + + + + + A data type definition for Service, Offer, Order and Order Item ID size constraint. + + + + + + + + + A data type for Unique ID with Context. + + + + + + + Airline designator or CRS code of the owner/ assigner of the Offer ID, typically used for offer ordering purposes. Example: UA, BA + +Encoding Scheme: IATA/ A4A (two or three character) Airline or CRS Designator Code + + + + + + + + + + A data type definition for Commonly Used Effective (start) and Expiration (end) Period. + + + + + Effective (start) and expiration (end) Dates. + + + + + Effective (start) and expiration (end) Date and Time. + + + + + Effective (start) and expiration (end) Timestamp. + + + + + Effective (start) Timestamp. Example: 2017-01-13T13:59:38Z + + + + + Expiration (end) Timestamp. Example: 2017-11-13T13:00:00Z + + + + + + + + + A data type definition for Effective/ Expiration Date And Time Period Representation. + + + + Effective (start) Date/ Time. Example: 2017-01-13T06:00:00 + + + + + Expiration (end) Date/ Time. Example: 2017-03-13T23:00:00 + + + + + + A data type definition for Effective/ Expiration Short Date Period Representation. + + + + Effective (start) Date. Example: 2017-01-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + Expiration (end) Date. Example: 2017-01-14 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + + A month number. Example: 01 (January) + + + + + + Effective (start) and expiration (end) Dates. + + + + + Effective (start) and expiration (end) Date and Time. + + + + + Effective (start) and expiration (end) Day of Week. + + + + + A data type for Day of Week Date Period Representation. + + + + + + Day Name. Example: Monday + + + + + + + + A data type for Effective/ Expiration Short Date Period Representation. + + + + + Effective (start) date. Example: 2017-01-13 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + Expiration (end) date. Example: 2017-01-14 + +Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) + + + + + + + A data type for Effective/ Expiration Date And Time Period Representation. + + + + + Effective (start) date/ time. Example: 2017-01-13T06:00:00 + + + + + Expiration (end) date/ time. Example: 2017-03-13T23:00:00 + + + + + + + A data type for Effective/ Expiration Day of Week Date Period Representation. + + + + + Effective (start) day of the week number. Example: 01 + + + + + Expiration (end) day of the week number. Example: 04 + + + + + + + Effective (start) and expiration (end) Months. + + + + + A data type for Month Number Date Period Representation. + + + + + + Month Name. Example: January + + + + + + + + A data type for Effective/ Expiration Month Date Period Representation. + + + + + Effective (start) month number. Example: 01 + + + + + Expiration (end) month number. Example: 04 + + + + + + + Effective (start) and expiration (end) Calendar Quarter. + + + + + A data type for Effective/ Expiration Calendar Quarter Period Representation. + + + + + Effective (start) quarter. +Example: 1Q (JAN-MAR) + + + + + + + + + + + + + Expiration (end) quarter. +Example: 3Q (JUL-SEP) + + + + + + + + + + + + + + + Effective (start) and expiration (end) Times. + + + + + A data type for Effective/ Expiration Time Period Representation. + + + + + Effective (start) time. Example: 09:00 + +Encoding Scheme: ISO 8601 Military/ 24 Hour Format (HH:MM) + + + + + Expiration time. Example: 18:00 + +Encoding Scheme: ISO 8601 Military/ 24 Hour Format (HH:MM) + + + + + + + A data type for a Timestamp Representation. Example: 2015-01-13T13:59:38Z + + + + + + + + Effective (start) and expiration (end) Full Year. + + + + + Effective (start) and expiration (end) Full Year and Month. + + + + + A data type for Effective/ Expiration Year Date Period Representation. + + + + + Effective (start) year. +Example: 2014 + + + + + Expiration (end) year. +Example: 2016 + + + + + + + A data type for Effective/ Expiration Year And Month Date Period Representation. + + + + + Effective (start) year and month. Example: 2017-01 + + + + + Expiration (end) year and month. Example: 2017-12 + + + + + + + + + + A data type for 3DS Program ACS Customer Authentication contextual list. Examples: Y- Customer authenticated N- Customer not authenticated A- An authentication attempt occurred but could not be completed U- Unable to perform authentication + + + + + + + A- An authentication attempt occurred but could not be completed + + + + + + N- Customer not authenticated + + + + + U- Unable to perform authentication + + + + + Y- Customer authenticated + + + + + + + + A data type for 3DS Program ACS Customer Authentication status. Examples: Y- Customer authenticated N- Customer not authenticated A- An authentication attempt occurred but could not be completed U- Unable to perform authentication + + + + + + + + A data type for 3DS Program Enrollment Status contextual list. Examples: CardNotEnrolled, CardEnrolled, CardMayBeEnrolled, Unknown + + + + + + + + + + + A data type for 3DS Program Enrollment Status. Examples: CardNotEnrolled, CardEnrolled, CardMayBeEnrolled, Unknown + + + + + + + + A data type for 3DS Transaction Type contextual list. Examples: Authorize: Authorize amount (no funds transferred) Complete: Complete a previous authorization (funds are transferred) Purchase: Purchase (funds are transferred immediately) Refund: Refund (funds transferred immediately) Validate: Validation Transaction (a small authorized transaction amount to validate card details including expiry date and address) + + + + + + Amount is authorized. No funds are transferred. + + + + + + + Complete a previous authorization. Funds are transferred. + + + + + + Purchase. Funds are transferred immediately. + + + + + Refund. Funds transferred immediately. + + + + + + Validation Transaction. Effects a $1.00 Authorization to validate card details including expiry date, address. + + + + + + + + + A data type for 3DS Transaction Type. Examples: Purchase, Refund, Authorization, Complete, Validate + + + + + + + + A data type for 3DS Secure Authorization Client Type contextual list. Examples: InteractiveVoiceResponse (IVR) Internet MailOrTelephoneOrder (MOTO) Recurring Unattended + + + + + + IVR + + + + + + MOTO + + + + + + + + + + A data type for 3DS Secure Authorization Client Type. Examples: InteractiveVoiceResponse (IVR) Internet MailOrTelephoneOrder (MOTO) Recurring Unattended + + + + + + + + A data type for Advanced Purchase list constraint. + +Examples: EARLIEST, LATEST, Other + + + + + + + + + + A data type for Fare Application. + + + + + + + A data type for Application size constraint. + + + + + + + + + Aircraft row number. + + + + + + A data type for Aircraft Equipment Code encoding constraint: IATA/ A4A Aircraft Equipment Code + + + + + + + + + A data type for Airline Designator Code encoding constraint: IATA/ A4A (two or three character) Airline Designator Code + + + + + + + + + + A data type for an Airport or City Code constraint. + Encoding: For maximum interoperability, use IATA/ A4A (three character) airport or city codes. + Examples: JFK, NYC + + + + + + + + + A data type for Baggage Applicable To contextual list. + + + + + + + + + + A data type for Baggage Application. + + + + + + A data type for Baggage Dimension contextual list. + + + + + + + + + + A data type for Baggage Dimension Unit. + + + + + + A data type for Baggage Disclosure Rule Code contextual list. + + + + + Disclosure with NO US DOT Reservation + + + + + No Disclosure or US DOT Reservation + + + + + Disclosure AND US DOT Reservation + + + + + + + + A data type for Baggage Disclosure Rule. + + + + + + + A data type for Code Set Value size constraint. + Encoding: Alphanumeric +Min Length: 1 +Max Length: 6 + Examples: A, ABC, 1 + + + + + + + + + A data type for an Implementer-Specified Code Value constraint. + Encoding: Alphanumeric +Min Length: 1 +Max Length: 6 + Examples: A, ABC, 1 + + + + + + + + + + A data type for Currency Code Application constrained list. + +Examples: Actual, Display, Requested, Conversion, Other + + + + + + + + + + A data type for Currency Code Application. + +Examples: Actual, Display, Requested, Conversion, Other + + + + + + + A data type for Currency Code Application constrained list. + +Examples: Actual, Display, Requested, Conversion, Other + + + + + + + + + + + + A data type for Currency Code Application. + +Examples: Actual, Display, Requested, Conversion, Other + + + + + + A data type for Email Application list constraints. +Example: Account, Business, Personal, SMS, Other + + + + + + + + + + + + A data type for Email Application. + + + + + + + A data type for Context Value size constraint. + Encoding: Alphanumeric +Min Length: 1 +Max Length: 35 + Examples: Provider, tablename.field + + + + + + + + + + A data type for Country Code encoding constraint: ISO 3166-1 (two character) Country Code + + + + + + + + + A data type for Coupon Media Type contextual list. + + + + + + + + + + A data type for Baggage Application. + + + + + + A data type for a Coupon Purpose. + + + + + + + + + + + + + + + + + + + + A data type for Fare Rule Modification or Override Type contextual list. + + + + + + + + + + A data type for Baggage Application. + + + + + + + Currency encoding for the Amount value. + + + + Currency code. Example: USD +Encoding Scheme: ISO 4217 (three alpha character) Currency Code + + + + + + Optional currency encoding for the Amount value. + + + + Currency code. Example: USD +Encoding Scheme: ISO 4217 (three alpha character) Currency Code + + + + + + A data type for Currency Code Application list constraint. + +Examples: Actual, Display, Requested, Conversion, Other + + + + + + + + + + + + A data type for Currency Code Application. + +Examples: Actual, Display, Requested, Conversion, Other + + + + + + A data type for Currency Code encoding constraint: ISO 4217 (three alpha character) Currency Code + + + + + + + + + A data type for Day of Week encoding constraint:String, 1 - 7 length + + + + + + + + + A data type for Day of Week encoding constraint:Positive Integer 1 - 7 + + + + + + + + A data type for Month Number encoding constraint: 01 through 12 + + + + + + + + A data type for Time encoding constraint: SO 8601 Military/ 24 Hour (HH:MM) +Example: 14:00 + + + + + + + + + + A data type for Description encoding constraint: Minimum Length of 1 + + + + + + + + A data type for a Short Description size constraint. + + + + + + + + + A data type for NDC Domain List. + + + + + + + + + + + + + A data type for Distance Unit of Measure contextual list. +Examples: Miles, Kilometers + + + + + + K = KILOMETERS + + + + + + M = MILES + + + + + + + + A data type for Currency Code Application. + +Examples: Actual, Display, Requested, Conversion, Other + + + + + + + A data type for an Image UOM constrained list. + + + + + + + + + + + + A data type for an Image UOM Description. + + + + + + + A data type for Language Code Application list constraint. + +Examples: Display, Requested, Spoken, Written, Other + + + + + + + + + + + + A data type for Language Code Application. + +Examples: Display, Requested, Spoken, Written, Other + + + + + + A data type for a Rendering Type constrained list. + + + + + + + + + + A data type for Language Code Application. + +Examples: Display, Requested, Spoken, Written, Other + + + + + + + A data type for Passenger Type Code (PTC) encoding constraint: IATA (three character) Passenger Type Codes + + + + + + + + + + A data type for a Credit Card Type constraint. + + + + + + + + + + + + A data type for a Credit Card Code constraint. + + + + + + + + + + + + A data type for a Credit Card Number constraint. + + + + + + + + A data type for a Payment Card Series Code constraint. + + + + + + + + A data type for a Payment Card Date constraint. + + + + + + + + + A data type for Payment Status contextual list. Examples: Canceled, Complete, Failed, MoreInformation, Partial + + + + + + + + + + + + + A data type for a Masked Payment Card Number constraint. + + + + + + + + + A data type for Offer Penalty Amount Application list constraint. + + + + + + + + + + A data type for Offer Penalty Amount Application. + + + + + + A data type for Offer Penalty Type list constraint. + + + + + + + + + + + + A data type for Offer Penalty Type. + + + + + + + A data type for Whole Percentage encoding constraint. + + + + + + + + + + A data type for Preference Type list constraint. + + + + + + + + + + A data type for Language Code Application. + +Examples: Display, Requested, Spoken, Written, Other + + + + + + + A data type for Proper Name size constraint. + + + + + + + + A data type for Carrier Name size constraint. + + + + + + + + A data type for Property Name size constraint. + + + + + + + + + A data type for Proximity Data Application list constraint. + + + + + + + + + + A data type for Proximity Data Application. + + + + + + + A data type for Pseudo City Code encoding constraint. Example: AAA2 + + + + + + + + + + A data type for a Redemption Unit List. + + + + + + + + + + A data type for Language Code Application. + +Examples: Display, Requested, Spoken, Written, Other + + + + + + + A data type for Rule Status contextual list. + + + + + + + + + A data type for Language Code Application. + +Examples: Display, Requested, Spoken, Written, Other + + + + + + + A data type for Special Service or Request Code constraint. + + + + + + A data type for Special Service Request Code encoding constraint: IATA +Examples: +EXST (EXTRA SEAT REQUIRED) +INFT (INFANT ACCOMPANYING ADULT PASSENGER) +PETC (PASSENGER TRAVELING WITH PET IN CABIN) +UMNR (UNACCOMPANIED MINOR) + + + + + + + + + A data type for IATA Company Number encoding constraint. Example: 98417900 + + + + + + + + A data type for ICAO Location Code encoding constraint. Example: K (CONTIGUOUS UNITED STATES) + + + + + + + + + + A data type for Ticket Designator Application list constraint. + +Examples: Requested, Ticketed, Other + + + + + + + + + + A data type for Language Code Application. + +Examples: Display, Requested, Spoken, Written, Other + + + + + + + A data type for Ticket Number Constraint. Examples: String, Length 1 to 16. + + + + + + + + + + + A data type for Trip Purpose contextual list. + + + + + + + + + + + + + A data type for a Unique String Identifier constraint. + + + + + + + + + A data type for Size Values list constraint. Examples: Centimeter, Inch + + + + + + + + + + + A data type for Policy Type list constraint. Examples: Privacy_PII, Payment_PCI, Credentialing + + + + + + + Personnally Identifting Information Privacy Policy. + + + + + + + + + + + A data type for Policy Type. Examples: Privacy_PII, Payment_PCI, Credentialing + + + + + + + + Used for Alpha-Numeric Strings, length 1 to 3 + + + + + + + + Used for Alphabetic Strings, length exactly 3 + + + + + + + + Type definition for IATA airline designator (2-alphanumeric) or ICAO airline code (3-alpha). + + + + + + + + Used for Alpha-Numeric Strings, length 1 to 71 + + + + + + + + Used forAlpha-Numeric Strings, length 1 to 4. + + + + + + + + Use for numeric values, from 0 to 99 inclusive. + + + + + + + + + Used for Numeric Strings, length 1 to 19. + + + + + + + + + A data type for an Order Action list constraint. Examples: Cancel, Create, Divide, Delete, Reissue, Reprice, Update + + + + + + + + + + + + + + + + Examples: Imperial, Metric + + + + + + + + + + + A data type for an Order Action. Examples: Create, Update, Delete, Reissue, Reprice + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator.Tests/xsd/iata/xmldsig-core-schema.xsd b/XmlSchemaClassGenerator.Tests/xsd/iata/xmldsig-core-schema.xsd new file mode 100644 index 00000000..486d134f --- /dev/null +++ b/XmlSchemaClassGenerator.Tests/xsd/iata/xmldsig-core-schema.xsd @@ -0,0 +1,263 @@ + + + + + + +]> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/XmlSchemaClassGenerator/Generator.cs b/XmlSchemaClassGenerator/Generator.cs index b6e071eb..c38a3e8a 100644 --- a/XmlSchemaClassGenerator/Generator.cs +++ b/XmlSchemaClassGenerator/Generator.cs @@ -261,8 +261,12 @@ private void BuildModel() Types[AnyType] = objectModel; - AttributeGroups = Set.Schemas().Cast().SelectMany(s => s.AttributeGroups.Values.Cast()).ToDictionary(g => g.QualifiedName); - Groups = Set.Schemas().Cast().SelectMany(s => s.Groups.Values.Cast()).ToDictionary(g => g.QualifiedName); + AttributeGroups = Set.Schemas().Cast().SelectMany(s => s.AttributeGroups.Values.Cast()) + .DistinctBy(g => g.QualifiedName.ToString()) + .ToDictionary(g => g.QualifiedName); + Groups = Set.Schemas().Cast().SelectMany(s => s.Groups.Values.Cast()) + .DistinctBy(g => g.QualifiedName.ToString()) + .ToDictionary(g => g.QualifiedName); foreach (var globalType in Set.GlobalTypes.Values.Cast()) { @@ -605,30 +609,40 @@ private IEnumerable CreatePropertiesForAttributes(Uri source, Typ if (attribute.Use != XmlSchemaUse.Prohibited) { var attributeQualifiedName = attribute.AttributeSchemaType.QualifiedName; + var attributeName = ToTitleCase(attribute.QualifiedName.Name); - if (attributeQualifiedName.IsEmpty) + if (attribute.Parent is XmlSchemaAttributeGroup attributeGroup && attributeGroup.QualifiedName != typeModel.XmlSchemaName) { - attributeQualifiedName = attribute.QualifiedName; - - if (attributeQualifiedName.IsEmpty || attributeQualifiedName.Namespace == "") + var interfaceTypeModel = (InterfaceModel)Types[attributeGroup.QualifiedName]; + var interfaceProperty = interfaceTypeModel.Properties.Single(p => p.XmlSchemaName == attribute.QualifiedName); + attributeQualifiedName = interfaceProperty.Type.XmlSchemaName; + attributeName = interfaceProperty.Name; + } + else + { + if (attributeQualifiedName.IsEmpty) { - // inner type, have to generate a type name - var typeName = _configuration.NamingProvider.PropertyNameFromAttribute(typeModel.Name, attribute.QualifiedName.Name); - attributeQualifiedName = new XmlQualifiedName(typeName, typeModel.XmlSchemaName.Namespace); - // try to avoid name clashes - if (NameExists(attributeQualifiedName)) + attributeQualifiedName = attribute.QualifiedName; + + if (attributeQualifiedName.IsEmpty || attributeQualifiedName.Namespace == "") { - attributeQualifiedName = new[] { "Item", "Property", "Element" } - .Select(s => new XmlQualifiedName(attributeQualifiedName.Name + s, attributeQualifiedName.Namespace)) - .First(n => !NameExists(n)); + // inner type, have to generate a type name + var typeName = _configuration.NamingProvider.PropertyNameFromAttribute(typeModel.Name, attribute.QualifiedName.Name); + attributeQualifiedName = new XmlQualifiedName(typeName, typeModel.XmlSchemaName.Namespace); + // try to avoid name clashes + if (NameExists(attributeQualifiedName)) + { + attributeQualifiedName = new[] { "Item", "Property", "Element" } + .Select(s => new XmlQualifiedName(attributeQualifiedName.Name + s, attributeQualifiedName.Namespace)) + .First(n => !NameExists(n)); + } } } - } - var attributeName = ToTitleCase(attribute.QualifiedName.Name); - if (attributeName == typeModel.Name) - { - attributeName += "Property"; // member names cannot be the same as their enclosing type + if (attributeName == typeModel.Name) + { + attributeName += "Property"; // member names cannot be the same as their enclosing type + } } var property = new PropertyModel(_configuration)