NGSI-LD¶

An ETSI information model and API for representing, querying and subscribing to context information as linked-data entities, properties and relationships.

Version: v1 · 2026-09-08 · History
Domain-specific #: 5769
Origin domain: context information systems
Subdomain: specialized structures

Core Idea¶

NGSI-LD standardizes exchange of evolving context across IoT, smart-city and digital-twin systems. Linked-data identifiers and typed relationships give shared semantics, while broker APIs support updates, federation, queries and change notifications. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

The load-bearing residual is not the broad topic of context information systems. It is An ETSI information model and API for representing, querying and subscribing to context information as linked-data entities, properties and relationships.

Scope of Application¶

NGSI-LD belongs to context information systems and is useful where the analyst can specify context entities, URIs, JSON-LD, properties, relationships, temporal or geographic metadata, broker, query and subscription interfaces, then evaluate payloads and operations conform to the declared NGSI-LD version and preserve entity and relationship semantics through JSON-LD context resolution. The scope is broad within that domain but bounded by the need for payloads and operations conform to the declared NGSI-LD version and preserve entity and relationship semantics through JSON-LD context resolution. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.

Clarity¶

The abstraction clarifies a crowded vocabulary by making payloads and operations conform to the declared NGSI-LD version and preserve entity and relationship semantics through JSON-LD context resolution the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name NGSI-LD can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.

Manages Complexity¶

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to NGSI-LD. NGSI-LD compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning¶

Identify the carrier. State what the elements, states, objects, or observations are: context entities, URIs, JSON-LD, properties, relationships, temporal or geographic metadata, broker, query and subscription interfaces. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express payloads and operations conform to the declared NGSI-LD version and preserve entity and relationship semantics through JSON-LD context resolution independently of one notation or implementation.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of context information systems because they reuse context entities, URIs, JSON-LD, properties, relationships, temporal or geographic metadata, broker, query and subscription interfaces, Linked-data identifiers and typed relationships give shared semantics, while broker APIs support updates, federation, queries and change notifications., and type the carrier, state every parameter and convention in the definition, test that payloads and operations conform to the declared NGSI-LD version and preserve entity and relationship semantics through JSON-LD context resolution, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions¶

Current abstraction NGSI-LD Domain-specific

Parents (1) — more general patterns this builds on

NGSI-LD is a kind of Representation Prime

The proposed strict upward parent is prime:representation.

Hierarchy path (1) — routes to 1 parentless root

NGSI-LD → Representation → Abstraction

Neighborhood in Abstraction Space¶

NGSI-LD sits in a moderately populated region (57^th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Messaging Protocols & Networked Services (23 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08