| 1 Definition | 2 Functional Requirements | 3 Syntax |
| 4 Semantics | 5 Conformance Testing | 6 Performance Assessment |
1 Definition
2 Functional Requirements
Temporal Cue specifies the nature of the cue (absolute, relative, keyword-based, or range) and provides the necessary details to resolve the intended time reference.
3 Syntax
https://schemas.mpai.community/OSD/V1.5/data/TemporalCue.json
4 Semantics
Table 1 provides the semantics of the components of Temporal Cue.
Table 1 – Semantics of Temporal Cue
| Label | Description |
|---|---|
| Header | Temporal Cue Header |
| – Standard-TemporalCue | The characters “OSD-TCU-V” |
| – Version | Major version – 1 or 2 characters |
| – Dot-separator | The character “.” |
| – Subversion | Minor version – 1 or 2 characters |
| MInstanceID | Identifier of the Virtual Space (M-Instance) to which the Temporal Cue applies. |
| TemporalCueID | Unique identifier of this Temporal Cue instance. |
| CueType | Nature of the temporal cue: – absolute: Fixed point in time.– relative: Time offset from now.– keyword: Semantic keyword (e.g., morning).– range: Interval between two times. |
| SimpleTimeRef | Reference to a SimpleTime structure for absolute or range cues. |
| RelativeExpression | Relative time expression (e.g., +2h, in 3 days). Pattern: ^(\+\d+[smhd] |
| Keyword | Keyword-based cue:morning, afternoon, evening, night, immediate, scheduled. |
| Confidence | Confidence level (0–1) in interpreting the temporal cue. |
| DescrMetadata | Optional descriptive metadata for the Temporal Cue instance. |
5 Conformance Testing
A Data instance Conforms with MPAI-OSD Temporal Cue V1.5 (OSD-TCU) if:
- Its JSON Object validates against its JSON Schema.
- Any included JSON Object validates against its JSON Schema.
- All Data in the JSON Object:
- Have the specified Data Types.
- Conform with the Qualifiers signaled in their JSON Schemas.