| Set a non-empty examples array at the top level of the schema to illustrate the expected data | |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /description |
| Set `properties` to identifier names that can be easily mapped to programming languages (matching [A-Za-z_][A-Za-z0-9_]*) | /properties/api-description – /properties/api-name – /properties/api-version – /properties/informationmodel-location – /properties/informationmodel-version |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/api-description/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/api-name/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/api-version/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/informationmodel/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/informationmodel-location/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/informationmodel-location/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/informationmodel-version/description |