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

ota2015a.OTA_RailConfirmBookingRS.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.
	
	
	
		
			The Rail Confirm Booking RS message is the response message for an OTA_RailConfirmBookingRQ that commits one or more provisionally booked messages that have been processed successfully from an OTA_RailBookRQ message but are not yet confirmed in the trading partners system as booked.

If the request message has been processed successfully, the Confirmation element in this response message contains the PNR Locator list that contains only unique ID(s) –OR- unique ID(s) with corresponding reservation information. NOTE that this is an implementation detail that you should discuss with your trading partners prior to implementing this message.
		
		
			
				
					
						
							The standard way to indicate successful processing of an OpenTravel message. Returning an empty element of this type indicates success.
						
					
					
						
							The standard way to indicate successful processing of an OpenTravel message, but one in which business warnings are generated.
						
					
					
						
							The PNR locator list for the provisional reservations that are now confirmed as booked.
						
						
							
								
									Allows for the inclusion of only a Unique ID for the confirmed reservations -OR- the unique ID and reservation details.
								
								
									
										The reservation confirmation number that uniquely identifies a reservation.  Note that the @Type attribute will typically contain a value of 40 which is a "Confirmation number" - See OpenTravel Code List Unique ID Type (UIT).
									
								
								
									
										The unique ID of the reservation with reservation details including itinerary, traveler or traveler count, payment rules and ticket fulfillment information.
									
								
							
						
					
				
				
					
						A collection of errors that occurred during the processing of this message.
					
				
			
			
		
	





© 2015 - 2024 Weber Informatics LLC | Privacy Policy