# Typographical conventions

#### XML Usage Description

**RG Bridge** utilizes OpenTravel standard XML for information exchange. The XML usage descriptions employ a pseudo-schema description format to specify the usage of XML elements and attributes as they apply to RG Bridge. The actual schema definitions are made available separately and adhere to industry standards, accommodating many use cases beyond what is required by RG Bridge.

#### Sample XML

Sample XML messages are provided throughout this document to aid in understanding the message usage. These messages are formatted for clarity. In the example message in Table A, the top-level element of the rate update request message is `OTA_HotelResNotifRQ`. The attributes of this element follow standard conventions.

**Sample XML**

```xml
<OTA_HotelResNotifRQ xmlns="http://www.opentravel.org/OTA/2003/0 " 
 
EchoToken="" 
 
TimeStamp="2011-01-26T10:22:00-05:00" 
 
Target="Production" 
Version="1.003" 
ResStatus="Book"> 
<POS> 
<Source> 
<RequestorID Type="13" ID="473"/> 
<BookingChannel Type="7" Primary="true"> 
<CompanyName>Travel Today</CompanyName> 
</BookingChannel> 
</Source> 
</POS> 
<HotelReservations> 
<HotelReservation> 
<RoomStays> 
<RoomStay> 
<!-- details omitted --> 
</RoomStay> 
</RoomStays> 
<ResGuests> 
<ResGuest> 
<Profiles> 
<ProfileInfo> 
<!-- details omitted --> 
</ProfileInfo> 
</Profiles> 
</ResGuest> 
</ResGuests> 
</HotelReservation> 
</HotelReservations> 
</OTA_HotelResNotifRQ> 
```

#### Message Focus and Formatting

**Identifiers**:

* To highlight the parts of the message being discussed, those parts have an identifier, like this: `OTA_CancelRQ`.

**Green Values**:

* Values shown in green must be set in a specific way because that is the only use of that element/attribute that RG Bridge can process. For example:

  xml

  ```
  <RateTimeUnit>Day</RateTimeUnit>
  ```

  * "Day" is the only value that can be passed to RG Bridge, even though the OTA schema allows other values.

**Red Values**:

* Values shown in red are specific to the message. For example:

  xml

  ```
  <CompanyName>Travel Today</CompanyName>
  ```

  * "Travel Today" specifies the channel name. These values are fictitious and used for sample purposes only.

**Formatting for Readability**:

* Messages have been formatted with additional new lines and tab characters for better readability. However, these are not part of the actual XML and must not be used in actual messages.

**XML Style Comments**:

* XML style comments in the samples are not part of the schema. They have been added to indicate incomplete sections in the XML, helping focus on the important parts and show the general pattern. For example:\<!— Content omitted-->

<br>


---

# 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/our-products/channel-manager/rg-bridge-supply-push/interface-specifications-reservation-notification-service/typographical-conventions.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.