schema: add MCM JSON schema v2.0.0

[raphael-ram]

Summary

Add the MCM (Manoeuvre Coordination Message) JSON Schema v2.0.0, based on ETSI TS 103 561 v1.1.

Close #512

Changes

• Add schema/mcm/mcm_schema_2-0-0.json

• trajectory is an array (SEQUENCE (SIZE(1..10)) OF WayPoint), items reference $ref: #/$defs/way_point

• way_point is a SEQUENCE with way_point_type, longitude, latitude, speed (required), altitude, heading (optional)

• longitude and latitude in way_point reference $ref: #/$defs/longitude_value and $ref: #/$defs/latitude_value

• altitude in way_point references $ref: #/$defs/altitude_value (integer, ETSI WGS84 bounds)

• altitude in reference_position references $ref: #/$defs/altitude (object with altitude_value + altitude_confidence, based on ETSI-ITS-CDD Altitude)

• latitude_value, longitude_value, altitude_value are standalone integer $defs with ETSI WGS84 bounds (renamed from latitude_position, longitude_position, altitude_position per reviewer comments)

• reference_position uses $ref for latitude, longitude, altitude and position_confidence_ellipse

• kinematics_characteristics is an empty object { "type": "object", "properties": {}, "additionalProperties": false }, referenced via $ref in both advised_trr_container and sub-manoeuvres container

[mathieu1fb]

I think that the overall structure of the schema if good. Some arrays should point to the objects that they contain, and some extra definitions have to be found for the "null" objects.

For instance, ASN.1 definitions of the MCM don't seem to be complete:

Trajectory::= SEQUENCE {
    wayPointType WayPointType,
    wayPoints SEQUENCE (SIZE (1..10)) OF WayPoint, -- Including starting way point and ending way point
    longitudePositions SEQUENCE (SIZE (1..10)) OF LongitudePosition,
    latitudePositions SEQUENCE (SIZE (1..10)) OF LatitudePosition,
    altitudePositions SEQUENCE (SIZE (1..10)) OF AltitudePosition OPTIONAL,
    headings SEQUENCE (SIZE (1..11)) OF Wgs84Angle OPTIONAL,
    speed INTEGER (0..511) -- in meters per second
}
 
WayPointType ::= ENUMERATED {
    startingWayPoint (0),
    intermediateWayPoint (1),
    endingWayPoint (2)
}
 
LongitudePosition ::= NULL
 
LatitudePosition ::= NULL
 
AltitudePosition ::= NULL
 
WayPoint ::= NULL

@nbuffon @ymorin-orange @tigroo31 any ideas?

[mathieu1fb]

I think that the overall structure of the schema if good. Some arrays should point to the objects that they contain, and some extra definitions have to be found for the "null" objects.

For instance, ASN.1 definitions of the MCM don't seem to be complete:

Trajectory::= SEQUENCE {
    wayPointType WayPointType,
    wayPoints SEQUENCE (SIZE (1..10)) OF WayPoint, -- Including starting way point and ending way point
    longitudePositions SEQUENCE (SIZE (1..10)) OF LongitudePosition,
    latitudePositions SEQUENCE (SIZE (1..10)) OF LatitudePosition,
    altitudePositions SEQUENCE (SIZE (1..10)) OF AltitudePosition OPTIONAL,
    headings SEQUENCE (SIZE (1..11)) OF Wgs84Angle OPTIONAL,
    speed INTEGER (0..511) -- in meters per second
}
 
WayPointType ::= ENUMERATED {
    startingWayPoint (0),
    intermediateWayPoint (1),
    endingWayPoint (2)
}
 
LongitudePosition ::= NULL
 
LatitudePosition ::= NULL
 
AltitudePosition ::= NULL
 
WayPoint ::= NULL

@nbuffon @ymorin-orange @tigroo31 any ideas?

Resolved in #512

[mathieu1fb]

Looks all good to me now, thanks @raphael-ram. Let's now wait for a review of @nbuffon, @tigroo31 or @ymorin-orange before merging.

[raphael-ram]

Ok. I've just made another commit to formalize the required fields of way_point because this doesn't respect the initial format of other's required fields.

[ymorin-orange]

Question to adress with @nbuffon (for the same question in the CAM): should the message_format be part of the required list?

[nbuffon]

Comments from Frédéric review

Review was re-done by @nbuffon as there is an issue with @tigroo's GitHub account.

[mathieu1fb]

Thanks @raphael-ram for all the work, we can now approve this first version of the MCM JSON schema!