Update 2 files

-- we could adjust the name accordingly or make Polygon a choice of FORMATS

-- it is also worth noting that GML supports doubles instead of integers for both uncertainty, altitude and angles, should we define our defs the same way

-- This could also be REAL, but I think we avoid that for some reason

AngleDecimalDegrees ::= UTF8String

-- GMLPolygons support interior borders as well. Do we thing we need to support this?

GMLPolygon ::= SEQUENCE

    rdsubbr                             [29] UTF8String OPTIONAL

}

-- This could also be REAL, but I think we avoid that for some reason

AngleDecimalDegrees ::= UTF8String

END

    WGS84LatitudeDecimal,

    WGS84LongitudeDecimal,

    MACAddress,

    CivicAddress

    CivicAddress,

    AngleDecimalDegrees

        FROM Common-Parameters

        {itu-t(0) identified-organization(4) etsi(0) common-parameters(3280) version271(271)};

DynamicOrientation ::= SEQUENCE

{

    horizontalOrientation [1] AngleDecimalDegrees,

    verticalOrientation   [2] AngleDecimalDegrees OPTIONAL

    horizontalOrientation [1] Common-Parameters.AngleDecimalDegrees,

    verticalOrientation   [2] Common-Parameters.AngleDecimalDegrees OPTIONAL

}

-- REAL OR INTEGER?

DynamicHeading ::= SEQUENCE

{

    horizontalHeading [1] AngleDecimalDegrees,

    verticalHeading   [2] AngleDecimalDegrees

    horizontalHeading [1] Common-Parameters.AngleDecimalDegrees,

    verticalHeading   [2] Common-Parameters.AngleDecimalDegrees OPTIONAL

}

--LIProvenance ::= ENUMERATED