Public:2009A Projects
From wiki.opentravel.org
Contents |
[edit] Active Projects
|
Team Pages: Content Distribution | Data Dictionary | Mobile Devices | Vehicle Booking Notification | Dynamic Package Enhancements |
[edit] Architecture
[edit] Creating An OpenTravel Data Dictionary
There are limitless ways implementers could (and have) extended and reused OpenTravel schemas. An OpenTravel Data Dictionary would facilitate greater and easier adoption:
1) By harmonizing the specifications by resolving conflicting definitions.
2) By sanitizing evolutionary dead ends in the design of messages that are either no longer useful or were never developed fully.
3) Creating reusable components that can be consumed by a RESTful framework.
4) Creating reusable components that can be deployed in other OpenTravel messages.
5) Blending specifications across multiple platforms in new (internal) messages.
6) Develop a ‘more’ tool friendly specification.
A Data Dictionary should also make it easier for the work groups:
1) To produce new messages as it should be easier to identify and reuse existing components in new ways.
2) To support the existing messages because they will be much simpler and changes will be applied consistently.
The existing message based content represents a tremendous amount of work that would be foolish for implementers to ignore, the Data Dictionary represents a logical spin off of that work.
To create a data dictionary it will be necessary to deconstruct the message set into its component parts, harmonize the definitions of competing components and rebuild the subsequent messages.
[edit] Guidelines for Mobile Integration
View the Study: Mobile Integration Recommendation
Harnessing the opportunity of the mobile web means different things to different people. This document seeks to categorise the practical opportunities, highlights the major differences between fixed line and mobile and recommends methods to integrate existing systems. This will not be limited to mobile internet, and may include SMS, etc. Work will be mindful of mobile carrier requirements and their recommendations. The project should include the following:
- Defining the practical opportunities today
- Transactional
- Browse
- Check availability and rates
- Reserve
- Call to book
- Secure transactions
- Added value services
- Travel ‘concierge’
- Mobile check in
- Retail coupons
- Transactional
- Highlight the differences between fixed and mobile internet
- Environment
- Device
- Connectivity
- User costs
- Environment
- Integration of existing systems
- Considerations
- Options
- Web Services/API’s
[edit] Namespace Usage In OpenTravel Schemas
Namespaces serve a basic function in XML; they allow users to unambiguously determine the meaning of an XML element (or attribute) when more than one with the same name may exist. This is very important when schemas from multiple sources are brought together which would otherwise require that one or other schema change to resolve the conflict. E.g. the SOAP layer has an Address element which would conflict with the equivalent Address element in the OpenTravel specifications.
The outcome of this philosophy is 2 practices.
1) Segregation of Data: between different specifications that use common terminology but with different definitions.
2) Separation of Versions: between different releases of the same specification that may have to co-exist.
The use of namespaces within the OpenTravel Schemas presents significant challenges since neither approach has been adopted.
The study will be limited to identifying the various common practices in the industry, what trends may be emerging or have emerged since the introduction of namespaces in the OpenTravel messages. The opportunity will be taken to review the history of the namespace policy in the OpenTravel Alliance and working through the implications of all the alternative options on the consumers, providers and integrators within the travel industry.
[edit] PCI-PII And Remediation Study
The Payment Card Industry (PCI) is on a mission to force owners of systems that process or store payment card information to tighten their security to prevent the theft and/or misuse of customer payment card information, especially after a major breach such as the TJX incident. The PCI has established a set of very specific and stringent requirements for the data security standards (DSS) which are being used by the major card brands as the basis for the assessment and certification of PCI compliance.
Likewise, governments are beginning to recognize the importance of protecting personal information and are considering legislation that requires the protection of PII.
Lastly, personal information that is not strictly PII, but that does have monetary value and can be exploited, such as loyalty membership information, will also be included within the scope of this study.
Messages based on Open Travel schemas can contain both types of information. The purpose of this study will be to determine the extent of usage of PCI data and PII, and make recommendations regarding protection, remediation, and best practices. Although out of scope of this study, end point storage of sensitive data either by design, as in database storage, or inadvertently, as in server message logs, is an important issue. This study will make note any best practices regarding such storage.
[edit] Transport
[edit] Booking Notification for Car Rental
[edit] Travel Integration
[edit] Dynamic Package Enhancements (Travel Integration WG)
[edit] Projects on Hold
Content Distribution:
Insurance Replacement Fields for Car Rental:
Opt-In/Opt-Out for Air:
[edit] Archives
To view our past projects, please visit our Public:Projects Archive.
