Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

Until this note is removed the documentation is a work in progress, and revisions to the documentation will not be tracked.

 

Namespace: http://www.asrv.aero/webservices/1.0/

...

IataFlightLegMsgSubmit

 

Document revisions

Date

Description

Author

yyyy-mm-dd First complete version of the documentation

...

Table of Content Zone
maxLevel2
locationtop

 

 

Numbered Headings

Introduction

Overview

This service description defines one service with a set of operations to set flight oriented data. All flight related data elements are defined by the ADD.

The service is primarily designed to meet the need of airport partners, but availability is the decision of the service provider.

There is one operation for each of the IATA telex type flight leg messages (MVT, LDM, DIV, +++). While the data is defined using the ADD the structure of the data closely matches the structure of the IATA messages. Mapping of IATA telex type data to ADD elements is more closely described here: ADDMIFTM

All normal use of the IATA messages should be covered by the service.

Implementation considerations

Any implementation of this service MUST use the WSDL and XSD files provided here: WSDL and XSDs

It is however up to the service provider to decide which data elements to actually update. And as clients vary wildly in their capabilities most elements are optional

Any service provider should make available documentation about the actual implementation, including:

    • the address of the service.
    • any limitations in the implementation.
    • any limitations on how often a client can use the service.

Purpose of this service description

This service description has the following purpose:

      • Describe of service in enough detail for a service provider to implement it.
      • Describe the service so that a client (of this service) developer can use it.
      • Make available the WSDL and XSD files necessary to implement and use the service.
      • Make it possible for relevant people at airports, airlines, handlers and other aviation partners to understand the available functionality and then to decide if to implement/use it or not.

Intended readership

    • IT architects
    • Developers
    • Business architects
    • Interested parties in the aviation community

Service overview

The figure below shows the available operations on the FlightDataSetService IataFlightLegMsgSubmit service. The operations are described in detail in Service operations.

The operations can set the following types of data:

  • Identification data
  • Arriving flights
  • Departing flights
  • Turnarounds (arriving and departing flights connected)
  • Flight leg (departure and arrival)

    . There is one operation for each of the IATA telex type flight leg oriented messages. The data for each operation closely matches the data in the corresponding IATA message, but all elements are defined using ADD terms.

    Service operations

    Include Page
    Service operations
    Service operations

    Data entities

    Include Page
    Data entities
    Data entities

    XML Usage

    Include Page
    FDSCP:XML Usage
    FDSCP:XML Usage

    WSDL and XSDs

    Include Page
    WSDL and XSDs
    WSDL and XSDs

    Examples

    Include Page
    Examples
    Examples


    ...