run prettier

# Annex [(informative)]{.inform}: Bibliography

-

##### C.2.2.1.3 Normalized representation when flattened Linked Entity retrieval is used

When flattened [Linked Entity]{.HTML-Keyboard} retrieval (see clause 7.7.3)

is specified, an array of normalized Entities is returned. Whenever a

When flattened [Linked Entity]{.HTML-Keyboard} retrieval (see clause 7.7.3) is

specified, an array of normalized Entities is returned. Whenever a

_Relationship_ Attribute targets an Entity stored locally or includes an

_`objectType`_, an additional normalized [Linked Entity]{.HTML-Keyboard} holding

data corresponding to the _Relationship's_ target _`object`_ URI is appended to

##### C.2.2.2.3 Concise representation when flattened Linked Entity retrieval is used

When flattened [Linked Entity]{.HTML-Keyboard} retrieval (see clause 7.7.3)

is specified, an array of concise Entities is returned. Whenever a

_Relationship_ Attribute targets an Entity stored locally or includes an

_`objectType`_, an additional concise [Linked Entity]{.HTML-Keyboard} holding

data corresponding to the _Relationship's_ target _`object`_ URI is appended to

the response. For Attributes of type ["ListRelationship"]{.HTML-Code}, an array

of concise [Linked Entities]{.HTML-Keyboard} is appended to the response which

hold the data corresponding to each of the target URIs found within its

_`objectList`_.

When flattened [Linked Entity]{.HTML-Keyboard} retrieval (see clause 7.7.3) is

specified, an array of concise Entities is returned. Whenever a _Relationship_

Attribute targets an Entity stored locally or includes an _`objectType`_, an

additional concise [Linked Entity]{.HTML-Keyboard} holding data corresponding to

the _Relationship's_ target _`object`_ URI is appended to the response. For

Attributes of type ["ListRelationship"]{.HTML-Code}, an array of concise [Linked

Entities]{.HTML-Keyboard} is appended to the response which hold the data

corresponding to each of the target URIs found within its _`objectList`_.

