There is a new option in the main menu Data Models -> Contribution Checklist
It is strongly recommended to pass every element before submitting your new data model.
See below the checklist
No comments
Author: maestro
New data model in Energy subject InverterDevice
1 new data model is available in the subject dataModel.Energy.
InverterDevice. The data model is intended to describe the mechanical, electrical characteristics of an Inverter according to DC – Direct Current Information supplied as input and AC – Alternating Current Information returned as output. Remark: This Data Model can be used directly as the main entity to describe the device [Inverter] or as a sub-entity of the Data Model {DEVICE] using a reference by the [refDevice] attribute.
Thanks to the contributors of the subject.
New NGSI linked data generator for every data model
Now the README file of every data model includes a link to the generator of NGSI-LD payloads compliant with the data model.
As you can see in the image below there is a new section “Dynamic examples generation”
There is the sentence “Link to the Generator of NGSI-LD payloads compliant with this data model. Refresh for new values”. By clicking the Generator link an example of payload appears on the web page. Refreshing (F5) generates new payloads.
Updated interactive specification
Now all data models have an interactive specification. (As long as they have examples)
This is the first step to deeper interactive services for every data model contributed.
See the example for weatherForecast.
First Survey to users and contributors of Smart Data Models
Privacy Object for Iot Devices in Device Subject
1 new data model coming from the synchronicity project is available in the subject dataModels.Device.
- PrivacyObject. Information about privacy for an IoT device.
The first version of this data model initially was developed in the project synchronicity and now it will be curated here.
Include userAlias in common-schema.json
The file common-schema.json compiles those properties massively used across the different data models in the different domains.
The property userAlias has been included to store those anonymous identifiers of a user that cannot be traced back to the user.
It can be referenced in any data model just by including this code
“userAlias”: {
“$ref” : “https://smart-data-models.github.io/data-models/common-schema.json#/definitions/userAlias”
}
Queue Monitor data model in Queue Management Subject
1 new data model coming from the synchronicity project is available in the subject dataModels.QueueManagement.
- QueueMonitor. An office counter queue system on a daily run.
The first version of this data model initially was developed in the project synchronicity and now it will be curated here.
RoadAccident data model in transportation Subject
1 new data model coming from the synchronicity project is available in the subject dataModels.Transportation.
- RoadAccident. A road accident description with causes and aftermath.
The first version of this data model was initially developed in the project synchronicity and now it will be curated here.
New data models in transportation subject coming from synchronicity project
3 new data models coming from the synchronicity project are available in the subject dataModels.Transportation.
- RestrictedTrafficArea. An area of a city in which the traffic generated by cars or any other kind of vehicles is subjected to limitation.
- RestrictionException. A Restriction Exception represents a particular case that specialise restriction reported in a Restricted Traffic Areas; for instance, it could describe particular permissions applied to specific kind of vehicles
- SpecialRestriction. A Special Restriction represents a particular case that specialise restriction reported in a Restricted Traffic Areas; for instance, it could describe particular restrictions applied to specific kind of vehicles
These data models were initially developed in the project synchronicity and now it will be curated here.
