opentravel 2.0 xml object suite introduction

© 2013 OpenTravel Alliance | www.opentravel.org 1

Introduction to the OpenTravel 2.0

XML Object Suite

About OpenTravel

Product Features

New Functionality

Component Model

Contact Us

January 2013

About OpenTravel – 2

Introducing the Component Model – 23

Product Features – 4

New 2.0 Functionality – 15

Contact Us – 31

2 © 2013 OpenTravel Alliance | www.opentravel.org

About OpenTravel

XML Standards for the Travel Industry

OpenTravel formed as a

member funded,

not-for-profit

organization.

1999

OpenTravel produces

the first open standards

for the travel industry.

2001

OpenTravel creates a

second open standard-

based schema product.

2011

OpenTravel provides the preferred open source XML standard for

the travel and leisure industry.

By using the OpenTravel specification, you’ll join a worldwide network of travel industry

suppliers, resellers, global distributors and integrators dedicated to

meeting their customer and trading partner XML distribution demands.


• OpenTravel maintains the

common information

exchange model (CIEM)

created by and for the

travel industry

• Represents travel industry

data at rest (implementer

stored) and in motion

(exchanged)

• The foundation of all

OpenTravel specifications

• Travel segment contextual

standard

schema

mapping

application

schema

mapping

service interface

schema

mapping

trading partner 1

standard

schema

mapping

application

schema

mapping

service interface

schema

mapping

trading partner 2

OpenTravel

Common

Information

Exchange Model

(CIEM)

About OpenTravel

Importance of Common Information Exchange Model


2.0 XML Object Suite Features

The XML Object Suite schema product has been

completely re-architected to support the new and innovative

approaches to travel industry distribution.


OpenTravel 2.0 XML Object Suite Features

Comprehensive Distribution Functionality

Air

Ground

Rail

Car Rental

Parking

Hotel

Hostel

Vacation

Rental

Extended

Stay

Event RFP

Packaged

Tour

Day Tour

Golf

Activity

Cruise

Offers

Travel Insurance

Travel Packages

Merchant Services

Online Maps

Loyalty Program

Subscriptions

Information Validation

Profiles

Location-Based Offers

2.0 provides distribution

functionality for all travel

segments.


The 2.0 functional model supports emerging business model

and distribution challenges.

Travel

Distribution

Demands

Multi-Participant

Sales & Distribution

Channels

Travel

Product

Differentiation

Travel Product

Bundling, Up-sell

& Cross-sell

Travel Product

Pricing & Bundling

Transparency

Personalized

Shopping &

Targeted Offers

Packaged Trip

Shopping &

Management

Partner & Customer

Subscriptions &

Notifications

Loyalty Program

with Customer

Recognition


Designed for Modern Distribution Channels


The 2.0 XML object architecture supports the rapidly

evolving travel environment by simplifying

interoperability.


XML Business Object Architecture

• Reusable, extensible and

substitutable XML objects

• Rapid deployment of new or

enhanced functionality

• Implementer proprietary

functionality

• Thin client applications The 2.0 XML architecture provides a

“use what you need” implementation

model.


Separate XML component

and service models

support:

• Versioning & maintaining internal 2.0

XML object libraries (with and without

proprietary extensions)

• Upgrading web services at an XML

object level versus an entire service

level 2.0 provides separate XML component

and service models to

accommodate your implementation

& upgrade requirements.


Independent Component & Service Models


Shopping, booking &

reservation management for

multiple trip components

• Sold through one channel

• Cross-sells between multiple partner

channels

Multi-participant distribution

channel support

• Packaging rules, booking rules, pricing

rules, etc.

• Co-managed itineraries

• Loyalty alliances


Packaged Trip Support for All Segments

Co-managed itineraries let you and your trading

partners create, modify and manage your own portions

of a packaged trip.

Your packaged trips may include flight, car rental,

lodging and activities (as an example) in a single

or co-shared reservation.


Built-in extension points

support unique internal

and trading partner

business requirements • Accommodate immediate and

emerging business

requirements

• Easy method for permanent

OpenTravel specification

enhancements

• Protects IT investment in

OpenTravel standard


Organic Extensibility

OpenTravel

PNR Object

OpenTravel

PNR Object

with your

extension

Trading Partner

1

Trading Partner

2

Your Reservation System

OpenTravel

PNR

Object

Your PNR

object

extension

You can easily extend 2.0 XML objects to meet your unique

