Fixed RDF and JSON-LD references

Implementations support the NGSI-LD Meta-model as follows:

- An **NGSI-LD Entity** is a subclass of rdfs:Resource [i.16].

- An **NGSI-LD Relationship** is a subclass of rdfs:Resource [i.16].

- An **NGSI-LD Property** is a subclass of rdfs:Resource [i.16].

- An **NGSI-LD Entity** is a subclass of rdfs:Resource [i.11].

- An **NGSI-LD Relationship** is a subclass of rdfs:Resource [i.11].

- An **NGSI-LD Property** is a subclass of rdfs:Resource [i.11].

- An **NGSI-LD Value** is either a rdfs:Literal or a node object (in JSON-LD

  syntax) to represent complex data structures [i.16].

  syntax) to represent complex data structures [i.11].

- An **NGSI-LD Property** has a **value,** stated through _`hasValue`_, which is

  of type rdf:Property [i.16].

  of type rdf:Property [i.11].

- An **NGSI-LD Relationship** has an **object** stated through _`hasObject`_

  which is of type rdf:Property [i.16].

  which is of type rdf:Property [i.11].

### 4.2.3 Cross-domain ontology

  hierarchical structure as defined in Clause+++clause-5+++root.2.7.

- **LanguageMaps:** Are a special type of NGSI-LD Value intended to convey the

  different values of Language Properties, stated through an _`hasLanguageMap`_,

  which is of type rdf:Property [i.16] and is itself a subproperty of

  which is of type rdf:Property [i.11] and is itself a subproperty of

  _`hasValue`_.

- **Geometry Values:** Are a special type of NGSI-LD Value intended to convey

  geometries corresponding to geospatial properties as defined in

This clause is intended to show how the NGSI-LD information model could be

described using UML diagrams. The aim of this diagram is to help those readers

less familiar with ontology representations or RDF [i.16] to understand the

less familiar with ontology representations or RDF [i.11] to understand the

NGSI-LD Information Model.

In Figure+++below NGSI-LD Entity, Relationship, Property and Value are

#### 4.3.4.1 Introduction

NGSI-LD serialization is based on JSON-LD [i.11], a JSON-based format for

NGSI-LD serialization is based on JSON-LD [i.12], a JSON-based format for

serializing Linked Data and a representation of RDF. The _`@context`_ in JSON-LD

is used to expand terms, provided as short-hand strings, to concepts, specified

as URIs, and vice versa, to compact URIs into terms. The motivation is to have,

request, not any previously used user _`@context`_.

The term to URI expansion or compaction is performed using an _`@context`_ as

described by the JSON-LD specification [i.11], section 5.1.

described by the JSON-LD specification [i.12], section 5.1.

<!-- prettier-ignore-start -->

considered implicitly present when processing or generating context information.

Furthermore, the Core _`@context`_ is protected and remainsD immutable and

invariant during expansion or compaction of terms. Therefore, and as per the

JSON-LD processing rules [i.11], when processing NGSI-LD content,

JSON-LD processing rules [i.12], when processing NGSI-LD content,

implementations are to consider the core _`@context`_ as if it were in the

**last** position of the _`@context`_ array. Nonetheless, for the sake of

compatibility and cleanness, data providers are expected to generate JSON-LD