OpenTravel specification architect gives a high level view of the differences and advantages to consider when migrating from the existing 1.0 open standard schema to the 2.0 XML Object Suite.

1. 2012 North American
Advisory Forum
Miami, Florida
Which OpenTravel
Schema Product is
Right for Me?

2. 2
Introduction to
OpenTravel

3. OpenTravel provides the XML distribution standard
3
of choice for the travel industry…
The OpenTravel Alliance provides a
community where companies in the
electronic distribution supply chain work …this enables suppliers and
together to create an accepted structure distributors to speak the
for electronic messages… same interoperability
language, trading partner to
trading partner.
OpenTravel’s membership
base includes travel
suppliers, global distributors,
technology integrators and
other standards bodies and
educational organizations.

4. What OpenTravel does and doesn’t do…
4
OpenTravel does not…
OpenTravel does… …own or have access to any
…provide open source XML schema supplier inventory (such as rental
that allows trading partners to cars, flights and hotels.) To access
exchange data in a highly supplier inventory, you must have
interoperable manner. trading partner agreements in place
with suppliers and distributors.

5. 5
Key
OpenTravel
Terminology

6. OpenTravel “XML Specification” Definition
6
Adhere to schema
architecture & design best
practices
Adhere to W3C and Have a status of
other defacto Published, Past or
OpenTravel standards Draft
specifications are
created by travel
industry experts.
OpenTravel
XML
Specifications

7. OpenTravel “Publication” Definition
7
Download
XML Messages Online
Publication Learning
Artifacts Resources
An OpenTravel
Publication contains Publication
a collection of items Process
Add-Ons
and processes.
Publication
Calendar
Publication
Processes

8. OpenTravel “Publication Add-On” Definition
8
As a benefit to implementers,
Opentravel provides “Publication
Add-Ons” that are an assortment
of free components, tools and
v
services for working with
OpenTravel and supported third-
party schema products.

9. OpenTravel “Lexis” Definition
9
A key feature of OpenTravel
schema products is that they are
highly interoperable…
and each OpenTravel-enabled
v
service has an XML payload that
already knows how to speak to
other OpenTravel XML
payloads…

10. OpenTravel “Lexis” Definition
10
The OpenTravel Lexis is a
logical and physical data model
with a supporting set of
operations that define and
enforce OpenTravel’s
v
vocabulary-based common
information exchange model,
which is often abbreviated as
“C–I–E–M” and pronounced
“SIM”.

11. 11
The
OpenTravel
Body of Work

12. The OpenTravel specification contains
12
XML business functionality for numerous travel segments…
In addition to mature segments,
including airline, car rental and
hotel, OpenTravel schema
v
products support emerging
segments such as day tours &
activities, golf, vacation rentals
and ground transportation.

13. OpenTravel 1.0 XML Message Suite Overview
13
The OpenTravel 1.0 XML Message
Suite has a message-based
architecture and that is the key
v
architectural difference between
this schema product and the
OpenTravel 2.0 XML Object Suite.

14. OpenTravel 2.0 XML Object Suite Overview
14 Available
July 2012
The key architectural difference
between the new OpenTravel 2.0
XML Object Suite and the
OpenTravel 1.0 XML Message
v
suite is XML objects versus
messages that allow trading
partners to construct lighter-weight
and interoperable xml payloads
with multiple extension points.

15. OpenTravel Schema 15
Product Comparison
1.0 XML Message Suite 2.0 XML Object Suite
Common Information Exchange Model OpenTravel Lexis Common Information Exchange Model
All Supported Travel Segments Business Functionality All Supported Travel Segments
Download, Submit Comments Free Download Download, Submit Comments
Create, Enhance, Version, Publish Process Create, Enhance, Version, Publish
3 Times Per Year Publication Schedule 3 Times Per Year
XML Message Collection Architecture XML Object Libraries
XML Message (Root) Level Extensibility XML Object Level
Standard Artifacts Tools 2.0 Component Builder, Etc.

16. 16
Schema Product
Selection

17. 17
Considerations for Selecting an XML Standard
 IT Environment
 Rapid application development
 Multi-platform (web, mobile)
 RESTful services
 High level of resource re-use across applications
 IT staff size and maturity
 Legacy systems
 Product & Services
 Frequency of service/ product innovation that affects IT systems
 Multi-modal services & products
 Proprietary Data Exchange
 Trading Partners
 Quantity
 IT maturity level
 “Middle Men” – global distribution, etc.