Inline Custom Styles

[some text]{.HTML-Code}
[some text]{.HTML-Sample}
[some text]{.HTML-Variable}
[some text]{.HTML-Keyboard}
[some text]{.HTML-Definition}
[some text]{.HTML-Error}
[some text]{.NF}

some text
some text
some text
some text
some text
some text
some text

Headings

# Heading 1

## Heading 2

### Heading 3

#### Heading 4

##### Heading 5

###### Heading 6

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5

Heading 6

Text Styles

*Italic Text*
**Bold Text**
***Bold Italic Text***
Text<sup>1</sup>

Italic Text
Bold Text
Bold Italic Text
Text¹

Links

(Google)[https://google.com]

Google

References

In this text we refer to [n.1] and [i.someref].

In this text we refer to [n.1] and [i.someref]

Notes

>>> [!note] NOTE:

When the simplified GeoJSON representation is selected, the layout of the Entities changes, see clause 4.5.17 for details.

>>>

NOTE:

When the simplified GeoJSON representation is selected, the layout of the Entities changes, see clause 4.5.17 for details.

Examples

>>> [!tip] EXAMPLE 1:

When the simplified GeoJSON representation is selected, the layout of the Entities changes, see clause 4.5.17 for details.

>>>

EXAMPLE 1:

When the simplified GeoJSON representation is selected, the layout of the Entities changes, see clause 4.5.17 for details.

JSONS

``` json
{
  "id": "urn:ngsi-ld:Car:6152s",
  "type": "Car",
  "parkingTickets": {
  "type": "JsonProperty",
  "json": {
         "id": "85a6cc52-0589-45f9",
         "value": "Overstay 60 minutes"
      }
  }
}
```

{
  "id": "urn:ngsi-ld:Car:6152s",
  "type": "Car",
  "parkingTickets": {
  "type": "JsonProperty",
  "json": {
         "id": "85a6cc52-0589-45f9",
         "value": "Overstay 60 minutes"
      }
  }
}

>>> [!tip] EXAMPLE 11:

[?q=parkingTickets\[value\]=="Overstay 60 minutes"&jsonKeys=parkingTickets]{.HTML-Code} . The trailing path is [parkingTickets]{.HTML-Code} . The [parkingTickets]{.HTML-Code} *Property* of the JSON object is targeted, but the target [value]{.HTML-Code} raw is JSON, and is not expanded to [ngsi-ld:hasValue]{.HTML-Code} using the core *\@context* . Refer to the following NGSI-LD Entity:
``` json
{
  "id": "urn:ngsi-ld:Car:6152s",
  "type": "Car",
  "parkingTickets": {
  "type": "JsonProperty",
  "json": {
         "id": "85a6cc52-0589-45f9",
         "value": "Overstay 60 minutes"
      }
  }
}
```

>>>

EXAMPLE 11:

?q=parkingTickets[value]==“Overstay 60 minutes”&jsonKeys=parkingTickets . The trailing path is parkingTickets . The parkingTickets Property of the JSON object is targeted, but the target value raw is JSON, and is not expanded to ngsi-ld:hasValue using the core @context . Refer to the following NGSI-LD Entity:

{
  "id": "urn:ngsi-ld:Car:6152s",
  "type": "Car",
  "parkingTickets": {
  "type": "JsonProperty",
  "json": {
         "id": "85a6cc52-0589-45f9",
         "value": "Overstay 60 minutes"
      }
  }
}

Images

This is the default way to include images along with their captions:

![](media/image2.png)

**Figure 4.2.1-1: Overview of the NGSI-LD Information Model Structure**

Figure 4.2.1‑1: Overview of the NGSI-LD Information Model Structure

Below, the alternative syntax:

::: FL
<img src="media/image2.png" >
:::

::: TF
Figure 4.2.1-1: Overview of the NGSI-LD Information Model Structure
:::

Figure 4.2.1‑1: Overview of the NGSI-LD Information Model Structure

Tables

Use grid tables for best results:

**Table 4.3.5-2: Main implementation configurations**


+-------------------+-----------------------------------------+----------------------------------------+
| Description | Temporal API | RegistryAPI |
+===========+=======================+=======================+
| Central | none | none |
+-------------------+-----------------------------------------+----------------------------------------+

Table 4.3.5‑2: Main implementation configurations

Description	Temporal API	RegistryAPI
Central	none	none

NOTE: The "prettier-ignore" statements prevent the code formatter from altering the layout of GRID TABLES. As of today, Prettier does not support GRID TABLES out of the box.

For captions we support both the following syntaxes:

**Table 4.3.5-2: Main implementation configurations** (DEFAULT ONE)

::: TF
Table 4.3.5-2: Main implementation configurations
:::

Table 4.3.5‑2: Main implementation configurations

Lists

#### 5.6.8.3 Input data

- A JSON-LD Array containing one or more JSON-LD documents each one representing an Entity as mandated by clause 5.2.4. See clause 5.5.11.2 for information on behaviour when there is more than one instance of the same entity in the input Array.
- An optional flag indicating the update mode (only applies in case the Entity already exists):
- Replace. All the existing Entity content shall be replaced (default mode).
- Update. Existing Entity content shall be updated.

5.6.8.3 Input data

A JSON-LD Array containing one or more JSON-LD documents each one representing an Entity as mandated by clause 5.2.4. See clause 5.5.11.2 for information on behaviour when there is more than one instance of the same entity in the input Array.
An optional flag indicating the update mode (only applies in case the Entity already exists):
- Replace. All the existing Entity content shall be replaced (default mode).
- Update. Existing Entity content shall be updated.

Hardcoded links to clauses/figures/images

See clauses 3.2, 1.2 and 5.6.8.3.
Looking at Table 2.3-1.
As shown in Figure 4.2.1-1.
As mentioned in annex b.

See clauses 3.2, 1.2 and 5.6.8.3.
Looking at table 2.3-1.
As shown in figure 4.2.1-1.
As mentioned in annex b.

Dynamic links to clauses/figures/images

See Clause+++test+++root.2.3.
Looking at Table+++below.
As shown in Figure+++above.
As mentioned in Clause+++root.
As shown in Figure+++image23.png. (we suppose there exists a image with this name in the media folder and in the document)

See clause 3.2.3.
Looking at table 2.3-1.
As shown in figure 4.2.1-1.
As mentioned in annex b.
As shown in figure 2.3-1.