Wow, look at all this fuss being made over the IATA NDC (New Distribution Capabilities) initiative. And I was so much looking forward to some R&R over the holidays.
Before we start, you need to know that I have not been a glowing fan of some of the IATA moves over the years, but this initiative—NDC—is one I think is rather insightful and extremely helpful not only for our airline industry but also for consumers, third-party developers, and travel agencies alike.
So let’s start to unravel the fuss with an understanding of what a schema actually is (in this case, a technical development schema) because I am pretty sure that most of the folks making all the fuss have most likely never worked with a technical schema or probably even seen one in real life. (I have attached a piece of a schema below so now they can attest to at least seeing one). A technical schema is a roadmap with very specific directions that, if you follow, will get to where you want to go–technically speaking, that is. In other words, an XSD schema file (XML Schema Definition) defines the structure of an XML message/document to include, for example, elements and attributes (child elements, order and number of elements, data types, and more).
For example, let’s say you are at the zoo and you want to go see the zebras. You will probably start out looking at a map of the zoo. If you follow the path defined for you by the map, you will undoubtedly end up seeing zebras and not those pesky hyenas by mistake. Same concept applies to a technical schema. In our case, a technology developer wants to accomplish certain tasks by connecting to an airline’s internal system to request a seat map, or retrieve a PNR, or make an exchange, etc. The schema simply provides the predictable technical pathway to accomplish the task at hand. Read the rest of this entry »