ID:

AIXM-391

target version:

AIXM 5.2

version:

1.0

last updated:

15 JAN 2019

status:

APPROVED


Description

The data type TextNameBaseType is modified to allow also the use of lowercase characters.

Rationale for change

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

In the current model, place and feature names are constrained by the TextNameType to use only uppercase characters, numbers and some special characters. This "uppercase only" restriction was imposed in the initial AIXM versions in order to facilitate the interoperability with aviation messages exchanged over AFTN (such as NOTAM, FPL and MET messages).

For the Digital NOTAM specification it has been recently agreed to promote the use of normal "sentence case" for the text of the event description. The use of a mix of upper and lower characters for airport names, airspace names, etc. would also improve the readability of static data encoded in AIXM. This would have no negative impact on the transmission of data over AFTN because the conversion lowercase to uppercase is straightforward and unambiguous. 

Therefore, the current pattern of TextNameType should be relaxed to also allow lower case characters [a..z].

Impact assessment

[FWD_1:1] No data mapping is necessary and no data loss occurs when data is exchanged from a system (A) that uses AIXM 5.1.1 for output towards a system (B) that uses AIXM 5.2 for input.

[BWD_MAP_1:1] Data mapping is possible and no data loss occurs when data is exchanged from a system (B) that uses AIXM 5.2 for output towards a system (A) that uses AIXM 5.1.1 for input.

Change Proposal details

In the UML model:

  • Modify the TextNameBaseType as follows:
    • Remove the ‘specialisation’ association with Character3Type
    • Add a ‘specialisation’ association with Character2Type
    • Add the following pattern
      • ([A-Z]|[a-z]|[0-9]|[, !"&#$%'\(\)\*\+\-\./:;<=>\?@\[\\\]\^_\|\{\}])*

Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

Not applicable.

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

[MAPC-00] The following algorithm shall be applied:

  • For each of the following elements, replace any lowercase [a-z] character with the equivalent [A-Z] uppercase character:
    • AerialRefuelling/name
    • AeronauticalGroundLight/name
    • AirportHeliport/name
    • Airspace/name
    • Airspace/localType
    • Apron/name
    • CallsignDetail/callSign
    • City/name
    • ContactInformation/name
    • ContactInformation/title
    • DesignatedPoint/name
    • GeoBorder/name
    • GuidanceLine/name
    • HoldingAssessment/patternTemplate
    • Navaid/name
    • NavaidEquipment/name
    • ObstacleAssessmentArea/safetyRegulation
    • ObstaclePlacement/pointType
    • OnlineContact/protocol
    • OrganisationAuthority/name
    • PostalAddress/city
    • PostalAddress/administrativeArea
    • PostalAddress/postalCode
    • PostalAddress/country
    • Procedure/name
    • RadarEquipment/name
    • RadarSystem/model
    • Road/designator
    • Route/name
    • Service/name
    • SpecialDate/name
    • SpecialNavigationStation/name
    • SpecialNavigationSystem/
    • SurveyControlPoint/designator
    • Unit/name
    • VerticalStructure/name

Mapping example

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

AIXM 5.2AIXM 5.1(.1)
message:AIXMBasicMessage
  message:hasMember
    AirportHeliport
      gml:identifier = dd062d88-3e64-4a5d-bebd-89476db0812
      timeSlice
        AirportHeliportTimeSlice
          gml:validTime
            gml:TimePeriod
              gml:beginPosition = 2009-01-01T00:00:00Z
              gml:endPosition = 
          interpretation = BASELINE
          sequenceNumber = 1
          correctionNumber = 0
          featureLifetime
            gml:TimePeriod
              gml:beginPosition = 2009-01-01T00:00:00Z
              gml:endPosition = 
          designator = LDBE
          name = Belcity Balloonoprt
          locationIndicatorICAO = LDBE
          designatorIATA = 
          type = BP
          certifiedICAO = 
          controlType = CIVIL
          fieldElevation = 22 M
          fieldElevationAccuracy = 0.5 M
          magneticVariation = 2
          magneticVariationAccuracy = 1
          dateMagneticVariation = 1995
          magneticVariationChange = 0.03
          referenceTemperature = 21.0 C
          transitionAltitude = 9000 FT
          certificationDate = 
          certificationExpirationDate = 
          servedCity
            City
              name = Belcity
          ARP
            ElevatedPoint
              gml:pos = 45.4026787 18.2434140
    ...
  





message:AIXMBasicMessage
  message:hasMember
    AirportHeliport
      gml:identifier = dd062d88-3e64-4a5d-bebd-89476db0812
      timeSlice
        AirportHeliportTimeSlice
          gml:validTime
            gml:TimePeriod
              gml:beginPosition = 2009-01-01T00:00:00Z
              gml:endPosition = 
          interpretation = BASELINE
          sequenceNumber = 1
          correctionNumber = 0
          featureLifetime
            gml:TimePeriod
              gml:beginPosition = 2009-01-01T00:00:00Z
              gml:endPosition = 
          designator = LDBE
          name = BELCITY BALLOONPORT
          locationIndicatorICAO = LDBE
          designatorIATA = 
          type = OTHER:BP
          certifiedICAO = 
          controlType = CIVIL
          fieldElevation = 22 M
          fieldElevationAccuracy = 0.5 M
          magneticVariation = 2
          magneticVariationAccuracy = 1
          dateMagneticVariation = 1995
          magneticVariationChange = 0.03
          referenceTemperature = 21.0 C
          transitionAltitude = 9000 FT
          certificationDate = 
          certificationExpirationDate = 
          servedCity
            City
              name = BELCITY
          ARP
            ElevatedPoint
              gml:pos = 45.4026787 18.2434140
	...
	



  • No labels