1 Definition
The sequence of Spatial Attitudes SA (SA1, SA2,…, SAi) and corresponding Times t (t1, t2, tj) planned to reach a Goal.
2 Functional Requirements
A Trajectory is composed of Segments. The Segment is described by the starting Spatial Attitude which is known and the starting time which is given and the destination of which Spatial Attitude and Time are given.
3 Syntax
https://schemas.mpai.community/OSD/V1.1/data/Trajectory.json
4 Semantics
| Label | Size | Description |
| Header | N1 Bytes | |
| – Standard | 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 | 2 Bytes | Data in the Trajectory |
| – StartSA | N5 Bytes | Spatial Attitude at StartTime |
| – EndSA | N6 Bytes | Spatial Attitude at EndTime |
| – Duration | 17 Bytes | Expected Duration of Trajectory from start to destination. |
| DescrMetadata | N8 Bytes | Descriptive Metadata |
5 Formats and Attributes
No formats required.
6 To Respondents
Respondents are requested to formulate functional requirements of Trajectory.
