All submitted modules are required to have a schemaVersion attribute in their schema.json.
This is changed in the guidelines for coding standards
An automatic script will detect it and in case of not being detected it includes a line
“schemaVersion” : “0.0”
The vehicle data model has been adapted to DATEX II 3.0 in terms of vehicle types.
Included pollutants Arsenic, Benzene, Cadmium, carbon monoxide, nickel, nitrogen monoxide, nitrogen dioxide, ozone, particulate minor 10 microns, particulate minor 2.5 microns, lead, sulfur dioxide, hydrogen sulfide.
Data model for vehicle, inside topic dataModel.Transportation to meet the description of datex II of having -1 speed to represent stopped cars.
There is a new domain available Robotics. In a short time, there will be topics and data models regarding this domain.
It has been created the topics for the domain of Smartwater
soon there will be PR to fill it with the data models
Thanks to Jaime Ventura, See here the issue comments but we will change the
uVIndexMax attribute across different data model.
IUDX joins the steering board of Smart Data Models initiative. This agreement will allow FIWARE and the IUDX to collaborate on data models suitable for use in smart city applications. This work will be done in conjunction with the ongoing joint activity between TM Forum — an alliance of 850+ global companies working together to break down technology and cultural barriers between digital service providers, technology suppliers, consultancies and systems integrators — and FIWARE.
This is the first post of this initiative. Just a thought if we really knew the cost of not sharing the same data models, maybe we should stop everything and say let’s do it.
However in a society with extreme growth of data availability, shared data models are not capable of growth at the same rate as data with the current standardization approach.
This initiative lead by TMForum an FIWARE foundation is addressing this concern by providing a flexible and agile way of sharing data models.