trading partner and/ or system-to-system requirements.


Light-weight XML

objects for OpenTravel-

enabling thin-client

applications:

• Flexible XML-binding mechanism

to reduce XML object sizes for

light-weight transactions

• Functional support for

• Real-time customer notification

programs (e.g. flight delay)

• Location-specific offers

Light-weight transactions are a must to meet your

thin-client transaction latency demands, and 2.0

provides the mechanisms you need to exchange

light-weight XML objects.


Mobile Application Support


Your OpenTravel-enabled API’s can function standalone or exchange information

with OpenTravel-enabled applications.

Th

in C

lien

t A

pp

licati

on

s an

d A

PI’s

mobile kiosk

2.0 XML Objects

Web

Services

API

Th

ick C

lien

t A

pp

lica

tio

ns

Application

Web

Services

2.0 XML Objects

pc server

2.0

XM

L M

ESSA

GE S

UIT

E

PA

YLO

AD


OpenTravel-Enabled API Support


Include 2.0 XML objects in your existing WSDL

Use your existing web services


Two Implementation Methods

1

Start with (and extend) baseline WSDL to meet your

distribution requirements

Use 2.0 “Model” WSDL

2


Additional specification releases for

OpenTravel Members:

• Meet the pace of innovation in the travel industry

• Meet IT schedules and new channel integration

• Provide more time for IT departments

to review and enhance draft 2.0

releases before final publication

As an OpenTravel member, you have access

to draft publications when OpenTravel project

milestones are met or project work is

completed


More Frequent Member Releases


2.0 XML Object Suite New Functionality

2.0 introduces new functionality to help implementers

meet their business objectives.


OpenTravel 2.0 XML Object Suite New Functionality

Multi-Channel Interoperability & Cooperation

Support for multiple

channel participants in

shopping, booking

and ancillary

transactions

Two implementation

mechanisms available:

1. Use 2.0 pre-defined set of

channel definitions

• Extend categories and roles

as required

2. Create your own unique

channel definitions Aggregators

distributor

travel

agency

DMO

Suppliers/

Operators

supplier

operator

carrier

Information

Managers

loyalty program

profile repository

Consolidators bundler

packager



Multi-Channel Participant Transparency

Multi-Channel Participant

information

transparency

at the XML object level

Dedicated

Travel

Manager

Aggregator

Air Supplier

Supplier/ Operator

Air Supplier

Supplier/ Operator

Distributor

Aggregator

shopping

request

Air Supplier

Supplier/ Operator

Travel Product & Offer Quote

Details Pricing/ availability expiration date/ time

Participation eligibility

Bundling & pricing rules

Inclusions & exclusions, etc.

Channel participant

identification

Changes made to any information

received from other channel

participants



Personalized Shopping

Personalized Shopping Results

& Offers

Shopper Input Examples Shopping by trip purpose or type (Packaged Trip, Deal,

Destination, Family Trip, etc.)

Awards shopping Proximity search Keyword search

Social media search Flexible dates & locations

Promotions, discounts & negotiated rates

Loyalty credentials Special needs

Shopper Input

Processing Influencer Examples Loyalty tier, etc. Customer profile Party size

Trip purpose Flexible dates & locations

Promotions Offers

Processing

Influencers

Flexible Results Examples Shopper-designated result quantities and display (sort

by price, awards, best match, etc.)

Alternate results

Travel product side-by-side comparison

Mouse-over tips Supplier-specific branding

Flexible Results



Geocoding and Online Maps

Geocoded coordinate

metadata for all geographical

location XML Objects

Geocoding metadata includes:

Map URL Natural Area Code Latitude Longitude

Altitude Granularity Confidence Side of Street

Remark

Address Country Region State/ Province

City City Neighborhood etc.

Support for

online mapping services



Location-Specific Services

Targeted offers and information based on any combination of:

Book

Flight origin: Tampa

destination: Anguilla

Flight

Arrival location: Anguilla

Airport

Check-in

check-in: 13:00

departure: 17:00

Trip

Stay location: Anguilla

Stay length: 5

days

Travel Products (supplier & trading partners)

Stay Duration

Trip Segment

Trip Location, Radius & Proximity



Opt-In Subscriptions

Support for opt-in

customer subscriptions

• Customer/ trip personalized

• Preset term

• Trip-based (e.g. flight notifications that

expire when flight is completed)

