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:
- How many contributors collaborate in this subject?
- How many subjects are being contributed by this person?
- What organisations are contributing to the initiative?
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.
“description” : “All date-time elements in data models unless explicitly stated are ISO 8601 compliant”,
“description”: “A structured value providing information about the opening hours of a place or a certain service inside a place.”,
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:
- Open the ability to have more exports and options of the examples
- Get cleaner the root directory
Now it is based on a responsive interface with these options:
- Sort any column
- Search on any value across the different columns
- 50-pages pagination
check it out
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.