Glossary - R

Rate

This field in the Daily Rates node of the property search response, gives the amount of the daily rate.

Rate Calculation

This describes the method used to calculate the rate. For example the rate calculation  for a property room booking can be Per Room or Per Person. If the calculation is per room, then the more rooms the higher the rate, if it is per person then the more guests, the higher the rate.

Region

There are three geography levels in iVectorConnect, Country, Region and Resort. The region is the same as the GeographyLevel2. See Geography Levels for more details.

RegionID

The Region ID maps each region in the system to a unique ID. The IDs are created when the regions are first loaded into the system. In the system, the region is also referred to as the GeographyLevel2. The Region ID is therefore the same as the Geography Level 2 ID. See Geography Levels for more details.

Resort

There are three geography levels in iVectorConnect, Country, Region and Resort. The resort is the most precise of these geography levels. It is the same as GeographyLevel3. See Geography Levels for more details.

Resort ID

The Resort ID maps a resort in the system to a unique ID. The IDs are created when the resorts are first loaded into the system.

In the system, the resort is also commonly referred to as the GeographyLevel3. The Resort ID is therefore the same as the Geography Level 3 ID. See Geography Levels for more details.

REST and RESTful requests

REST is a set of communications protocols used for accessing and manipulating data over the internet. The user requests a resource (data) via a URL and a representation of the resource is returned (e.g. an XML document). There is a set of defined rules on how data in REST requests can be structured and what can be done to the data. A REST request may also be called a RESTful request.

The only allowed structures for the data are either XML or JSON. In iVectorConnect the format used is XML.

The only four methods of manipulating data through RESTful requests are data creation, retrieval, update and deletion. The REST calls the user can make in iVectorConnect only make use of the data retrieval method.

Return Arrival Date

This is the local arrival date of the return leg of a journey, in the format YYYY-MM-DD. For example the 28th of June 2015 is represented 2015-06-28.

Return Arrival Time

This the time that the return leg of a journey arrives in local time. The time must be a valid time on the 24 hour clock in the format hh:mm, e.g. 00:35 means 12:35 in the morning, 12:00 means 12 o'clock noon.

Return Departure Date

This is the local departure date of the return leg of a journey, in the format YYYY-MM-DD. For example the 28th of June 2015 is represented 2015-06-28.

Return Departure Time

This is the local time that the return leg of a journey departs. The time must be a valid time on the 24 hour clock in the format hh:mm. For example, 00:35 means 12:35 in the morning, 12:00 means 12 o'clock noon.

Return Flight Class ID

This is a unique identifier for the flight class of the return flight.

Return Flight Code

This is a short often three to five character flight code on the outbound leg of a return flight that is used by airlines and at airports to identify a particular flight.

Return Operating Flight Carrier ID

A unique identifier for a particular flight carrier in iVectorConnect on the outbound leg of a flight.

Room Booking Token

A string of letters and characters that is an encoded summary of some of the room booking details needed to book the room. It is returned in the property booking response and required in the property prebook request.

Room Request

Room Requests form part of the Property search request. Each Property Search Request must contain at least one Room Request. The room request specifies the search parameters for that room.

For example a typical search for one room for 2 adults would use a property search request containing only one room request for 2 adults. If a user wanted to book 2 rooms, one with 2 adults and one with 1 adult and one child, for example, the property search request would include two room requests, with each request containing the details of the room required.

Room Type

This is a brief description of the type of room. For example, Double Deluxe or Twin. Room types are not standardized so there may be very different variations of similar room types for different hotels and different suppliers.

Room Type ID

This is a unique identifier for a particular room type in iVectorConnect.

Room View

This is a brief description of the view from the room, which may be important if there is a better view from rooms such as an ocean view, or to distinguish between two rooms with the same room type but different views. For example, Garden View or Sea View. The names of room views are not standardized so there may be very similar room views with different names for different hotels and different suppliers, e.g. a sea view may be described as a room view of 'Ocean View' by one supplier and 'Sea View' by another.

Room View ID

This is a unique identifier for a particular room view in iVectorConnect.