1     Definition 2     Functional Requirements 3     Syntax
4     Semantics 5    Conformance Testing 6     Performance Assessment

1      Definition

The sequence of start and end Spatial Attitudes SA (SA1, SA2,…, SAi) and corresponding Times t (t1, t2, tj) expected and actual of a series of segments.

2      Functional Requirements

A Trajectory is composed of Segments. Each Segment is described by the expected and actual start and end Spatial Attitudes and Times.

3      Syntax

https://schemas.mpai.community/OSD/V1.3/data/Trajectory.json

4      Semantics

Label Size Description
Header N1 Bytes Trajectory Header
– Standard-Trajectory 9 Bytes The characters “CAV-TRJ-V”
– Version N2 Bytes Major version – 1 or 2 Bytes
– Dot-separator 1 Byte The character “.”
– Subversion N3 Bytes Minor version – 1 or 2 Bytes
TrajectoryID N4 Bytes Identifier of Trajectory.
TrajectoryData[] N5Bytes Data in the Trajectory
– SpaceTime N6 Bytes Expected and/or actual Spatial Attitude and Time of a Trajectory segment.
DescrMetadata N7 Bytes Descriptive Metadata

5     Conformance Testing

A Data instance Conforms with Trajectory (OSD-TRJ) V1.3 if:

  1. The Data validates against the Trajectory ’s JSON Schema.
  2. All Data in the  Trajectory ’s JSON Schema
    1. Have the specified type
    2. Validate against JSON Schemas.
    3. Conform with their Data Qualifiers if present.

6     Performance Assessment