This is a public repository for managing work around the OAI Travel Working Group, providing a single place to manage artifacts, discussions, projects, and other aspects of using the OpenAPI specification as part of the travel industry.
The working group is currently made up of the following individual, and feel free to submit issue requested to be added.
- Kin Lane (Chief Evangelist at Postman)
- Brian Bell (President & CEO at LinksRez)
- Stu Waldron (Travel Consultant)
- Luis Weir (Senior Director at Oracle Hospitality)
- Keith Helsop (Delta, Digital Transformation and Technology Innovation Leader)
- Jeff ErnstFriedman (Executive Director at OpenTravel Alliance)
- Sandy Angel (Senior Director, Technology & Information at American Hotel & Lodging Association)
- Steve Livezey (Chief Technology Officer for ID90 Travel)
- Steve Fohl (Product Manager at LinksRez)
- Refael Botbol Weiss (UP9 Co-founder & VP of Customer Experience)
The Travel SIG will compile and present a collective representation of the API behaviors required by the travel industry documented in the form of use cases and workflows. This effort will include working with various established travel standards and trade association bodies using the Open Travel Alliance as a coordination point. Open Travel will moderate the various needs of sectors such as (but not limited to) air, hotel, car, cruise, rail, tours, distribution channels, etc. with a focus on enabling interoperability across the sectors. The standards bodies and trade associations will lead on what functionality is needed by their members. The Travel SIG will work with other OAI SIGs on how best to support the documented use cases and workflows. The intent here is to avoid duplication of SIG efforts and have the Travel SIG focus on what is needed and work with other SIGs on how to meet that need.
This working group is just getting started, but feel free to get involved via one of these channels:
- Weekly Call - Weekly call Friday 8:00 AM to 8:30 AM PDT.
- Discussions - Use the Github discussions to ask questions and engage in discussion with the community.
- Slack - Email [email protected] and we'll get you added to the Slack channel for the group.
- Issues - Feel free to submit a Github issue with any question or comment about the working group.
- Projects - Keep up to speed on the various projects occurring via Github projects for this group.