Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

ID:

AIXM-483

target version:

AIXM 5.2

version:

1.0

last updated:

25 FEB 2021

status:

PROPOSED


Description

Change name of class AirTrafficManagementService into AirTrafficFlowManagementService.

Rationale for change

See https://aixmccb.atlassian.net/browse/AIXM-237

The definition of class AirTrafficManagementService is: "A kind of service that provides flight planning and flow management operations." This definition is in accordance to how this class appears in the model and with the list of values of its "type" attribute.

However, the name of the class is misleading since "Air Traffic Management" is a general term, that includes air navigation, air traffic control, etc.

The name "AirTrafficFlowManagementService" would better match the list of values for its type and its definition, as shown at the right.

Impact assessment

When receiving data from AIXM 5.2 implementations, current AIXM 5.1(.1) systems will have to convert the data by applying the mapping guidance proposed further.

When receiving data from AIXM 5.1(.1) implementations, AIXM 5.2 systems will have to convert the data by applying the mapping guidance proposed further.




Change Proposal details

In the UML model:

  • Rename class AirTrafficManagementService into AirTrafficFlowManagementService.

Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

The following algorithm shall be applied:

  • [MAPC-00] Each record named AirTrafficManagementService is converted into AirTrafficFlowManagementService

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

The following algorithm shall be applied:

  • [MAPC-00] Each record named AirTrafficFlowManagementService is converted to AirTrafficManagementService

Mapping example

(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-xxx

AIXM 5.2AIXM 5.1(.1)







  • No labels