The service description is a work in progress, and without version control, as long as this note is here.

Service facts

• Name: AirportSlotDataService

• Operations, see Service operations 

• Operations are accessed using GET or POST, as specified per operation.
• Service security: Decided by implementation

• Standard return codes are described here: Service error response

Introduction

Overview

This service description defines one service with a set of operations designed to support integration between airports and BRS (Baggage Reconciliation System). At the bag level this service extend the functionality defined in Bag Event Notification Service, and add functionality for reporting batch oriented events. A "batch" in this regard is a set of bags treated as one "unit" and delivered at some location without any other bags being delivered to the same location. The service is designed to be implemented by both the relevant airport and the BRS provider.create and update airport slots. The service is airport oriented as the slot allocation is by it's nature airport oriented. The airport implements this service and the slot coordinator uses it. 

A set of use cases are described here: Avinor use cases

Implementation considerations

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

It is however up to the service provider which data elements to support.

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

• • the address of the service.
  • any limitations in the implementation.

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 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 operations

Data entities

Avinor use cases

XSDs