# GDS information

Although OpenTravel allows unlimited occurrences of each element within the OTA\_HotelDescriptiveContentNotifRQ message, ENTERPRISE CONNECTIVITY has elected to set limits for many of these elements. Unless specified under the Usage column below, ENTERPRISE CONNECTIVITY only allows one instance of each element per property message.<br>

| **Element** | **Level**   | **Attribute**      | <p><strong>R</strong></p><p><strong>O C</strong></p> | <p><strong>G</strong></p><p><strong>D S</strong></p> | **Example** | **Usage**                                                      | **Description**                                                                                                              |
| ----------- | ----------- | ------------------ | ---------------------------------------------------- | ---------------------------------------------------- | ----------- | -------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| GDS\_Info   | 3           | <p><br></p>        | O                                                    | <p><br></p>                                          | <p><br></p> | <p><br></p>                                                    | Only 1 element allowed per Property message.                                                                                 |
| GDS\_Codes  | 4           | <p><br></p>        | R                                                    | <p><br></p>                                          | <p><br></p> | <p><br></p>                                                    | <p>Required when</p><p>GDS\_Info is present.</p><p><br></p><p>Only 1 element allowed per Property message.</p>               |
| GDS\_Code   | 5           | <p><br></p>        | R                                                    | <p><br></p>                                          | <p><br></p> | <p><br></p>                                                    | Only 1 element allowed per Property message.                                                                                 |
| <p><br></p> | <p><br></p> | ChainCode          | R                                                    | R                                                    | ZZ          | 2 Char                                                         | <p>GDS Chain Code</p><p><br></p><p>Required for GDS\_Code element.</p>                                                       |
| <p><br></p> | <p><br></p> | GDS\_Property Code | R                                                    | R                                                    | ZZ1234      | 6 Char                                                         | <p>GDS Property Id</p><p><br></p><p>Required for GDS\_Code element.</p>                                                      |
| <p><br></p> | <p><br></p> | GDS\_Name          | R                                                    | R                                                    | <p><br></p> | <p>Amadeus</p><p>ApolloGalileo</p><p>Sabre</p><p>Worldspan</p> | <p>Name of the GDS System.</p><p><br></p><p>Enumerated attributed. Must use one of the values found in the Usage column.</p> |

**Schema design view**

<figure><img src="/files/T5EwfXqJ08hUp2KixIiS" alt=""><figcaption></figcaption></figure>

**Example transaction**

```xml
<OTA_HotelDescriptiveContentNotifRQ xmlns="
http://www.opentravel.org/OTA/2003/05
" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance
" Version="4.000" PrimaryLangID="EN">
<HotelDescriptiveContents>
<HotelDescriptiveContent UnitofMeasureCode="1" CurrencyCode="USD" TimeZone="CST" BrandCode="ZZ"
HotelCode="AA123" HotelName="Test Hotel" Overwrite="false">
<GDS_Info>
<GDS_Codes>
<GDS_Code ChainCode="YY" GDS_Property="12345" GDS_Name =”Sabre”/> </GDS_Codes>
</GDS_Info>
</HotelDescriptiveContent>
</HotelDescriptiveContents>
</OTA_HotelDescriptiveContentNotifRQ>
```


---

# 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/gds-information.md?ask=<question>
```

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.