UNIVIP Specification 0.2.0-draftLink to the section UNIVIP Specification 0.2.0-draft
On this page
This directory contains the normative specification, split by topic. Each part states its own maturity level. Machine-readable artifacts in ../schemas/ and ../api/ are normative where this text says so; where prose and schema disagree, the schema is authoritative for wire format and the prose is authoritative for behavior, and the disagreement is a defect to be fixed.
| Part | Title | Profiles | Maturity |
|---|---|---|---|
| 01 | Scope, conformance language and versioning | all | Draft |
| 02 | Terminology | all | Draft |
| 03 | Architecture, deployment modes and transport baseline | all | Draft |
| 04 | Profiles S, C and N | all | Draft |
| 05 | Identity, discovery, onboarding and the session channel | all | Draft |
| 06 | Capability document | all | Draft |
| 07 | Telemetry data model | S | Draft |
| 08 | Events and the event catalog | S | Draft |
| 09 | Media streaming and synchronized metadata | S | Draft |
| 10 | Camera and payload control | C | Draft |
| 11 | Vehicle control, control leases and safety | N | Draft |
| 12 | Geospatial extension | optional | Draft |
| 13 | Security | all | Draft |
| 14 | Conformance testing | all | Draft |
| A | Annex A: Mappings to ONVIF, MAVLink, MISB ST 0601 and the DJI Cloud API | informative | Draft |
Changes in 0.2Link to the section Changes in 0.2
Version 0.2.0-draft resolves the implementation findings recorded while building the reference gateway, the .NET client SDK and the .NET gateway port (../docs/implementation-findings.md; each resolved row names its resolution). Messages valid under 0.1 remain valid under the 0.2 schemas. A device that declares 0.2 and does not host its REST surface must answer request envelopes (transports.rest.session_proxy), because 0.1 gave clients no way to reach it. The full list is in ../CHANGELOG.md.
Reading orderLink to the section Reading order
Implementers of a device or gateway: 01 → 03 → 05 → 06 → 07 → 08 → 09, then 10 and 11 as needed, then 13 and 14.
Implementers of a VMS or other client: 01 → 03 → 05 → 06 → 09 → 07 → 08, then 10, 12, 13, 14.