The raise an issue form had an issue. It is already fixed.
Anyhow there is always room for improvement. Let us know
In order to create a new data model is always interesting what others have done in order copy and to maintain interoperability.
That’s why we have available a database with all attributes and enumerations across all data models.
Now it’s updated daily and the number of occurrences is also available.
We are testing a potential new format for the specification that
1) makes easier for people to read the specification
2) provides additional utility to be connected with other platforms making NGSI more compatible
Could you check these two new specifications Building, BuildingOperation compared with the old two Building, BuildingOperation and gives us your opinion?
(once in, click on the name of the object for deploying all the content)
The actual new specs are here without viewer (building, building operation) what you see above is generated automatically from the yaml specs.
What’s the idea behind adopting yaml specifications? To allow multiple evolutions (automatic multilanguage spec, integration with other platforms, etc)
New data models for
available at its own repository in the Cross-sector domain.
Thanks to stbnrivas for its migration from previous project Synchronicity
In the pending repository (the place where the data models can be developed if you wish) there is an interesting working going on about sensoring related to water management.
In development is :
– A data model for the actuator
– A data model for the service which is related to the actuator
– Modifications of the device data model
– A data model for a gateway gathering the data of a group of sensors
They are in the very early stages (so not that much is being contributed).
These contributions are based on the works of the EU project FIWARE4WATER in its group of IoT data models. You can contact them here.
Some of the contributors have requested some help about creating new data models. How to do it and where to do it.
HOW TO CREATE DATA MODELS
1) If you are clear about the payloads that you want to share (you have a plain key values json payload)
2) You can use this tool https://www.liquid-technologies.com/online-json-to-schema-converter (This link is always available in the Learning Zone on the upper menu, section tools)
to generate a draft version of the json schema. You will have to review (for sure).
– Whether you need some restrictions (min, max) on number properties
– The number of required properties
– The full list of options in enumeration properties
– Remove the context (it is treated as property)
– Check the Arrays (minItems, etc)
and possibly some other minor issues
WHERE TO CREATE DATA MODELS
3) We offer an open repository named pending for you to contribute while developing. Ask for access raising an issue with the option ‘Access to pending repository’
The data models for aquaculture are under specification. Contributors interested can make Pull Request or submit through the form
Thanks to the University of Cantabria (check the updated contributors.yaml) there are two new data models for Urban Mobility inside the domain of Smart cities
They are focused on the needs of public transport while been quite aligned with GTFS standard
The offStreet parking data model (inside smart cities domain) had improved its consistency between the specification and the examples and the data model schema. And to be aligned with DATEX II specification.
Check it out in this link OffStreetparking to see it complete.
Thanks to the user danvilmont
The new domain of Smart Destination includes now data models from Weather and Point of Interest. They are available as submodules.
The submodules are independent repositories and therefore its evolution will help Smart Destination to keep updated with the new needs.