All Downloads are FREE. Search and download functionalities are using the official Maven repository.

ota2015a.OTA_AirBaggageRQ.xsd Maven / Gradle / Ivy

There is a newer version: 3.0.0
Show newest version


	
		ALL SCHEMA FILES IN THE OPENTRAVEL ALLIANCE SPECIFICATION ARE MADE AVAILABLE ACCORDING TO THE TERMS DEFINED BY THE OPENTRAVEL LICENSE AGREEMENT AT http://www.opentravel.org/Specifications/Default.aspx.
	
	
	
		
			OpenTravel Air Baggage Request.
			Note: The air baggage message set provides baggage related functionality including pricing for checked bags, baggage allowance for an itinerary and lists of checked baggage. Baggage calculations may be based on an airline supplier, a specific flight, an air reservation, a traveler type, traveler loyalty benefits, a fare group (including private and negotiated fares) and an origin/ destination pair.
		
		
			
				
					
						Point of Sale.
					
					
						
							
						
					
				
				
					
						Message level processing directives.
						OpenTravel Best Practice: Information Message Level Processing Directives: For messages that have message level processing directives specified, and also have child elements with attributes where the same information may be specified, the child attributes are assumed to inherit the message level processing directives UNLESS child-level information has been specified (which then overrides the message-level directives, but ONLY for the child-level specification.)
					
					
						
							
								Query type.
								Example: BaggageCharge
								Note: This is the requested baggage query type that the receiving will fulfill.
							
							
								
									
										
											Retrieves baggage charges for a specified itinerary or traveler(s).
										
									
									
										
											Retrieves baggage allowances for a specified itinerary or traveler(s).
										
									
									
										
											Retrieves both baggage allowances and charges for a specified itinerary or traveler(s).
										
									
									
										
											Retrieves a list (or catalog) of all bags that may be checked for a specified itinerary and airline carrier that includes pricing. Typically used to calculate applicable charges. All bag types and pricing information.
										
									
								
							
						
						
							
								Pricing/ filing currency.
								Example: USD
								OpenTravel Best Practice: Currency Type Designation: Unless otherwise noted, all currency code designations are three alpha characters and WILL follow ISO 4217 prescribed format. Additionally, all currency amounts SHOULD have decimal places (minor units) specified.
							
						
						
							
								Currency decimal places.
								Example: 2
								OpenTravel Best Practice: Currency Type Designation: Unless otherwise noted, all currency code designations are three alpha characters and WILL follow ISO 4217 prescribed format. Additionally, all currency amounts SHOULD have decimal places (minor units) specified.
							
						
					
				
				
					
						Baggage information.
					
					
						
							
								
									
										If true, this baggage is already checked in.
									
								
								
									
										Excess baggage occurrences.
										Example: 2
									
								
								
									
										Baggage Item Reference ID.
										Example: 1
										Note: This is a unique reference ID for one baggage item that is set here and may be referenced elsewhere in this message.
										OpenTravel Best Practice: Using Reference Place Holders: The reference place holder (RPH) is a unique ID assigned to an instance in a collection of like items (e.g. used to assign a unique ID to each passenger in a list of passengers. When referencing an RPH, the same RPH type is used to identify the assigned unique ID in an element that references the item in a collection.
									
								
								
									
										Fare Reference ID.
										Example: 2
										Note: This fare reference ID was defined elsewhere in this message.
										OpenTravel Best Practice: Using Reference Place Holders: The reference place holder (RPH) is a unique ID assigned to an instance in a collection of like items (e.g. used to assign a unique ID to each passenger in a list of passengers. When referencing an RPH, the same RPH type is used to identify the assigned unique ID in an element that references the item in a collection.
									
								
								
									
										Flight Segment Reference ID.
										Example: 3
										Note: This flight segment reference ID was defined elsewhere in this message.
										OpenTravel Best Practice: Using Reference Place Holders: The reference place holder (RPH) is a unique ID assigned to an instance in a collection of like items (e.g. used to assign a unique ID to each passenger in a list of passengers. When referencing an RPH, the same RPH type is used to identify the assigned unique ID in an element that references the item in a collection.
									
								
								
									
										Pricing Reference ID.
										Example: 1
										Note: This pricing reference ID was defined elsewhere in this message.
										OpenTravel Best Practice: Using Reference Place Holders: The reference place holder (RPH) is a unique ID assigned to an instance in a collection of like items (e.g. used to assign a unique ID to each passenger in a list of passengers. When referencing an RPH, the same RPH type is used to identify the assigned unique ID in an element that references the item in a collection.
									
								
								
									
										Traveler Reference ID.
										Example: 2
										Note: This traveler reference ID was defined elsewhere in this message.
										OpenTravel Best Practice: Using Reference Place Holders: The reference place holder (RPH) is a unique ID assigned to an instance in a collection of like items (e.g. used to assign a unique ID to each passenger in a list of passengers. When referencing an RPH, the same RPH type is used to identify the assigned unique ID in an element that references the item in a collection.
									
								
							
						
					
				
				
					
						Associated company information for the traveler.
					
				
				
					
						Optional services associated with electronic miscellaneous documents.
					
				
				
					
						Checked bag(s) included fare reference information.
						Note: Provides a reference for fares that include checked bags as some baggage allowances and charges are based on a fare code.
					
					
						
							
								
									Detailed fares and related information for the specified fare.
								
								
									
										
									
								
							
						
						
							
								Total passenger quantity.
								Example: 2
								Note: This is the total passenger quantity for the entire itinerary.
							
						
						
							
								The total price for the entire itinerary for all passengers of all types.
							
						
						
							
								Currency type.
								Example: USD
								Note: This does not need to be set if it is the same as the @PricingCurrency.
								OpenTravel Best Practice: Currency Type Designation: Unless otherwise noted, all currency code designations are three alpha characters and WILL follow ISO 4217 prescribed format. Additionally, all currency amounts SHOULD have decimal places (minor units) specified.
							
						
						
							
								Currency decimal places.
								Example: 2
								Note: This does not need to be set if it is the same as the @PricingCurrency.
								OpenTravel Best Practice: Currency Type Designation: Unless otherwise noted, all currency code designations are three alpha characters and WILL follow ISO 4217 prescribed format. Additionally, all currency amounts SHOULD have decimal places (minor units) specified.
							
						
						
							
								Fare Reference ID.
								Example: 1
								Note: This is a unique reference ID for one set of fare information that is set here and may be referenced elsewhere in this message.
								OpenTravel Best Practice: Using Reference Place Holders: The reference place holder (RPH) is a unique ID assigned to an instance in a collection of like items (e.g. used to assign a unique ID to each passenger in a list of passengers. When referencing an RPH, the same RPH type is used to identify the assigned unique ID in an element that references the item in a collection.
							
						
						
							
								Traveler Reference ID.
								Example: 2
								Note: This traveler reference ID was defined elsewhere in this message.
								OpenTravel Best Practice: Using Reference Place Holders: The reference place holder (RPH) is a unique ID assigned to an instance in a collection of like items (e.g. used to assign a unique ID to each passenger in a list of passengers. When referencing an RPH, the same RPH type is used to identify the assigned unique ID in an element that references the item in a collection.
							
						
					
				
				
					
						Flight segment information.
					
				
				
					
						Traveler loyalty program information.
					
					
						
							
								If true, this traveler is already checked in.
							
						
						
					
				
				
					
						Merchandising offers associated with the fare or traveler.
					
				
				
					
						PNR information for the traveler.
					
					
						
							
								
									
										If true, this traveler is already checked in.
									
								
								
									
										Associated ID.
										Example: UAA512346
										Note: This may contain an associated ID, such as a conjunctive ticket number.
									
								
							
						
					
				
				
					
						Pricing information including ticket information, optional charges, restrictions, negotiated fares, private fares and original issuer.
					
					
						
							
								
									Information for negotiated fares and services.
								
								
									
										
											
												
													
														Supplier/ carrier airline information.
													
												
											
										
									
								
							
							
								
									The original ticket/document issue information.
								
								
									
										
											Ticket/ document number,
											Example: BWA42317
											Note: This is the original ticket/document number.
										
									
									
										
											Issuing agent ID.
											Example: 91256690
											Note: This is the ID of the original issuer of the ticket/document.
										
									
									
										
											Date of issue.
											Example: 2013-01-13
											Note: This is the date the ticket/document was originally issued.
										
									
									
										
											Original issue location.
											Example: NYC14
										
									
									
										
											Original issuing airline code.
											Example: BWA
										
									
								
							
							
								
									Information for private fares and services.
								
							
						
						
							
								Carrier or Service Record Owner code.
								Example: RES = all reservation centers
							
						
						
							
								Optional charge code.
								Example: C = Catalog only, S = Service charge details
								Note: This is a code that indicates if catalog of charges or services are requested along with allowance.
							
						
						
							
								Pricing Reference ID.
								Example: 1
								Note: This is a unique reference ID for one set of pricing information that is set here and may be referenced elsewhere in this message.
								OpenTravel Best Practice: Using Reference Place Holders: The reference place holder (RPH) is a unique ID assigned to an instance in a collection of like items (e.g. used to assign a unique ID to each passenger in a list of passengers. When referencing an RPH, the same RPH type is used to identify the assigned unique ID in an element that references the item in a collection.
							
						
						
							
								Country of sale code.
								Example: us
								Note: This is the country in which the booking will be made (sold).
								OpenTravel Best Practice: Country Code Designation: Unless otherwise noted, all country code designations are two characters and WILL follow ISO 3166 prescribed format.
							
						
						
							
								City or airport of ticketing code.
								Example: TYO
								Note: This is the city or airport code where the ticket will be/ has been issued in IATA encoding.
								OpenTravel Best Practice: Airport Code Designation: Unless otherwise noted, all airport code designations WILL be three characters and WILL follow IATA airport code prescribed format.
								OpenTravel Best Practice: City Code Designation: Unless otherwise noted, all city code designations WILL be three characters and WILL follow IATA city code prescribed format.
							
						
						
							
								Country of ticketing code.
								Example: US
								Note: This is the country where the ticket will be issued.
								OpenTravel Best Practice: Country Code Designation: Unless otherwise noted, all country code designations are two characters and WILL follow ISO 3166 prescribed format.
							
						
					
				
				
					
						Service family information used to filter response results.
					
				
				
					
						Traveler type and quantity information.
						Note: This contains the number of travelers and their age classification if traveler details are not known.
					
					
						
							
								Traveler age and category.
							
						
						
							
								Traveler Type Reference ID.
								Example: 1
								Note: This is a unique reference ID for one traveler that is set here and may be referenced elsewhere in this message.
								OpenTravel Best Practice: Using Reference Place Holders: The reference place holder (RPH) is a unique ID assigned to an instance in a collection of like items (e.g. used to assign a unique ID to each passenger in a list of passengers. When referencing an RPH, the same RPH type is used to identify the assigned unique ID in an element that references the item in a collection.
							
						
					
				
			
			
		
	





© 2015 - 2024 Weber Informatics LLC | Privacy Policy