• No expiration date (e.g. trip deal fare/ rate

reductions)

• Qualifiers

• Loyalty tier or status, age category, current

customers, etc.

• Associated with travel products and

offers or location-based

• Multiple content formats (plain text,

HTML, multimedia)

2.0 subscription XML objects can be associated with

opt-in subscription offers in websites, e-mails,

electronic itineraries, etc.

Weather

Alerts

Travel

Deals

Customer

Ratings

Flight

Notifications

Room

Availability

Loyalty

Earners

Customizable Subscription

XML Objects

Social

Media



XML Object-Level Secure Data Exchange

Sensitive “data in motion”

may be secured at the 2.0

XML object level or sent

as plain text

• Meet internal and trading

partner PCI compliance and

other mandated initiatives

• Support for

• Encryption

• Tokenization

• Masking

Reservation System

Payment Authorization

tokenized/

encrypted

Response Request

Payment Information

masked plain text

Credit Card Number


2.0 XML Object Suite Component Model


The 2.0 Component

Model contains a

hierarchical structure

of XML Objects used

to:

• Optimize component reuse

• Build other 2.0 XML objects

• 2.0 enable web services

• 2.0 enable APIs

OpenTravel 2.0 XML Object Suite Component Model

Hierarchical Component Model



Component Categories

Basic Components

• Not implementer extensible

• Enforce reuse throughout the open

distribution standard

• Protect integrity of (and

investment in) the open

distribution standard

• Used as “building blocks” for

other 2.0 components

Examples:

• 2.0 Simple Type

• 2.0 Value with Attributes

Extensible Components

• Implementer extensible

• Allow exchange of proprietary

information

• Prevents business disruption by

allowing exchange of data while

distribution standard is being

enhanced

Examples:

• 2.0 Enumeration

• 2.0 Core Object

• 2.0 Business Object



Extensible Components: Enumerations Implementer

Extensible

Closed Enumeration • Non-value extensible enumerated list

• Static list of values and system actionable

metadata

• Alternate language extensible

Open Enumeration • Fully extensible enumerated list



Extensible Components: Business Objects Implementer

Extensible

Business Object • Large-grained business objects

that are used to enable travel

distribution by sharing data

across heterogeneous business

applications both internal and

external

• Uniquely identifiable and define all

information known for the given object

• Typically associated with enterprise

business processes, such as:

• Shopping and availability

• Loyalty program management

• Reservation create, modify, cancel

and retrieve

Examples • Loyalty Account

• Profile

• Offer

• Reservation

• Itinerary

• Seat Map

• Vacation Rental Property

• Company

• Activity



Extensible Components: Core Objects Implementer

Extensible

Core Object

• Logical groupings of parts of

an object

• Used as “building blocks” in: • Other core objects

• Business objects

• For example, an Address core

object is a component of: • A Company business object

• A Directions core object

Examples • Directions

• Copyright

• Geocoding

• Seat

• Guest Room

• Vacation Rental Unit

• Origin & Destination

• Payment Card

• Email Address

• Passport



Extensible Components: Facets

2.0 Facet

• Organized collections of data in

2.0 Components

• Provide XML object extensibility

at the facet category level

• Provide XML binding substitution

mechanism

• Hierarchal inclusion structure

Facet Categories

includes

includes includes

Identifier A subset of the XML object data that uniquely identifies a

Business Object

Summary A subset of descriptive XML data intended for use in thin-

client services

Detail A larger subset of descriptive XML data intended for use in

functionally richer services

Query A subset of data that applies to a query process

Custom Proprietary implementer defined facet (business objects)



Extensible Components: Facet Substitution

Substitution Groups • Used with core and business

object facets

• Allows XML binding to one

substitution group facet

Business Object Substitution Group Example: Airport

I only need to

exchange an IATA

airport code

I need to exchange

links for airport

contact & directions in

search results

I need to include airport

terminal lounge

information and airport

ground transportation

information in a

reservation confirmation

ID

Summary

Detail


Travel distribution just got cool.

OpenTravel 2.0 XML Object Suite

Questions?

Valyn Perini, CEO

[email protected]

Bonnie Lowell, Specification Architect

[email protected]

MA Neff, Program Manager

[email protected]

www.OpenTravel.org

opentravel 2.0 xml object suite introduction

Travel

opentravel alliance

xml object architecture

xml object level

xml object libraries

xml architecture

industry distribution

functionality component

travel industryopentraveldata