```json

[

##### C.2.2.3.3 Simplified representation when flattened Linked Entity retrieval is used

When flattened [Linked Entity]{.HTML-Keyboard} retrieval (see clause 7.7.3)

is specified, an array of JSON Objects is returned. Whenever a _Relationship_

When flattened [Linked Entity]{.HTML-Keyboard} retrieval (see clause 7.7.3) is

specified, an array of JSON Objects is returned. Whenever a _Relationship_

Attribute targets an Entity stored locally or includes an _`objectType`_, an

additional JSON Object of key-value pairs holding data corresponding to the

_Relationship's_ target _`object`_ URI is appended to the response. For

  - N is an Entity instance of type **T** or types **Ts**. Type name is "AliasT"

    or there is an Array of Type names ["AliasT1", ...,"AliasTn"], N's

    identifier is **I**.

  - N has 0 or more associated _Property_. Each

    _Property_ (**Psi**) is defined as follows:

  - N has 0 or more associated _Property_. Each _Property_ (**Psi**) is defined

    as follows:

    - _Property_ type identifier is **Pi**.

    - _Property_ name is "AliasPi".

    - _Property_ Value is **Vi**.

    - _Property_ Value's associated data type is **Di**.

  - N is the subject of 0 or more  _Relationship_. Each

     _Relationship_ is defined as follows:

  - N is the subject of 0 or more _Relationship_. Each _Relationship_ is defined

    as follows:

    - _Relationship_ type identifier is **Ri**.

    - _Relationship_ name is "AliasRi".

    - _Relationship_ target object identifier is **Robji**.

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

3.  For each _Property_ Psi (Pi, "AliasP", Vi, Di) associated

    to N:

3.  For each _Property_ Psi (Pi, "AliasP", Vi, Di) associated to N:

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

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

4.  For each  _Relationship_ Rs (Ri, AliasRi, Robji) associated

    to N:

4.  For each _Relationship_ Rs (Ri, AliasRi, Robji) associated to N:

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

## D.3 Algorithm for transforming an NGSI-LD Property into JSON-LD (ALG1.1)

Let **Ps** be the _Property_ that has to be transformed. It is

defined by (P, "AliasP", V, D), where **P** denotes a

_Property_ Type Id, "**AliasP**" is the

_Property_ name, **V** is the _Property_

Value and **D** is the _Property_ Value's data type.

Let **Ps** be the _Property_ that has to be transformed. It is defined by (P,

"AliasP", V, D), where **P** denotes a _Property_ Type Id, "**AliasP**" is the

_Property_ name, **V** is the _Property_ Value and **D** is the _Property_

Value's data type.

Ps might be associated to extra _Properties_ or

_Relationships_.

Ps might be associated to extra _Properties_ or _Relationships_.

Let O be the output JSON-LD object and C the associated JSON-LD context:

## D.4 Algorithm for transforming an NGSI-LD Relationship into JSON-LD (ALG1.2)

Let **Rs** be the  _Relationship_ that has to be transformed.

It is defined by (R, "AliasR", Robj), where **R** denotes a

 _Relationship_ Type Id, "**AliasR**" is the

 _Relationship_'s name and **Robj** is the identifier of the

target object of the  _Relationship_.

Let **Rs** be the _Relationship_ that has to be transformed. It is defined by

(R, "AliasR", Robj), where **R** denotes a _Relationship_ Type Id, "**AliasR**"

is the _Relationship_'s name and **Robj** is the identifier of the target object

of the _Relationship_.

Rs might be associated to extra _Properties_ or

_Relationships_.

Rs might be associated to extra _Properties_ or _Relationships_.

Let O be the output JSON-LD object and C the current JSON-LD context:

JSON-LD nodes and terms are always defined using camel case notation starting

with lower case.

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

>>> [!tip] EXAMPLE 4:

When referring to special terms, data types or words defined previously in the

present document or by other referenced specifications, italics format is used.

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

>>> [!tip] EXAMPLE 5:

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

When referring to the JSON-LD Context the mnemonic text string

_`@context`_ is used as a placeholder.

When referring to the JSON-LD Context the mnemonic text string _`@context`_ is

used as a placeholder.

All the dates and times are given in UTC format.

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

>>> [!tip] EXAMPLE 7:

The measurement units used in the API are those defined by the International

System of Units.

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

>>> [!tip] EXAMPLE 8:

### G.2.2 Associating an Entity with a natural language

Where a context Entity is associated with a single natural language, include a

well-defined _Property_ indicating the natural language of the

content. For example an Event taking place in French may be defined as follows:

well-defined _Property_ indicating the natural language of the content. For

example an Event taking place in French may be defined as follows:

```json

{

### G.2.3 Associating a Property with a natural language

Where a _Property_ of a context entity can be associated to

one more natural language, include additional metadata as a sub-Property of that

_Property_. For example, a Hotel with booking forms available

in English, French and German may be defined as follows:

Where a _Property_ of a context entity can be associated to one more natural

language, include additional metadata as a sub-Property of that _Property_. For

example, a Hotel with booking forms available in English, French and German may

be defined as follows:

```json

{

### G.2.4 Associating as equivalent Entity

Where equivalent context entities in multiple natural languages exist, they may

be associated with each other through the use of a one-to-many

_Relationships_, where each _Relationships_

holds an additional sub-Property indicating the natural language of the

equivalent entities.

be associated with each other through the use of a one-to-many _Relationships_,

where each _Relationships_ holds an additional sub-Property indicating the

natural language of the equivalent entities.

For example, three Events (such as a walking tour which is available in English,

French and German) may be associated to each other as follows:

### G.3.3 Route language sensitive queries via a proxy

Create a simple forwarding proxy around the NGSI-LD system. For any urls with a

_`q`_ param (and a _`collate`_ flag) run a clean-up

of the _`q`_ param and amend the query string:

_`q`_ param (and a _`collate`_ flag) run a clean-up of the _`q`_ param and amend

the query string:

The following request on the proxy:

### G.4.2 Localizing dates

For example, if a system needs to display _DateTime_ data in

Islamic Date format

For example, if a system needs to display _DateTime_ data in Islamic Date format

The following request on the proxy: