Stable Identity and Links

An Object ID identifies an entity or track in [R]DP. An aircraft keeps the same ID when its position or callsign changes, so each update applies to the same Object. An Action ID identifies a particular task, order, or alert throughout its lifecycle.

Build an ID from source identity

A source identifier makes a useful WDM ID when it uniquely identifies the represented entity or track. Some identifiers, such as a station’s local name, are unique only within a source system. Including that system’s name prevents two stations called station-7 from sharing an Object.

In the ADS-B example, two receivers observing aircraft A1B2C3 both use mode_s:A1B2C3. This lets [R]DP recognize one aircraft even when its observations arrive from different receivers. The receivers identify the aircraft by its ICAO address, so a new position updates the existing Object.

Example IDs

These conventions distinguish the source namespaces and keep the IDs readable:

Source identifier WDM ID What it identifies

CoT origin demo.example, UID demo-track-7

cot:demo.example:demo-track-7

The unit identified by the sender’s UID.

Vessel MMSI 367123456

mmsi:367123456

The vessel identified by this MMSI.

ICAO Mode-S address a1b2c3

mode_s:A1B2C3

The aircraft identified by this address. Six uppercase hexadecimal digits give lowercase and uppercase inputs the same ID.

Weather source demo-network, station station-7

weather:demo-network:station-7

The station’s current weather conditions. New observations update this Object.

Task source demo.example, task move-001

task:demo.example:move-001

The movement task identified by its source key.

Entity IDs and report IDs

One aircraft can produce many reports. Its Object ID stays the same as the report identifiers change. identities holds the aircraft’s source identifiers, provenance.id identifies the source report or assertion, and externalRefs[].externalId identifies the source record or entity in the retained payload. These fields preserve source identifiers without making every report a new aircraft Object.

The same distinction applies when one message contains several tracks. Each track has its own Object ID based on its source key; its source reference connects it to the message and the item within it. An array index would change the track’s ID if the message reordered its items.

A link refers to the related record’s WDM ID. For example, an Action can identify an aircraft as its assigned asset through objectLinks, allowing clients to retrieve the aircraft’s current position without copying it into the Action.

Objects use relationships to link to other Objects; Actions use links for other Actions and objectLinks for Objects. Each link has a direction, and WDM does not automatically create its reverse.

See Action and Objects for a complete example, and Map External Data to WDM for field mapping and expiry.