Data models guidelines
This is a set of guidelines for defining new data models. Further information and a guideline update can be found at D2.2 Synhronicity IoT LSP
- Use English terms, preferably American English.
- Use camel case syntax for attribute names (
- Entity type names must start with a Capital letter, for instance,
- Use names and not verbs for attribute names, ex.
name, qualifying it when necessary, ex.
- Avoid plurals in attribute names, but state clearly when a list of items fits. Ex.
- Check for the existence of the same attribute on any of the other models and reuse it, if pertinent.
- Have a look at schema.org trying to find a similar term with the same semantics.
- Try to find common used ontologies or existing standards well accepted by the Community, or by goverments, agencies, etc. For instance, Open311 for civic issue tracking or Datex II for transport systems.
- When possible reuse schema.org data types (
Enumerate the allowed values for each attribute. Generally speaking it is a good idea to leave it open for applications to extend the list, provided the new value is not semantically covered by any of the existing ones.
State clearly what attributes are mandatory and what are optional. If needed state clearly what is the meaning of a
Define a default unit for magnitudes. Normally it will be the unit as stated by the international system of units.
If a quantity is expressed in a different unit than the default one, use the unitCode metadata attribute.
- Use values between
1for relative quantities, which represent attribute values such as
addressattribute for civic locations as per schema.org
locationattribute for geographical coordinates. Ideally use GeoJSON for codifying geospatial properties. That works from Orion 1.2 on. If not use, old NGSI version 1 type
Modelling linked data
When an entity attribute is used as a link (relationship) to other entities two modelling options are possible:
- A/ Name the attribute with the prefix
refplus the name of the target (linked) entity type. For instance
refStreetlightModel, represents an attribute which contains a reference to an entity of type
StreetlightModel. This option has been extensively used by data models initially intended to be used with NGSIv2 .
- B/ Name the attribute using a verb (plus optionally an object) such as
hasTrip, etc. This option is the one advocated by NGSI-LD, as in NGSI-LD URNs are used to identify entities, and NGSI-LD URNs already convey the type of the target entity, for instance
- A/ Name the attribute with the prefix
As the current trend is to align with NGSI-LD as much as possible, B option can be considered as the recommended one and A option is to some extent "deprecated".
Attribute type must be
dateprefix for naming entity attributes representing dates (or complete timestamps). Ex.
dateCreatedmust be used to denote the (digital) entity's creation date.
dateModifiedmust be used to denote the (digital) entity's last update date.
dateModifiedare special entity attributes provided off-the-shelf by NGSIv2 implementations. Be careful because they can be different than the actual creation or update date of the real world entity represented by its corresponding digital entity.
When necessary define additional attributes to capture precisely all the details about dates. For instance, to denote the date at which a weather forecast was delivered an attribute named
dateIssuedcan be used. In that particular case just reusing
dateCreatedwould be incorrect because the latter would be the creation date of the (digital) entity representing the weather forecast which typically might have a delay.
- Use a metadata attribute named
timestampfor capturing the last update timestamp of a dynamic attribute. Please note that this is the actual date at which the measured value was obtained (from a sensor, by visual observation, etc.), and that date might be different than the date (metadata attribute named
dateModifiedas per NGSIv2) at which the attribute of the digital entity was updated, as typically there might be delay, specially on IoT networks which deliver data only at specific timeslots.
There can be certain entity attributes which content is subject to be internationalized. For instance, the description of a Point of Interest. The internationalization (i18N) guidelines for the FIWARE Data Models are defined as follows:
By default, the value of an attribute subject to be internationalized should be expressed in American English (
en-US). However there can be situations where an English term is not the most common one, for instance, the English exonym for the city of Livorno (Italy) is a very obscure term,
Leghorn. In such situations, the common international name (
Livornoin our example) in latin script should be used.
There shall always be a term for the original attribute, i.e. it is not allowed to have entity representations which only contain terms associated to language variants.
- For each language variant of an internationalized attribute, there shall be an additional entity attribute which name shall be in the form:
JSON-LD can facilitate developers to parse internationalized entity representations, thus Context Producers are encouraged to use JSON-LD (provided that the backing implementations support it).
When parsing plain JSON content, developers should validate that the corresponding JSON terms are actually conveying a language variant of an attribute. For instance, by validating that the term's suffix actually corresponds to a valid language tag and by checking that the corresponding original attribute is contained in the entity.
An entity may contain an attribute named
description. The value of such attribute shall be expressed in American English.
Additionally it might exist an attribute named
description_es used to convey the value of such a
description attribute in Spanish.
Some of the most used attributes
In case of doubt check other existing models!