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
In the process of converting repositories to the new format, the repo dataModel.WasteManagement is being converted.
It means:
Although the net is plenty of sites for validation of a payload against a json schema, below you have this service.
Besides this post the form will be available in the validation payload link where it is explained how to validate through an API call (bottom part of the page, so scroll down a bit)
Enjoy!
For those of you willing to submit new data models there has been an update of the contribution manual in section 1.2 pages 9-11.
It affects to the use of $ref for single properties and how to document.
Additionally the expections allowed (for the moment) for the documentation of geoproperties.
In the process of converting repositories to the new format, the repo dataModel.Agrifood is being converted.
It means:
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)
Output: A json payload with these properties
on error
In the process of converting repositories to the new format, the repo dataModel.Weather is being converted.
It means:
In the process of converting repositories to the new format, the repo dataModel.PointOfInterestr is being converted.
It means:
In the process of converting repositories to the new format, the repo dataModel.User is being converted.
It means:
In the process of converting repositories to the new format, the repo dataModel.device is being converted.
It means: