Airlines, ATPCO form Open AXIS Group

Six airlines formed a member-based, not-for-profit organization called Open AXIS Group to promote a standardized XML (eXtensible Markup Language) schema as the optimal electronic messaging structure for airline system connectivity used in content distribution. Members are Air Canada, American Airlines, Continental Airlines, Delta Air Lines, United Airlines and US Airways. ATPCO has been invited to serve as the founding Allied Member and former Frontier Airlines VP Jim Young will serve as executive director.

The Open AXIS Group’s mission is to expand the adoption, promotion, enhancement and maintenance of a robust airline industry-standardized XML schema that supports a range of airline transactions, including booking and PNR management, multiple passenger management, ticketing, exchange, refunds, voids, optional services, bundling and EMD management. "Having this standard provides a one-stop shop for modern airline connectivity," said American Airlines Director-Merchandising Strategy Cory Garner.

Membership is not a requirement to use the group's messaging standard; the XML schema is available to all on the group's website. "We plan on being an open, transparent and inclusive group," Young said. "The Open AXIS Group is structured to respond quickly to the fast-paced needs of the airlines."

Discuss this news 1

14 Jul03:25

As I understand most of these

By Anonymous

As I understand most of these standards do exist already as XML standards published by IATA (PADIS XML working group) for Electronic Ticketing transactions, EMD transactions. Why create yet another standards group working within the same area instead of using existing bodies where the standards are already developed and maintained ? The complexicity of data exchange and data contents is already today a complicated area as the content of the data exchange is tied into resolutions that defines the data elements to be exchanged. Work and effort should instead be put into using the existing standards development bodies to ensure compliance with the overall resolutions controlling the content of data exchange and synergy/reuse of xml schemas already developed. If there are business processes where the data exchanges is not in place, these should be requested developed through these bodies to ensure compliance with things such as data definitions, naming conventions etc. Having different standards created for same business transactions will create a hugh problem moving down the path of interoperability, interline, data exchanges, understanding of naming conventions and be a lot more costly to implement

Post new comment

The content of this field is kept private and will not be shown publicly.
ATW encourages and welcomes comments on articles that add value to the topic. Offensive and/or obscene comments will be removed.

Latest From Twitter