Public:Architecture Projects
From wiki.opentravel.org
|
Architecture » Home • Announcements • Projects • Contacts |
Contents |
[edit] Overview
[ Architecture Workgroup Action Items ]
The following items are currently the topics for the Architecture Workgroup conference calls. Most of them should have more full descriptions in what follows below.
- Roadmap
- PCI Compliance
- Reliable Messaging
- Conversation/Session Management
- TypeX Recommendations
- TPA_Extensions 2.0
- Internationalization
- OpenTravel 2.0 Planning
- Prep for 2008 OpenTravel Advisory Forum
- Planning for OpenTravel 2.0, 1.X dual tracks
A presentation on the OpenTravel 2.0 was given to IO and the Board at their February meetings.
[edit] Architecture Subcommittee Roadmap
For the past several years, the OTA architecture subcommittee has proactively issued guidance related to specific interoperability issues addressing several topic areas. The group now plans to build on that work by preparing a roadmap for the future. This roadmap will provide a framework against which projects can be executed over the next two to three years. This framework will be outlined in a brief document with any necessary supporting graphics. The intended audience of this document is OTA membership. Future iterations of this work may involve creating document(s) or collateral targeted to a public audience.
Status: Open
Target Completion: Ongoing
[edit] Other Efforts
[edit] Wiki/Website/Forum Support
The Architecture Subcommittee set up this wiki and continues to assist with and consult on its evolution. is active in defining Usage Profiles and how they are useful in promoting interoperability.
Status: Open
- OpenTravel Forum - Target Completion: Nov 2007 - Integration of some Forum software with the wiki
- OpenTravel Mailing List Integration - Target Completion: TBD - Integration of Forum
[edit] Usage Profiles
The Architecture Subcommittee is active in defining Usage Profiles and how they are useful in promoting interoperability.
Status: Open
Target Completion: TBD
[edit] Conversation Management Recommendations
This may soon become a PTP (Project Team Proposal) for a real project.
For now, we are in preliminary discussions about a project for Convresation Management Recommendations.
John Ramos Yeo (EDS) has volunteered to spearhead the project.
Status: Open
Target Completion: Survey to be done by Q2 2008 Survey proposal:
Open Travel Survey for converwation management
1) General questions
a) Do you use exchange state-ful transactions with partners or other computers ? b) Would you be interested in mainaging conversations( for related transactions ) using a new OpenTravel format ? c) Would you be interested in transporting state-ful transacations over the public internet ? d) Are you familiar with the any legacy standards e.g. IATA host to host header ? e) If applicable, would you be interested in adapting a conversation management protocol independent of any lower layer protocls e.g. HTTP, socket ?
2) Session management questions
a) If applicable, do you manage conversation at the application level ? b) Do you cookies for maintaining or tracking a session.
3) Application protocol questions
a) What protocol do you use for managing conversation ( or sessions)? Examples are:
i) IATA host to host header
ii) Propietary
iii) Terminal emulation
b) Do you support SOAP client over HTTP ?
c) Do you support SOAP server over HTTP ?
4) Security questions
a) Do you encrypt your payload? b) Do you support SSL ( secured socket layer)
5) Link protocol questions
a) If applicable, what link protocol do you use for transporting legacy paylods e.g. X.25 , UDP/P, TCP/IP, SNA b) Do you support native IP connection via the public internet from your host system ( not workstations).
[edit] Reliable Messaging Recommendations
This may soon become a PTP (Project Team Proposal) for a real project.
For now, we are in preliminary discussions about a project for Reliable Messaging Recommendations.
John Ramos Yeo (EDS) has volunteered to spearhead the project.
Status: Open
Target Completion: Q2 2008 for survey
Survey proposal:
Open Travel Survey for reliable messaging
0) Need for a Reliable Messaging recommendation (some more questions from Stephen Adkins)
a) Do you think that it would be valuable for OpenTravel to issue guidance on exchanging messages asynchronously and /or reliably?
b) Do you currently implement asynchronous and/or reliable message exchange?
c) Do you intend to implement asynchronous and/or reliable message exchange in the future?
d) Is it important to you that your asynchronous and/or reliable message exchange protocol be highly interoperable with a wide range of partners?
Do you think an OpenTravel Reliable Messaging Recommendation would help that interoperability come about?
e) If OpenTravel issued a Reliable Messaging Recommendation, would it be likely that you would implement it?
1) General questions
a) Do you exchange Type-B ( reliable messaging) messages with partners or other computers ? b) Would you be interested in exchanging Type-B messages using a new OpenTravel format ? c) Would you be interested in transporting Type-B messages over the public internet ? d) Are you familiar with the Type-X messaging proposal from SITA and ARINC ? e) If applicable, would you be interested in adapting the Type-X messaging proposal ?
2) Payload questions
a) If applicable, do you use a proprietary payload or do you use the AIRIMP message standard by IATA ? b) Is your Type-B message payload limited to 3840 characters ? c) If applicable, do you have to break Type-B messages into multiple parts due to the payload limitations ? d) Would you be interested to have a bigger size payload e.g. 1 Meg or more.
3) Application protocol questions
a) What protocol do you use for message assurance. Examples are:
i) SLC(Synchronous Link Control or P1024B)
ii) BATAP ( Type-B application to application protection)
iii) MQ
iv) MATIP
b) Do you support SOAP client over HTTP ?
c) Do you support SOAP server over HTTP ?
4) Security questions
a) Do you encrypt your Type-B payload ? b) Do you support SSL ( secured socket layer)
5) Link protocol questions
a) If applicable, what link protocol do you use for BATAP ? e.g. X.25 , UDP/P, TCP/IP b) Do you support native IP connection via the public internet from your host system ( not workstations).
[edit] TypeX Messaging Guidance
TypeX is a protocol enhancement designed in conjunction with IATA to enable a variety of Reliable Messaging features over a variety of different underlying protocols. These capabilities are potentially useful for systems exchanging OpenTravel messages. This project would allow members of the TypeX development team to show how these capabilities can be used over SOAP.
Status: Open
Target Completion: TBD
[edit] Open Travel initial PCI study
From an OTA perspective, PCI( payment Card Industry) requires transported messages to be secured. We need to develop a specification/recommendation that allows open travel members to exchange messages in an open but still secured manner. If such specification exists, it will encourage more use of Open travel schemas for etickets and other messages involving PCI information.
This may soon become a PTP (Project Team Proposal) for a real project.
For now, we are in preliminary discussions about a project for PCI study.
John Ramos Yeo (EDS) has volunteered to spearhead the survey and initial study. A new group will be formed to do further study.
Status: Open
Target Completion: Q2 2008 for survey
Survey proposal:
Open Travel Survey for PCI Study 1) General questions
a) Do you exchange PCI related information with partners or other computers ? b) Are you already PCI compliant ? c) Are you concern about PCI messages transported using open trabel standard? d) Would you be interested in using open travel message format if it offers certain ground rules for PCI related messages?
2) Application related questions
a) If applicable, do you exchange form or payment information e.g. credit card numbers with other partners for reference purposes ? b. If applicable, do you exchange form of payment information e.g. credit card numbers with other partners for billing purposes ?
3) Security questions
a) Do you encrypt your payload ? b) Do you support SSL ( secured socket layer)
4) Link protocol questions
a) If applicable, what link protocol do you use ? e.g. X.25 , UDP/P, TCP/IP, HTTP b) Do you support native IP connection via the public internet from your host system ( not workstations).
[edit] Past Projects
Listing of previous Architecture projects with links to each project's page.
