Correct definition of normalized temporal

The temporal evolution of an _Attribute_ (for instance, its historical evolution

or future predictions) is composed of the sequence of instances of the referred

during a period of time within its lifetime.

_Attribute_ during a period of time within its lifetime.

The temporal representation of an _Attribute_ shall be provided as an Array of

JSON-LD objects (or a single JSON-LD object in case only one is present), each

one representing an instance of the Attribute (as mandated by

one representing an instance of the _Attribute_ (as mandated by

Clause+++root.2.6.4) at a particular point in time, which is recorded as a

Temporal Property of the instance (typically _`observedAt`_). See example in

Annex A, Clause+++annex-a+++A.6. In case the _Attribute_ is deleted, an instance

of the _Property_ is recorded with its _value_ set to the URI

["urn:ngsi-ld:null"]{.HTML-Code} and the _`deletedAt`_ Temporal Property set.

Systems should maintain an _instanceId_ for each such _Property_ instance.

Systems should maintain an _`instanceId`_ for each such _Attribute_ instance.

Without such an _`instanceId`_, it is not possible to selectively modify or

delete temporal information via the NGSI-LD API. The consequences of this may be

severe in the case of modification or deletion requests for legal reasons, e.g.

**Mandatory**

For Each _Attribute_, one of the following members shall be present:

Within the Array of JSON-LD objects holding each instance of an _Attribute_,

one of the following members shall be present:

- ["values"]{.HTML-Code} indicating the temporal evolution of a _Property_ -

  further members shall follow the data type described in Clause+++root.2.6.4.3

- ["objects"]{.HTML-Code} indicating the temporal evolution of a

  _Relationship_ - further members shall follow the data type described in

  Clause+++root.2.6.4.4

- ["values"]{.HTML-Code} indicating the temporal evolution of a _GeoProperty_ -

  further members shall follow the data type described in Clause+++root.2.6.4.5

- ["languageMaps"]{.HTML-Code} indicating the temporal evolution of a

  _LanguageProperty_ Attribute - further members shall follow the data type

  described in Clause+++root.2.6.4.6

- ["vocabs"]{.HTML-Code} indicating the temporal evolution of a

  _VocabProperty_ - further members shall follow the data type described in

  Clause+++root.2.6.4.7

- ["valueLists"]{.HTML-Code} indicating the temporal evolution of a

  _ListProperty_ - further members shall follow the data type described in

  Clause+++root.2.6.4.8

- ["objectLists"]{.HTML-Code} indicating the temporal evolution of a

  _ListRelationship_ Attribute - further members shall follow the data type

  described in Clause+++root.2.6.4.9

- ["jsons"]{.HTML-Code} indicating the temporal evolution of a _JsonProperty_ -

  further members

- shall follow the data type described in Clause+++root.2.6.4.10

- ["value"]{.HTML-Code} indicating a _Property_ - further members shall follow

  the data type described in Clause+++root.2.6.4.3

- ["object"]{.HTML-Code} indicating a _Relationship_ - further members shall

  follow the data type described in Clause+++root.2.6.4.4

- ["value"]{.HTML-Code} indicating a _GeoProperty_ - further members shall

  follow the data type described in Clause+++root.2.6.4.5

- ["languageMap"]{.HTML-Code} indicating a _LanguageProperty_ - further members

  shall follow the data type described in Clause+++root.2.6.4.6

- ["vocab"]{.HTML-Code} indicating a _VocabProperty_ - further members shall

  follow the data type described in Clause+++root.2.6.4.7

- ["valueList"]{.HTML-Code} indicating a _ListProperty_ - further members shall

  follow the data type described in Clause+++root.2.6.4.8

- ["objectList"]{.HTML-Code} indicating a _ListRelationship_ - further members

  shall follow the data type described in Clause+++root.2.6.4.9

- ["json"]{.HTML-Code} indicating a _JsonProperty_ - further members shall

  follow the data type described in Clause+++root.2.6.4.10

On an _Attribute_, the following member is also mandatory, aligning with the

data type described above:

Aligning with the data type described above, on each instance of an _Attribute_,

the following member is also mandatory:

- ["type"]{.HTML-Code}: a fixed value describing the Attribute data type, one of

  the following values:

  - ["Property"]{.HTML-Code}, ["Relationship"]{.HTML-Code},

    ["GeoProperty"]{.HTML-Code}, ["LanguageProperty"]{.HTML-Code},

    ["VocabProperty"]{.HTML-Code}, ["ListProperty"]{.HTML-Code},

    ["Relationship"]{.HTML-Code}, ["JsonProperty"]{.HTML-Code}

    ["ListRelationship"]{.HTML-Code}, ["JsonProperty"]{.HTML-Code}

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

    "type": "Property",

    "value": 120,

    "unitCode": "KMH",

    "observedAt": "2018-08-01T12:03:00Z"

    "observedAt": "2018-08-01T12:03:00Z",

    "instanceId": "urn:ngsi-ld:instance:14141732",

  },

  {

    "type": "Property",

    "value": 80,

    "unitCode": "KMH",

    "observedAt": "2018-08-01T12:05:00Z"

    "observedAt": "2018-08-01T12:05:00Z",

    "instanceId": "urn:ngsi-ld:instance:2236646",

  }

]

```

- ["@context"]{.HTML-Code}, a JSON-LD _`context`_ as described in

  Clause+++root.3.2.1.

For Each _Attribute_, one of the following members shall be present:

- For each _Property_, a member whose key is the Property name (a term), the

  member value shall be a JSON-LD object labelled with the type

  ["Property"]{.HTML-Code}. Such JSON-LD object shall only contain a member

<!-- prettier-ignore-end -->

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

>>> [!tip]