Annex F (informative):
Conventions and syntax guidelines

When new terms are defined, they are marked in bold, and terms are capitalized thereafter.

EXAMPLE 1:
NGSI-LD Linked Entity , Linked Entity .

API Parameter names are always in lowercase.

EXAMPLE 2:
options .

Entity Types are defined using lowercase but with a starting capital letter.

EXAMPLE 3:
Vehicle, Building, ParkingSpace.

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

EXAMPLE 4:
createdAt , value , unitCode .

When referring to special terms, data types or words defined previously in the present document or by other referenced specifications, italics format is used.

EXAMPLE 5:
ListRelationship, GeoProperty, Geometry, Second, Number .

When referring to literal strings double quotes are used.

EXAMPLE 6:
"application/json" , "Subscription" .

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.

EXAMPLE 7:
2018-02-09T11:00:00Z .

The measurement units used in the API are those defined by the International System of Units.

EXAMPLE 8:
The distance in geo-queries is provided in meters.

When defining application-specific elements or API extensions the same conventions and syntax guidelines should be followed.