Context data objects may contain equivalent key-value pairs for identifying and looking up context types, with optional identifiers to support various applications, though some types may require at least one identifier.

Context data objects may include a "name" property for additional information or display, with some derived types making it mandatory based on the use case.

Required field in the FDC3 context data schema, essential for routing context data and for intent discovery within the FDC3 ecosystem.