Public:Architecture Workgroup

From wiki.opentravel.org

Architecture »     Home • Announcements • Projects • Contacts

[edit] Work Group Overview

• 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.
• The Architecture roadmap diagram provides a high level view of the current and envisioned projects going on in the Architecture Workgroup.

• The following table outlines each of the current and possible future Public:Architecture Projects on the roadmap.

Basic Registration Program – TBD

Asynchronous Messaging Reference - We will standardise the way partners send messages, notifications and events to each other. This will enable realworld applications like mobile messaging (text/sms), customer/business notification emails, real world event handling (flight delays, hurricanes), and offline data transfer (like inventory and rates) to speed up operations like searching and pricing.

Reliable Messaging Reference - We will shows the partners the way to make asynchronous messages (data, messages, events) more reliable, so the sender of the message knows if it has been received or not, and help ensure messages are not duplicated. Essential for messages to be used in business critical applications.

Reference Guides - We will collate and publish these guides, to help your technology team understand the way OpenTravel standards work and how OpenTravel messages are implemented and exchanged. Helps reduces confusion and is especially valuable if your company is new to OpenTravel or XML / web services.

Conversation Management Reference - Sometimes systems need to do more than ask one question and get one reply. Conversations between systems allow multiple messages to be exchanged. This helps with complex multi-step operations including servicing existing bookings.

Authentication Reference - We will show the recommended way to ensure your services can only be accessed by your chosen trading partners. Companies are doing this many different ways now, if we can agree a common approach we can reduce the IT costs of partner integration and make everything more secure.

Collected Usage Profiles - OpenTravel is very flexible, the usage profiles allow you to see what others (existing and potential partners) have implemented. New members can learn from these profiles. The profile of a potential partner helps you see what functionality they support and helps you assess the effort of connecting to them.

Message Users Guide - The MUG document is designed to be high level, human readable guidelines and examples, on how to use each message. This document is essential for first time OpenTravel users. The "users" in this case are your technology team and business analysts.

Implementers Forum - This is an online notice board for developers to exchange questions and learn from each other's experience.

Wiki - This is a collaborative web site and knowledge base (built on the same technology as Wikipedia), which will act as a repository for OpenTravel related knowledge.

Basic UDDI Registry - When lots of companies are offering services (e.g. selling hotels), a UDDI registry is like an online catalog which computers can use to find specific types of services. This could eventually give the OpenTravel members the ability to dynamically find and connect to trading partners.

Policies & Procedures to Manage Service Lifecycles - TBD

Vendor Adaptors for Reference Software - TBD