There is a new data model RainFallRadarObservation. The Data Model is intended to measure the water slides on a predefined area by a set of 4 Location represented by a Geo property format.
Located in the Environment Subject.
No comments
Category: Smart Environment domain
New data model for Environment. Phreatic Observed
There is a new data model PhreaticObserved is intended to measure, observe and control the level and quality of groundwater at a given time (T), by a fixed or mobile monitoring system. Depending on the device used, it is also possible to measure the quality of water such as its electrical conductivity, its salt content, its temperature, etc. In this case, the values measured are processed by the Data Model `WaterObserved` and `WaterQualityObserved`. Additional Information about Attributes: For attributes dedicated to water, a MetaData attribute can also be used. it contains the `TimeStamp` in seconds, the `qualification` and control `status` of the measurement”.
Located in the Environment Subject
New data model IndoorEnvironmentObserved
There is a new data model IndoorEnvironmentObserved for observations of air and climate conditions for indoor environments.
It belongs to the Smart.Environment domain in the subject dataModel.Environment.
Specifications in languages in the readme of the data models
Now you can see the links to the specification in two languages, Spanish y French in the README.md of every data models. German and Japanese are in the queue.
See here an example
All specifications updated
All the specifications (the text descriptions of the data model located in the /doc directory of each daat model) for the different domains and languages (currently French and Spanish besides English) have been updated to the new format. See an example in Spanish and French.
All of them are generated automatically from the json schema (which is the unique source of truth for the data model)
The contribution manual explains further details.
Raise an issue for any point you find in the new format.
Repo dataModel.WasteManagement updated
In the process of converting repositories to the new format, the repo dataModel.WasteManagement is being converted.
It means:
- json schema has already documented every property
- The new specs in EN-US, FR and ES are available
Check a schema validates a payload
If you want to check if a schema validates a payload through this API call
Call: https://smartdatamodels.org/extra/validate_payload.php
Parameters: (Mandatories)
- payloadUrl: The url of the payload in RAW version
- schemaUrl: The link to the RAW version of the json schema (see example)
Output: A json payload with these properties
- result: Boolean. if the schema validates the payload.
- time: time stamp in ISO 8601 (CET) of the validation
- payloadUrl: The url of the payload in RAW version submitted
- schemaUrl: The link to the RAW version of the json schema submitted
on error
- cause: The description of the cause for the rejection to the validation
Repo dataModel.Weather updated
In the process of converting repositories to the new format, the repo dataModel.Weather is being converted.
It means:
- json schema has already documented every property
- The new specs in EN-US, FR and ES are available
updated the contribution manual
The contribution manual (link in the upper menu of main page) is updated due to the change in the approach for documenting the data models.
Main changes:
- Properties’ definitions are now included as an attribute in the json schema
- The specification is generated automatically based on the json schema
- Json schema has to pass a test to be approved.
See the rest of changes in the link
Create automatically the specification of your data model
The new version of the smart data models specification is on progress (most of the /doc directories of the data models have a version). If you want to check how this would look like you can have through this API call
Call: https://smartdatamodels.org/extra/create_spec.php
Parameters: (Mandatories)
- dataModel: The name of the entity for the specification
- schemaUrl: The link to the RAW version of the json schema (see example)
- examplesUrl: the url of where the 4 examples required for a data model are available (named
- notesUrl: The url to the yaml for the customization paragraphs (notesHeader, after the title, notesMiddle, after properties’ list and notesFooter by the end)
- mail:Â a valid mail of yours
Output: A markdown text that although the HTML visualization is faulty, the source code of the page can be pasted in any markdown viewer (optimized for github) and you see will see something like this.
We are on the transition to having all the data models compliant.
