Skip to main content
The OTA_ProductDescriptiveInfoRS is an OTA response message used in the Excursions NBC (Notification‑Based Content) flow to deliver descriptive product metadata for a tour activity. It surfaces the Excursion identifier, the set of Products offered, and the available Service types.

Purpose

This response provides:
  • TourActivityID — unique identifier of the excursion.
  • Products — product options offered under the excursion (e.g., 15‑min vs 30‑min tour).
  • Services — service delivery types (e.g., ticket only, with pickup).
  • Descriptive text for display.

Structure – Root Element

Common Attributes
  • Version — OTA spec version (e.g., 2008.1).
  • xmlnshttp://www.opentravel.org/OTA/2003/05.

Structure - Core Elements

TourActivityDescriptiveInfo

Container of one or more tour activities returned in the response. The structure is similar to Hotel NBC.

TourActivityDescriptiveContent

Contains the retrieved service details.

Schedule

Displays the available schedules for the retrieved Tour Activity.

TourActivityCategory

Displays the category of the retrieved activity. See Activity Codes.

ProductInfo

Shows short descriptions for each unit (Code).

ServiceInfo

Short description of the available service types.

ZoneInfo

Describes the zones where the Tour Activity operates. RefPoints Zone information. Can be used in Search and Avail messages.
OperationTime Description of the pick up and drop off points for the services that include transfer.

Descriptions

Includes a long description in the requested language if available.

Position

Geo location of the product.

Services

Shows different facts of the retrieved product.
Service@CodeDetail encodes a hierarchy using line breaks (pipes in textual examples). Related values can appear under Features/Feature@CodeDetail with a DescriptiveText value. Duration windows may be modeled with OperationSchedules/OperationSchedule.

MultimediaDescriptions

See Hotel Multimedia Descriptions.

ContactInfos

See Hotel Contact Infos.

Complete example

NBC Response

Best Practices

  1. Treat TourActivityID as the stable key for excursion mapping.
  2. Use ProductInfo/@Code and ServiceInfo/@Code to build your SKU axes; validate availability via incoming NBC rate plan notifications.
  3. If multiple TourActivityDescriptiveInfo blocks are present, index on RPH and TourActivityID for deterministic merges.