# Typographical Conventions

### XML Usage Description

**RG Bridge** utilizes OpenTravel standard XML to facilitate 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 provided separately. These schemas adhere to industry standards and accommodate many use cases beyond those required by RG Bridge. Only the elements and attributes described in the XML Usage description are used by RG Bridge. Any other element or attribute passed in the message will be ignored.

#### Sample XML

Sample XML messages are provided throughout this document to aid in understanding message usage. These messages are formatted for clarity and are set inside tables with dashed borders. All OpenTravel messages follow a consistent format, with a single top-level element. The element name starts with "OTA\_".

In the example message in Table A, the top-level element of the rate update request message is OTA\_HotelRateAmountNotifRQ. The attributes of this element are standard.

**Table A: Sample XML**

```xml
<OTA_HotelRateAmountNotifRQ xmlns="http://www.opentravel.org/OTA/2003/05"  
TimeStamp="2005-02-02T12:00:00" 
 
Target="Production" 
Version="1.002"> 
<RateAmountMessages ChainCode="CY" HotelCode="ATLPE"> 
 
 <RateAmountMessage> 
 
 	<StatusApplicationControl  Start="2005-04-01"  
 	End="2005-04-01" 
 
 	RatePlanCode="BARA00" 
 
 	InvCode="STD"/> 
 
 	<Rates> 
 
 	<Rate RateTimeUnit="Day" 
 
 	Start="2005-04-01" 
 
 	End="2005-04-01" 
 
 	CurrencyCode="USD"> 
 
 	<BaseByGuestAmts> 
 
 	<BaseByGuestAmt AmountBeforeTax="100.00"/> 
 
 	</BaseByGuestAmts> 
 
 	</Rate> 
 
 	</Rates> 
 
 </RateAmountMessage> 
 
 </RateAmountMessages> 
 
</OTA_HotelRateAmountNotifRQ> 
```

To emphasize the important parts of the message, the relevant sections have been highlighted with a lime background, such as: `RateAmountMessages`.

* **Green Values**: These values must be set in a specific way because RG Bridge can only process them in that manner. For example, in `RateTimeUnit="Day"`, "Day" is the only value that can be passed to RG Bridge, even though the OTA schema allows other values.
* **Red Values**: These values are significant for the message. For example, in `RatePlanCode="BARA00"`, "BARA00" specifies the rate type and is crucial for the operation. Note that these values are fictitious and used for sample purposes only.

For better readability, the messages have been formatted with additional new lines and tab characters. However, these are not part of the actual XML and should not be used in real messages.

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 important parts and show the general pattern. For example:

\<!-- Content omitted -->.


---

# 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-availability-and-rates-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.