The greenEnergy Subject now compiles two data models GreenEnergyGenerator and GreenEnergyMeasurement inherited (recover) from former synchronicity project.
Thanks to Esteban Rivas, and his entity the La Factoria BikeIn.
No comments
Author: maestro
New store data model for Point of Interest repository
Thanks to the contribution of the University of Cantabria and the migration of data models from synchronicity project, now there is a new data model for Store in the repository of Point of Interest.
You can see the contributors which are the ones in the global repository belonging to University of Cantabria.
It takes a while to update the README.md and other documents.
Updated DateTime-Commons
Thanks to the contributors of Store data model inside the point of interest repository it has been detected an error in the shared element which maps schema.org concept of opening hours specification which was located at commons in the root of data models repository.
Automatic creation of examples
In order to reduce the amount of work in the contribution of data models, we have a script that generates the key-values format of a normalized NGSI LD payload.
It has been operated on 46 data models currently in the repository.
In a close future instead of submitting 4 examples, it will be only necessary to include 2 examples, the normalized payloads for NGSI v2 and NGSI LD (the other two would be generated automatically).
Making examples more consistent
All the repositories have been normalized in the naming of the core examples. So:
- Key values in NGSI v2 is named example.json
- Key values in NGSI LD is named example.jsonld
- Normalized (default) in NGSI v2 is named example-normalized.json
- Normalized (default) in NGSI LD is named example-normalized.jsonld
It is possible to have more examples in the directory. And in the same directory of every data model, there are other exports (csv) for the use of the data model users.
The goal is that this 4 examples were present in every data model
Manual for simple contribution updated
The manual for a simple contribution of a data model has been updated. See it in this link.
Automated README for Subjects
As promised the README.md at Subject level explaining the different data models is automated, and therefore there is no need to be contributed by the contributors. See an example here for the weather subject
Thus, the README.md is based on the data models and their descriptions, linking to the current contributors
Soon the README.md for the domain will be also automated.
Best
Replaced CONTRIBUTORS.MD by CONTRIBUTORS.yaml
Now in the root of every subject, you can find only the file CONTRIBUTORS.yaml with the current contributors to the data model of the subject.
The old file CONTRIBUTORS.md is being removed.
CONTRIBUTORS.yaml is a structured format that allows automatic treatment globally across the initiative. It compiles the full name of the contributor, his/her organization, and their project and comments if necessary.
If you keep seeing it is because you are not looking at the master branch but in a specific commit (like it happens in the submodules). We update the branches in submodules daily, so tomorrow it will not appear unless you want it to go to former commits.
See one example.
Automated README.md for data models
Currently, the README.md at data models level (inside every directory in a Subject) explaining the contents of the data models is automated, and therefore there is no need to be contributed by the contributors. See an example here for the weather forecast.
Thus, the README.md is based on the examples provided, the specification and the model.yaml.
Soon the README.md for the Subject will be also automated.
New domain aeronautics
A new domain SmartAeronautics it is available and some data models are being incubated in the first subject of this domain dataModel.Aeronautics.
the data models are
Slack channel
Validate a payload with a data model