Public:Architecture Workgroup

From wiki.opentravel.org

Jump to: navigation, search

Contents

[edit] Welcome to the OpenTravel Architecture Workgroup Page!

[edit] Overview

Image:Fotolia_5650951_XS_ARCHWG_SML.jpg

The Architecture Workgroup works on all aspects of the OpenTravel specification which are outside the contents of the XML messages themselves and which generally affect all of the industry workgroups equally.


[edit] Resources


[edit] Workgroup Leadership & Support

  • Chair: David Morley, Marriott International
  • Co-chair: Dave Hollander, Sabre
  • Interoperability Committee Rep 1: David Morley, Marriott International
  • Interoperability Committee Rep 2: Dave Hollander, Sabre Travel Network
  • OpenTravel Specifications Manager - Bonnie Lowell

[edit] OpenTravel Member Company Participants

Listed alphabetically by Company Name

Amadeus
Amtrak
ARINC
Continental Airlines
Datalex
DB Rent
EDS
Expedia
Hertz
HTNG
IBM
Intercontinental Hotels Group
Marriott International
Micron Nexus
OpenJaw
Pegasus
Royal Caribbean Cruise Lines
Rubicon Group
Sabre
Sita Aero
Travel Technology Initiative
Travelport/Galileo
Tsinghua University
Worldspan

[edit] Projects

  • Note that architecture workgroup projects are not tied to a specific publication release.

[edit] Active

OpenTravel 2.0 Prototype Project

OpenTravel has been conducting a study on a new initiative called “OpenTravel 2.0” led by the OpenTravel Architecture Workgroup. This project will create a prototype of the proposed new OpenTravel 2.0 type library and business objects. Please note this is a prototype and not an actual schema development project. The outcome of this study will be evaluated by OpenTravel leadership for its impact on current and future implementations.

Rail Common Services Model Definition Project

Led by the OpenTravel Architecture workgroup, this project will define and document a reference set of common core reservation services using OpenTravel best practices that could be implemented by any implementer of the OpenTravel Specification Rail messages. In some cases this would be used by solution providers creating an industry offering, in other cases this may be used by a member to prepare their current legacy solution for modernization by organizing appropriate functions around the OpenTravel model.

[edit] On-Hold

OpenTravel PCI/PII Schema Remediation Study
The Payment Card Industry (PCI) has mandated that owners of systems that process, store or exchange payment card information tighten security and handling of this type of information to prevent the theft and/or misuse of customer payment card information and other personally identifying information. OpenTravel schema messages and supporting files may contain both types of information and the purpose of this study is to determine the extent of usage of PCI data and PII within the OpenTravel Specification and make recommendations regarding protection, remediation, and best practices for collecting, storing and exchanging the information. It is anticipated that the result of this study will initiate an OpenTravel schema modification project.

[edit] Completed

OpenTravel Namespace Study Project

The Namespace Usage Study has identified the various common practices in the industry regarding namespaces and the trends that may be emerging or have emerged since the introduction of namespaces in the OpenTravel messages. The study reviews the history of the namespace policy in the OpenTravel Specification and discusses alternative options for suppliers, OTA’s and integrators within the travel industry.



[edit] Artifacts

Personal tools