{"id":209,"date":"2020-03-20T13:46:14","date_gmt":"2020-03-20T13:46:14","guid":{"rendered":"http:\/\/data-models.fiware.org\/?page_id=209"},"modified":"2021-05-10T17:13:16","modified_gmt":"2021-05-10T15:13:16","slug":"guidelines","status":"publish","type":"page","link":"https:\/\/smartdatamodels.org\/index.php\/guidelines\/","title":{"rendered":"Guidelines"},"content":{"rendered":"<p><code><div id=\"file\" class=\"md\" data-path=\"guidelines.md\"><article class=\"markdown-body entry-content container-lg\" itemprop=\"text\"><div class=\"markdown-heading\" dir=\"auto\"><h1 class=\"heading-element\" dir=\"auto\">Smart Data Models guidelines<\/h1><a id=\"user-content-smart-data-models-guidelines\" class=\"anchor\" aria-label=\"Permalink: Smart Data Models guidelines\" href=\"#smart-data-models-guidelines\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<p dir=\"auto\">This is a set of guidelines for defining new data models.<\/p>\n<p dir=\"auto\">Before creating a new data model, <a href=\"https:\/\/smartdatamodels.org\/index.php\/ddbb-of-properties-descriptions\/\" rel=\"nofollow\">explore the existing ones<\/a>  or the <a href=\"https:\/\/smartdatamodels.org\/index.php\/list-of-data-models-3\/\" rel=\"nofollow\">quick finder<\/a> to be sure there is\nalready a data model that covers your use case. Recall to use synonyms in your search. E.g. what you might call Public\nTransport already exists under UrbanMobility.<\/p>\n<p dir=\"auto\">If you are looking for guidelines on adoption of existing data models, please\nrefer to <a href=\"https:\/\/github.com\/smart-data-models\/data-models\/blob\/master\/specs\/howto.md\">How to use Smart Data Models in your projects<\/a>\nsection.<\/p>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Syntax<\/h2><a id=\"user-content-syntax\" class=\"anchor\" aria-label=\"Permalink: Syntax\" href=\"#syntax\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<ul dir=\"auto\">\n<li>Use English terms, preferably American English.<\/li>\n<li>Use camel case syntax for attribute names (<code>camelCase<\/code>).<\/li>\n<li>Entity Type names must start with a Capital letter, for instance,\n<code>WasteContainer<\/code>.<\/li>\n<li>Use names and not verbs for Attributes of type Property, ex. <code>name<\/code>,\nqualifying it when necessary, ex. <code>totalSpotNumber<\/code> or <code>dateIssued<\/code>.<\/li>\n<li>Avoid plurals in Attribute names, but state clearly when a list of items\nfits. Ex. <code>category<\/code>.<\/li>\n<li>All first level properties defined in the  json schema has to have a description attribute<\/li>\n<\/ul>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Reuse<\/h2><a id=\"user-content-reuse\" class=\"anchor\" aria-label=\"Permalink: Reuse\" href=\"#reuse\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<ul dir=\"auto\">\n<li>Check for the existence of the same Attribute on any of the other models and\nreuse it, in <a href=\"https:\/\/smartdatamodels.org\" rel=\"nofollow\">this resource<\/a> if pertinent.<\/li>\n<li>When you find a confict it is recommended to extend the name. Example <em>category<\/em> would be replaced by <em>deviceCategory<\/em>.<\/li>\n<li>It is also available a resource for looking into the descriptions of the different\nproperties. Access to this <a href=\"https:\/\/smartdatamodels.org\/index.php\/ddbb-of-properties-descriptions\/\" rel=\"nofollow\">resource<\/a>.<\/li>\n<li>Have a look at <a href=\"http:\/\/schema.org\" rel=\"nofollow\">schema.org<\/a> trying to find a similar term\nwith the same semantics.<\/li>\n<li>Try to find common used ontologies or existing standards well accepted by\nthe Community, or by goverments, agencies, etc. For instance,\n<a href=\"http:\/\/www.open311.org\/\" rel=\"nofollow\">Open311<\/a> for civic issue tracking or\n<a href=\"http:\/\/www.datex2.eu\/\" rel=\"nofollow\">Datex II<\/a> for transport systems.<\/li>\n<\/ul>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Payload validation<\/h2><a id=\"user-content-payload-validation\" class=\"anchor\" aria-label=\"Permalink: Payload validation\" href=\"#payload-validation\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<ul dir=\"auto\">\n<li>The schemas defined here are aimed to validate key-values representation of the payloads<\/li>\n<li>It means that it is possible to have arrays of relationships (something which is not allowed in\nNGSI-LD, although it could be implemented through the datasetId)<\/li>\n<\/ul>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Data types<\/h2><a id=\"user-content-data-types\" class=\"anchor\" aria-label=\"Permalink: Data types\" href=\"#data-types\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<ul dir=\"auto\">\n<li>When possible reuse schema.org data types (<code>Text<\/code>, <code>Number<\/code>, <code>DateTime<\/code>,\n<code>StructuredValue<\/code>, etc.).<\/li>\n<li>Remember that <code>null<\/code> is not allowed in NGSI-LD and therefore should be\navoided as a value.<\/li>\n<\/ul>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Attribute definition<\/h2><a id=\"user-content-attribute-definition\" class=\"anchor\" aria-label=\"Permalink: Attribute definition\" href=\"#attribute-definition\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<ul dir=\"auto\">\n<li>\n<p dir=\"auto\">Enumerate the allowed values for each attribute. Generally speaking it is a\ngood idea to leave it open for applications to extend the list, provided the\nnew value is not semantically covered by any of the existing ones.<\/p>\n<\/li>\n<li>\n<p dir=\"auto\">State clearly what attributes are mandatory and what are optional. Remember\nthat <code>null<\/code> value should be avoided as it is prohibited in NGSI-LD. The minimum required  attributes will make the data models more flexible for other to use them.<\/p>\n<\/li>\n<li>\n<p dir=\"auto\">Whenever you create a list of enumerated values, use camelCase coding and strictly avoid spaces within the values (only allowed when mapping existing enumerated values)<\/p>\n<\/li>\n<li>\n<p dir=\"auto\">Internal attributes. In NGSIv2 there are two special attributes created by the system:<\/p>\n<ul dir=\"auto\">\n<li>dateCreated<\/li>\n<li>dateModified<\/li>\n<\/ul>\n<p dir=\"auto\">Similarly in NGSI-LD there are two different:<\/p>\n<ul dir=\"auto\">\n<li>createdAt<\/li>\n<li>modifiedAt<\/li>\n<\/ul>\n<p dir=\"auto\">those attributes <strong>must NOT be included into the definition of the data model<\/strong> (schema.json)\nbut they can appear in the payloads of the examples included.<\/p>\n<\/li>\n<\/ul>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Numbers<\/h2><a id=\"user-content-numbers\" class=\"anchor\" aria-label=\"Permalink: Numbers\" href=\"#numbers\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<ul dir=\"auto\">\n<li>When a value is a number, when relevant include range limits if they exist. Otherwise do not do it.<\/li>\n<\/ul>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Units<\/h2><a id=\"user-content-units\" class=\"anchor\" aria-label=\"Permalink: Units\" href=\"#units\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<ul dir=\"auto\">\n<li>\n<p dir=\"auto\">Define a default unit for magnitudes. Normally it will be the unit as stated\nby the International System of Units.<\/p>\n<\/li>\n<li>\n<p dir=\"auto\">If a quantity is expressed in a different unit than the default one, use the\n<a href=\"http:\/\/schema.org\/unitCode\" rel=\"nofollow\">unitCode<\/a> metadata attribute in NGSI v2.<\/p>\n<\/li>\n<li>\n<p dir=\"auto\">In NGSI-LD the Property <code>unitCode<\/code> is already defined and available to be\nused.<\/p>\n<\/li>\n<li>\n<p dir=\"auto\">The list of UN\/CEFACT Common Code (3 characters) can be download from this <a href=\"https:\/\/www.unece.org\/cefact\/codesfortrade\/codes_index.html\" rel=\"nofollow\">page<\/a>.<\/p>\n<\/li>\n<li>\n<p dir=\"auto\">The list is available directly from <a href=\"https:\/\/www.unece.org\/fileadmin\/DAM\/cefact\/recommendations\/rec20\/rec20.zip\" rel=\"nofollow\">here<\/a>.<\/p>\n<\/li>\n<\/ul>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Relative values \/ Percentages<\/h2><a id=\"user-content-relative-values--percentages\" class=\"anchor\" aria-label=\"Permalink: Relative values \/ Percentages\" href=\"#relative-values--percentages\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<ul dir=\"auto\">\n<li>Use values between <code>0<\/code> and <code>1<\/code> for relative quantities, which represent\nattribute values such as <code>relativeHumidity<\/code>, <code>precipitationProbability<\/code>,\netc.<\/li>\n<\/ul>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Modelling location<\/h2><a id=\"user-content-modelling-location\" class=\"anchor\" aria-label=\"Permalink: Modelling location\" href=\"#modelling-location\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<ul dir=\"auto\">\n<li>\n<p dir=\"auto\">Use <code>address<\/code> attribute for civic locations as per\n<a href=\"http:\/\/schema.org\/address\" rel=\"nofollow\">schema.org<\/a>. You can read the <a href=\"https:\/\/github.com\/smart-data-models\/data-models\/blob\/master\/common-schema.json\">location-commons<\/a><\/p>\n<\/li>\n<li>\n<p dir=\"auto\">Use the <code>location<\/code> Attribute for geographical coordinates. GeoJSON must be\nused for encoding geospatial properties.<\/p>\n<\/li>\n<li>\n<p dir=\"auto\">There is a shared resource including both at <a href=\"https:\/\/github.com\/smart-data-models\/data-models\/blob\/master\/common-schema.json#Location-Commons\">https:\/\/github.com\/smart-data-models\/data-models\/blob\/master\/common-schema.json<\/a><\/p>\n<\/li>\n<\/ul>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Modelling linked data<\/h2><a id=\"user-content-modelling-linked-data\" class=\"anchor\" aria-label=\"Permalink: Modelling linked data\" href=\"#modelling-linked-data\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<ul dir=\"auto\">\n<li>When an Entity Attribute is used as a link (relationship) to other entities name\nthe attribute using a verb (plus optionally an object) such as\n<code>hasStop<\/code>, <code>operatedBy<\/code>, <code>hasTrip<\/code>, etc. This option is the one\nadvocated by NGSI-LD, as in NGSI-LD URNs are used to identify entities,\nand NGSI-LD URNs already convey the type of the target entity, for\ninstance <code>urn:ngsi-ld:gtfs:Stop:S123<\/code>.<\/li>\n<\/ul>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Date Attributes<\/h2><a id=\"user-content-date-attributes\" class=\"anchor\" aria-label=\"Permalink: Date Attributes\" href=\"#date-attributes\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<ul dir=\"auto\">\n<li>\n<p dir=\"auto\">In NGSI v2 the Attribute type must be <code>DateTime<\/code>.<\/p>\n<\/li>\n<li>\n<p dir=\"auto\">In NGSI-LD, please check the date and time encoding at the\n<a href=\"https:\/\/github.com\/smart-data-models\/data-models\/blob\/master\/ngsi-ld_howto.md#airquality-in-ngsi-ld-format\">NGSI-LD FAQ<\/a>.<\/p>\n<\/li>\n<li>\n<p dir=\"auto\">Use the <code>date<\/code> prefix for naming entity attributes representing dates (or\ncomplete timestamps). Ex. <code>dateLastEmptying<\/code>.<\/p>\n<\/li>\n<li>\n<p dir=\"auto\"><code>dateCreated<\/code> in NGSIv2 (<code>createdAt<\/code> in NGSI-LD) must not be used as long as they are internal attributes of the NGSI specification.<\/p>\n<\/li>\n<li>\n<p dir=\"auto\"><code>dateModified<\/code> in NGSIv2 (<code>modifiedAt<\/code> in NGSI-LD) must not be used as long as they are internal attributes of the NGSI specification.<\/p>\n<\/li>\n<li>\n<p dir=\"auto\"><code>dateCreated<\/code> and <code>dateModified<\/code> are special read-only Entity Attributes provided\noff-the-shelf by NGSI implementations. Be careful because they can be\ndifferent than the actual creation or update date of the real world entity\nrepresented by its corresponding digital entity.<\/p>\n<\/li>\n<li>\n<p dir=\"auto\">When necessary define additional Attributes to capture precisely all the\ndetails about dates. For instance, to denote the date at which a weather\nforecast was delivered an attribute named <code>dateIssued<\/code> can be used. In that\nparticular case just reusing the internal attribute <code>dateCreated<\/code> would be\nincorrect because the latter would be the creation date of the (digital) entity\nrepresenting the weather forecast which typically might have a delay.<\/p>\n<\/li>\n<\/ul>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Dynamic attributes<\/h2><a id=\"user-content-dynamic-attributes\" class=\"anchor\" aria-label=\"Permalink: Dynamic attributes\" href=\"#dynamic-attributes\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<ul dir=\"auto\">\n<li>\n<p dir=\"auto\">In NGSI v2 use a metadata attribute named <code>timestamp<\/code> for capturing the last\nupdate timestamp of a dynamic attribute. Please note that this is the actual\ndate at which the measured value was obtained (from a sensor, by visual\nobservation, etc.), and that date might be different than the date (metadata\nattribute named <code>dateModified<\/code> as per NGSI v2) at which the attribute of the\ndigital entity was updated, as typically there might be delay, specially on\nIoT networks which deliver data only at specific timeslots.<\/p>\n<\/li>\n<li>\n<p dir=\"auto\">In NGSI-LD use the <code>observedAt<\/code> Property to convey timestamps.<\/p>\n<\/li>\n<\/ul>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Internationalization (i18N)<\/h2><a id=\"user-content-internationalization-i18n\" class=\"anchor\" aria-label=\"Permalink: Internationalization (i18N)\" href=\"#internationalization-i18n\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<p dir=\"auto\">There can be certain entity attributes which content is subject to be\ninternationalized. For instance, the description of a Point of Interest. The\ninternationalization (i18N) guidelines for the Smart Data Models are defined as\nfollows:<\/p>\n<ul dir=\"auto\">\n<li>\n<p dir=\"auto\">By default, the value of an attribute subject to be internationalized\n<em>should<\/em> be expressed in <strong>American English<\/strong> (<code>en-US<\/code>). However there can\nbe situations where an English term is not the most common one, for\ninstance, the English exonym for the city of Livorno (Italy) is a very\nobscure term, <code>Leghorn<\/code>. In such situations, the common international name\n(<code>Livorno<\/code> in our example) in latin script should be used.<\/p>\n<\/li>\n<li>\n<p dir=\"auto\">There shall always be a term for the original attribute, i.e. it is not\nallowed to have Entity representations which only contain terms associated\nto language variants.<\/p>\n<\/li>\n<li>\n<p dir=\"auto\">[Under revision] For each language variant of an internationalized attribute, there shall be\nan additional Entity Attribute which name shall be in the form:<\/p>\n<\/li>\n<\/ul>\n<p dir=\"auto\"><code>&lt;AttributeName&gt;_&lt;LanguageTag&gt;<\/code> where <code>AttributeName<\/code> is the original attribute\nname and <code>LanguageTag<\/code> shall be a language tag as mandated by\n<a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc5646.txt\" rel=\"nofollow\">RFC 5646<\/a>. W3C provides guidelines\non\n<a href=\"https:\/\/www.w3.org\/International\/articles\/language-tags\/\" rel=\"nofollow\">how to use language tags<\/a>.<\/p>\n<p dir=\"auto\"><a href=\"https:\/\/www.w3.org\/TR\/json-ld\/#string-internationalization\" rel=\"nofollow\">JSON-LD<\/a> can\nfacilitate developers to parse internationalized Entity representations, thus\nContext Data Producers are encouraged to use JSON-LD (provided that the backing\nimplementations support it).<\/p>\n<p dir=\"auto\">When parsing plain JSON content, developers should validate that the\ncorresponding JSON terms are actually conveying a language variant of an\nattribute. For instance, by validating that the term's suffix actually\ncorresponds to a valid language tag and by checking that the corresponding\noriginal attribute is contained in the entity.<\/p>\n<p dir=\"auto\">[Under review] Example:<\/p>\n<p dir=\"auto\">An entity may contain an attribute named <code>description<\/code>. The value of such\nattribute shall be expressed in American English. Additionally, it might exist an\nattribute named <code>description_es<\/code> used to convey the value of such a\n<code>description<\/code> attribute in Spanish.<\/p>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Some of the most used attributes<\/h2><a id=\"user-content-some-of-the-most-used-attributes\" class=\"anchor\" aria-label=\"Permalink: Some of the most used attributes\" href=\"#some-of-the-most-used-attributes\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<p dir=\"auto\">In case of doubt check the existing data models. The full list can be got in the\n<a href=\"https:\/\/smartdatamodels.org\/index.php\/ddbb-of-properties-descriptions\/\" rel=\"nofollow\">attributes search tool<\/a> by using an empty string.<\/p>\n<ul dir=\"auto\">\n<li><code>name<\/code><\/li>\n<li><code>alternateName<\/code><\/li>\n<li><code>description<\/code><\/li>\n<li><code>serialNumber<\/code><\/li>\n<li><code>category<\/code><\/li>\n<li><code>features<\/code><\/li>\n<li><code>source<\/code><\/li>\n<li><code>temperature<\/code><\/li>\n<\/ul>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Versioning<\/h2><a id=\"user-content-versioning\" class=\"anchor\" aria-label=\"Permalink: Versioning\" href=\"#versioning\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<p dir=\"auto\">FIWARE Foundation, TMForum, OASC and IUDX Smart Data Models Project aim to maintain backwards compatibility, however some\nincompatibilities will inevitably occur over time. Data providers may choose to\ntag Entities with an additional <code>schemaVersion<\/code> Attribute so that Data Consumers\ncan behave accordingly. This aligns with the\n<a href=\"https:\/\/schema.org\/schemaVersion\" rel=\"nofollow\">https:\/\/schema.org\/schemaVersion<\/a> Property\ndefinition.<\/p>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Mapping external standards<\/h2><a id=\"user-content-mapping-external-standards\" class=\"anchor\" aria-label=\"Permalink: Mapping external standards\" href=\"#mapping-external-standards\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<p dir=\"auto\">Smart Data Models follows the <a href=\".\/MANIFESTO.md\">six principles of agile standardization<\/a>\nThus, many existing, adopted and open standards are mapped into the SDM (GTFS, GBFS, DCAT-AP, schema.org, etc)\nthose cases we include in the schemas defining the data model an attribute 'derivedFrom' linking to the origin and\nspecifying the source in the description. Besides, although the recommendation for the codification of attributes is\nto use cameCase notation, those cases the original ones are preserved.<\/p>\n<p dir=\"auto\">In some specific cases like schema.org we only map those attributes that we have information of being used.\nWhy? Because schema.org have hundreds of attributes, and we only include those actually used. Hw could we document new attributes\nused and not available. Just rise an issue or make a PR on the repository and a new version will be generated extending the current data model.<\/p>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">How to contribute<\/h2><a id=\"user-content-how-to-contribute\" class=\"anchor\" aria-label=\"Permalink: How to contribute\" href=\"#how-to-contribute\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<p dir=\"auto\">Contributions should come in the form of pull requests.\n<a href=\"https:\/\/help.github.com\/articles\/fork-a-repo\/\">Fork<\/a> the repository,\n<a href=\"https:\/\/help.github.com\/articles\/creating-and-deleting-branches-within-your-repository\/\">Create a branch<\/a>\ncontaining your changes, and proceed with a\n<a href=\"https:\/\/help.github.com\/articles\/creating-a-pull-request-from-a-fork\/\">Pull Request<\/a>.<\/p>\n<p dir=\"auto\">Pull Request should be easy to review, so if the model, or the changes you are\nproposing are wide, please create different pull requests.<\/p>\n<p dir=\"auto\">New data models should be added under a folder structured as follows:<\/p>\n<div class=\"snippet-clipboard-content notranslate position-relative overflow-auto\" data-snippet-clipboard-copy-content=\"-   `NewModel\/`\n    - `notes.yaml`: An optional file with customization contents for the specification. Optional\n    -  `LICENSE.md`: file with the legal permission of use of th data model. It always grant free user, free modification and free share of modifications.\n    -  `ADOPTERS.yaml`: A file containing use cases of the data models. Optional\n    -   `schema.json`: The JSON Schema definition, which includes the descriptons of attributes, e.g.\n        [schema.json of WeatherObserved](.\/Weather\/WeatherObserved\/schema.json)\n        \n  - `examples\/`\n    -   `example.json`: One JSON key-values for NGSI v2 example file, e.g.\n        [example.json of WeatherObserved](https:\/\/github.com\/smart-data-models\/dataModel.Weather\/blob\/master\/WeatherObserved\/examples\/example.json)\n    -   `example.jsonld`: One JSON key-values for NGSI-LD example file, e.g.\n        [example.json of WeatherObserved](https:\/\/github.com\/smart-data-models\/dataModel.Weather\/blob\/master\/WeatherObserved\/examples\/example.jsonld)\n    -   `example-normalized.json`: One JSON example file in NGSI v2\n        normalized format, e.g.\n        [example-normalized.json of WeatherObserved](https:\/\/github.com\/smart-data-models\/dataModel.Weather\/blob\/master\/WeatherObserved\/examples\/example-normalized.json)\n    -   `example-normalized-ld.jsonld`: One JSON example file in\n        **NGSI-LD** normalized format, e.g.\n        [example-normalized-ld.jsonld of WeatherObserved](https:\/\/github.com\/smart-data-models\/dataModel.Weather\/blob\/master\/WeatherObserved\/examples\/example-normalized.jsonld)\n        \n  - `resources\/`. folder with additional contents for customization a data model in case notes.yaml is not enough. i.e. images. Optional\"><pre class=\"notranslate\"><code>-   `NewModel\/`\n    - `notes.yaml`: An optional file with customization contents for the specification. Optional\n    -  `LICENSE.md`: file with the legal permission of use of th data model. It always grant free user, free modification and free share of modifications.\n    -  `ADOPTERS.yaml`: A file containing use cases of the data models. Optional\n    -   `schema.json`: The JSON Schema definition, which includes the descriptons of attributes, e.g.\n        [schema.json of WeatherObserved](.\/Weather\/WeatherObserved\/schema.json)\n        \n  - `examples\/`\n    -   `example.json`: One JSON key-values for NGSI v2 example file, e.g.\n        [example.json of WeatherObserved](https:\/\/github.com\/smart-data-models\/dataModel.Weather\/blob\/master\/WeatherObserved\/examples\/example.json)\n    -   `example.jsonld`: One JSON key-values for NGSI-LD example file, e.g.\n        [example.json of WeatherObserved](https:\/\/github.com\/smart-data-models\/dataModel.Weather\/blob\/master\/WeatherObserved\/examples\/example.jsonld)\n    -   `example-normalized.json`: One JSON example file in NGSI v2\n        normalized format, e.g.\n        [example-normalized.json of WeatherObserved](https:\/\/github.com\/smart-data-models\/dataModel.Weather\/blob\/master\/WeatherObserved\/examples\/example-normalized.json)\n    -   `example-normalized-ld.jsonld`: One JSON example file in\n        **NGSI-LD** normalized format, e.g.\n        [example-normalized-ld.jsonld of WeatherObserved](https:\/\/github.com\/smart-data-models\/dataModel.Weather\/blob\/master\/WeatherObserved\/examples\/example-normalized.jsonld)\n        \n  - `resources\/`. folder with additional contents for customization a data model in case notes.yaml is not enough. i.e. images. Optional\n<\/code><\/pre><\/div>\n<p dir=\"auto\">New Subjects containing data  models should be added under a folder structured as follows:<\/p>\n<div class=\"snippet-clipboard-content notranslate position-relative overflow-auto\" data-snippet-clipboard-copy-content=\"-   `Subject\/`\n    -   `README.md`. Contains links and descriptions to the different data models contained in the subject. Generated automatically\n    -   `CONTRIBUTORS.yaml`. Contains data of the authors to the different data models contained in the subject. Optional \n    -   `notes.yaml`. Contents for the customization of the Subject README.md. Optional \n    -   `Subject-schema.json`. Schema containing objects used across differente data models. Referenced from there. Optional \n    -   `DataModel1`. Folder containing all the assets for a data model \n    -   `DataModel_incubated`. Folder with a link to where this new data model is being developing. Soon to be available. Optional\"><pre class=\"notranslate\"><code>-   `Subject\/`\n    -   `README.md`. Contains links and descriptions to the different data models contained in the subject. Generated automatically\n    -   `CONTRIBUTORS.yaml`. Contains data of the authors to the different data models contained in the subject. Optional \n    -   `notes.yaml`. Contents for the customization of the Subject README.md. Optional \n    -   `Subject-schema.json`. Schema containing objects used across differente data models. Referenced from there. Optional \n    -   `DataModel1`. Folder containing all the assets for a data model \n    -   `DataModel_incubated`. Folder with a link to where this new data model is being developing. Soon to be available. Optional\n<\/code><\/pre><\/div>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Definitions' section<\/h2><a id=\"user-content-definitions-section\" class=\"anchor\" aria-label=\"Permalink: Definitions' section\" href=\"#definitions-section\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<p dir=\"auto\">The section definitions will be included into the subject-schema.json name of the subject.<\/p>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">$ref values<\/h2><a id=\"user-content-ref-values\" class=\"anchor\" aria-label=\"Permalink: $ref values\" href=\"#ref-values\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<p dir=\"auto\">Whenever possible they will be absolute references in order to provide the ability to use the data models isolated from the rest of documents<\/p>\n<div class=\"markdown-heading\" dir=\"auto\"><h2 class=\"heading-element\" dir=\"auto\">Going through the data models<\/h2><a id=\"user-content-going-through-the-data-models\" class=\"anchor\" aria-label=\"Permalink: Going through the data models\" href=\"#going-through-the-data-models\"><svg data-component=\"Octicon\" class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"><path d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"><\/path><\/svg><\/a><\/div>\n<p dir=\"auto\">For a clear explanation on the current use of the data models. Check the <a href=\"https:\/\/github.com\/smart-data-models\/data-models\/blob\/master\/specs\/howto.md#going-through-a-data-model\">Going through the data models<\/a><\/p>\n<\/article><\/div><\/code><\/p>\n","protected":false},"excerpt":{"rendered":"<p> <a class=\"continue-reading-link\" href=\"https:\/\/smartdatamodels.org\/index.php\/guidelines\/\">More&#8230;<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_monsterinsights_skip_tracking":false,"footnotes":""},"class_list":["post-209","page","type-page","status-publish","hentry"],"jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":37,"url":"https:\/\/smartdatamodels.org\/index.php\/domain-repositories\/","url_meta":{"origin":209,"position":0},"title":"Domain repositories","author":"maestro","date":"17\/03\/2020","format":false,"excerpt":"List of main domains repositories https:\/\/github.com\/smart-data-models\/CrossSector https:\/\/github.com\/smart-data-models\/Smart-Sensoring https:\/\/github.com\/smart-data-models\/SmartAgrifood https:\/\/github.com\/smart-data-models\/SmartCities https:\/\/github.com\/smart-data-models\/SmartEnergy https:\/\/github.com\/smart-data-models\/SmartEnvironment https:\/\/github.com\/smart-data-models\/SmartWater \u00a0","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1217,"url":"https:\/\/smartdatamodels.org\/index.php\/list-of-data-models-2\/","url_meta":{"origin":209,"position":1},"title":"List of data models","author":"maestro","date":"01\/01\/2021","format":false,"excerpt":"List of data models","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":60,"url":"https:\/\/smartdatamodels.org\/index.php\/list-of-data-models\/","url_meta":{"origin":209,"position":2},"title":"List of data models and repositories","author":"maestro","date":"17\/03\/2020","format":false,"excerpt":"This page is obsolete, you should use the search tool. Check here any term you want to check if it is already standardized. If not maybe it could suggest it here choose the option new data model. List of data models","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":596,"url":"https:\/\/smartdatamodels.org\/index.php\/smart-data-models-survey\/","url_meta":{"origin":209,"position":3},"title":"Smart data models Survey","author":"maestro","date":"02\/09\/2020","format":false,"excerpt":"","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":192,"url":"https:\/\/smartdatamodels.org\/index.php\/use-data-models\/","url_meta":{"origin":209,"position":4},"title":"use Data models","author":"maestro","date":"20\/03\/2020","format":false,"excerpt":"All the data models available in Github under the umbrella repository smart-data-models are free to use and with an open license allowing its modification. You have a list here. There are examples in all of them in several formats, including json, jsonld, dtdl and csv. Additionally, there are schemas that\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":141,"url":"https:\/\/smartdatamodels.org\/index.php\/course-on-data-models\/","url_meta":{"origin":209,"position":5},"title":"Course on Data models","author":"maestro","date":"18\/03\/2020","format":false,"excerpt":"","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/pages\/209","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/comments?post=209"}],"version-history":[{"count":2,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/pages\/209\/revisions"}],"predecessor-version":[{"id":211,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/pages\/209\/revisions\/211"}],"wp:attachment":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/media?parent=209"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}