# Transaction specifications The following sections describe in detail the message structure required to perform various updates of hotel data within the HCD. The payload for transactions received by Enterprise connectivity should follow the schema defined for the OTA\_HotelDescriptiveContentNotifRQ (version 2005B) message. The payload for transactions returned to the client by ENTERPRISE CONNECTIVITY will follow the schema defined for the OTA\_HotelDescriptiveContentNotifRS (version 2005B) message. **Element table definitions** Each transaction is defined in terms of the elements and attributes that are used within that transaction. For each element or attribute, the following information is presented: | **Column Heading** | **Description** | | ------------------ | ---------------------------------------------------------------------------------------------------------- | | Element Name | The name of the element | | Attribute Name | The name of the attribute | | Level | The depth of the current element in the XML tree structure, with ‘0’ being the root element in the message |
|

Required / Optional /

Conditional

|

Identification code to state if the element or attribute is: R Required – Must be populated within the message O Optional – Not required for processing

C Conditional - The element or attribute contains a specific condition that must be met for processing.

| | ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | GDS |

Identification code to state if the data found in the element or attribute will be delivered to the GDS and if it is required or optional for GDS updating.

R Required – Must be populated for the property in order to deliver updates to the GDS. A warning will be returned if not present.

O Optional – The data will be delivered to the GDS only if present.

C Conditional – The element or attribute contains a specific condition that must be met for delivery to the GDSs.

No value in this column indicates the data will never be delivered to the GDSs. NOTE: GDS updates will only occur if the hotel chain has subscribed to the GDS updating service via HCD.

| | Example | Example data for free form text fields | | Usage | Indicates the max length, codes list or valid enumeration values for the field. The definitions found within the OTA XML schemas will apply unless specifically stated within this section. When length is specified in bytes, this indicates a multi-lingual field and the value is applicable to non-English text. | | Description | Additional information associated to the element or attribute. See GDS Notes in this column for further information on delivery of HCD data to the GDSs. | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://developer.rategain.com/content/content-update-1/transaction-specifications.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.