Data Models Contribution API

TEST 1: Check if your candidate schema is properly documented

The schemas to be accepted need to include a description for every property

Call: https://smartdatamodels.org/extra/check_schema.php

Parameters: (Mandatories)

• schemaUrl: The link to the RAW version of the schema (see example)
• mail: your mail
• test: 1
• yamlOutput: True / False

Example: https://smartdatamodels.org/extra/check_schema.php?schemaUrl=https://raw.githubusercontent.com/smart-data-models/dataModel.Building/master/Building/schema.json&mail=alberto.abella@fiware.org&test=1&yamlOutput=False

Output: A json/yaml payload with 4 sections

documentationStatusOfProperties (report of the individual status of the property description)

• x-ngsi: Boolean. Describes if the description contains property, relationship or geoproperty in the description.
• x-ngsi_text: Text. Further explanations about x-ngsi value.
• documented: Boolean. If the description of the property reaches 15 chars.
• text: Text. complementary information about the documentation (it could be either incomplete or nonexisting)

schemaDiagnose (Global diagnose, needs to be zero wrong to get data model accepted)

• summary of how well documented are the properties

alreadyUsedProperties

• Properties used in other data models

availableProperties

• Properties never used in the initiative

Also available in this form below

FULL TEST: Check the whole data model repository

Parameters: (Mandatories)

• datamodelRepoUrl: The link to the data model repository repository on github (see example)
• mail: your mail
• testnumber: different tests you can choose from based on your need. Some tests depend on the others
• File structure check: to check the file structure of the repository, such as whether the url given is reachable, whether the least required files are in the repository (schema.json file and one jsonld example under examples folder)
• Schema is properly documented: to check the validation and content in schema.json file
• Examples check: to check the validation and content of files under the examples folder (Currently only example.json and example-normalized.json file supported)
• Other files check: to check the validation and content of other files, such as notes.yaml and ADOPTERS.yaml
• Full check: to do the full checks above
• yamlOutput: True / False

Output:

It will output the message under the processing of check; detailed information are stored in the json file, which is reachable by clicking the link.