All Schema files in the OTA specification are made available according to the terms defined by the OTA License Agreement at http://www.opentravel.org/ota_downloads_form.cfm The OTA_HotelStatsNotifRS is the message used to indicate the status of processing the OTA_HotelStatsNotifRQ message. Used for codes in the OTA code tables. Possible values of this pattern are 1, 101, 101.EQP, or 101.EQP.X. The Reference Place Holder (RPH) is an index code used to identify an instance in a collection of like items (e.g. used to assign individual passengers or clients to particular itinerary items). Used for Character Strings, length 0 to 128. Used for Character Strings, length 1 to 128. Used for Character Strings, length 1 to 16. Used for Character Strings, length 1 to 32. Used for Character Strings, length 1 to 64. A placeholder in the schema to allow for additional elements and attributes to be included if required, per Trading Partner Agreement (TPA). Identifies a company by name. Provides detailed information on a company. The division name or ID with which the contact is associated. The department name or ID with which the contact is associated. Standard way to indicate that an error occurred during the processing of an OTA 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". Refer to OTA Code List Error Warning Type (EWT). Details of the error. 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. A collection of errors that occurred during the processing of a message. An error that occurred during the processing of a message. Textual information to provide descriptions and/or additional information. Language of the text. Information to acknowledge the receipt of a message. The presence of the empty Success element explicitly indicates that the OTA versioned message succeeded. Used in conjunction with the Success element to define one or more business errors. Errors is returned if the request was unable to be processed. May be used to return the unique id from the request message. The OTA_PayloadStdAttributes defines the standard attributes that appear on the root element for all OTA payloads. Standard way to indicate successful processing of an OTA message. Returning an empty element of this type indicates success. Allows extensions to be added to the OTA specification per trading partner agreement. An identifier used to uniquely reference an object in a system (e.g. an airline reservation reference, customer profile reference, booking confirmation number, or a reference to a previous availability quote). Identifies the company that is associated with the UniqueID. Standard way to indicate successful processing of an OTA 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". Refer to OTA Code List Error Warning Type (EWT). Details of the warning. Reference Place Holder used as an index for this warning. Collection of warnings. Used in conjunction with the Success element to define a business error. 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. Provides detailed information on a company. Used to provide the company common name. Refer to OTA Code List Travel Sector (TVS). Identifies a company by the company code. Identifies the context of the identifying code, such as DUNS, IATA or internal code, etc. 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 abbreviated version of the error in textual format. If present, this refers to a table of coded values exchanged between applications to identify errors or warnings. Refer to OTA Code List Error Codes (ERR). If present, this URL refers to an online description of the error that occurred. If present, recommended values are those enumerated in the OTA_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. This value may contain a concatenation of a unique failed transaction ID with specific record(s) associated with that transaction. Used to provide a required unique identifier. A unique identifying value assigned by the creating system. The ID attribute may be used to reference a primary-key value within a database or in a particular implementation. Identifies language. Language identification. The OTA_PayloadStdAttributes defines the standard attributes that appear on the root element for all OTA 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 OTA 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. Identifes the primary language for the message. Identifes the alternate language for the message. 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. 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. Provides unique identification information. URL that identifies the location associated with the record identified by the UniqueID. A reference to the type of object defined by the UniqueID element. Refer to OTA Code List Unique ID Type (UIT). The identification of a record as it exists at a point in time. An instance is used in update messages where the sender must assure the server that the update sent refers to the most recent modification level of the object being updated. Used to provide a required unique identifier. Used to identify the source of the identifier (e.g., IATA, ABTA).