Smart water data models for subject water network management have been updated to align them with current guidelines.
These data model will allow you to connect your NGSI platform with EPANET.
There are no structural changes, but the definitions are located in the subject shared schema.
It affects to
This data model, node, is not officially approved but is on the path for becoming a resource for simulation a node inside a digital twin model (See this video) receiving the measures from an array of sensors controlling different properties and to provide these data to several other nodes which can be connected to.
Remember that incubated repository is devoted to the design and test before submitting officially to the Smart Data Models initiative.
You can claim access to this repository in the issue form option access to the incubated repository.
In order to align the data model for museum inside the subject of PointOf Interest with the Schema.org regarding the opening hours specification, it has been modified to make it compliant with it.
in fact, this translation of schema.org it has become part of the common shared elements of the data models available in the section DateTime-commons at the common-schema.json.
The GS1 Global Data Dictionary (GDD) is a repository of the data elements defined across all GS1 Standards.
GS1 Business Message Standards (BMS) and their components with definitions for GDSN 3.1, 3.1.2 , 3.1.3 and 3.1.4, GS1 XML for EDI 3.0, 3.1, 3.2 and 3.3, TSD and EPCIS 1.0.1. Higher versions will be added upon ratification.
The Business Messages are composed of Business Information Entities that comprise classes of information and their attributes. The attributes, in turn, have data types that may contain code list
The Full Set of GDSN & Shared Code Lists, and the Full Set of EDI, EPCIS, CPV & Shared Code Lists is now in a structured format in json much easier to integrate with NGSI platform.
Soon there will be part of them integrated into the smart data models.
1.- It is just a technical improvement but now you can access everything in this site with https://data-models.fiware.org.
2.- The issue form has also been improved with new options but simplified structure.
Check it out and please report any issue.
Best
The subscription page is being dramatically simplified keeping the same functionality.
Now instead of having different forms for the different mail lists nos it is just a checkbox fo the list you are willing to subscribe.
Remember just one mail once a week.
Every subject had a file named CONTRIBUTORS.md which compiles all contributors to the different data models in this subject. However, from the point of view of the management, it was not a structured format. Due to this, it is going to be replaced with a new file named CONTRIBUTORS.yaml with the same info but structured so we could manage properly and answer questions like:
Now there is also a field for allocating comments.
The format is friendly enough to be simply edited but at the same time, it can be automatically processed.
Next week CONTRIBUTORS.md will be removed from the different repos.
There is a new common section, named “DateTime-Commons“, in the file common-schema.json (the one which is partially included into most of the data models) because it compiles some shared elements (like Location-Commons or GSMA-Commons).
This section includes the first element, which is the mapping into a property (type object) of the schema.org class OpeningHoursSpecification. (see below)
So whenever there is an opening hours specification this would be the chosen format. (It is true that there is a similar property named OpeningHours, also mapped in schema.org) that it is only a text (oriented to be printed more than queried).
It only affects the museum data model that it will be updated after gathering the feedback of the contributors.
The new section included.
“DateTime-Commons”: {
“type”: “object”,
“description” : “All date-time elements in data models unless explicitly stated are ISO 8601 compliant”,
“properties”: {
“openingHoursSpecification”: {
“type”: “array”,
“description”: “A structured value providing information about the opening hours of a place or a certain service inside a place.”,
“items”: {
“properties”: {
“opens”: {
“type”: “string”,
“format”: “date-time”
},
“closes”: {
“type”: “string”,
“format”: “date-time”
},
“dayOfWeek”: {
“type”: “string”,
“enum”: [
“Monday”,
“Tuesday”,
“Wednesday”,
“Thursday”,
“Friday”,
“Saturday”,
“Sunday”,
“PublicHolidays”
]
},
“validFrom”: {
“type”: “string”,
“format”: “date-time”
},
“validThrough”: {
“type”: “string”,
“format”: “date-time”
}
}
},
“minItems”: 1
}
}
See it in the original file common-schema.json.
Dear users, now you’ll realise that examples are no longer in the root repo of every data model but in the examples folder.
The aims of this change are:
Now it is based on a responsive interface with these options:
Slack channel
Discord channel #smart-data-models
help on discord
Invitation to discord 
Validate a payload with a data model(external)
