- SourceMeta name
- order
- Base dialect
- https://json-schema.org/draft/2020-12/schema
- SourceMeta dialect
- https://json-schema.org/draft/2020-12/schema
- Bytes
- 1.000 bytes
- Bytes bundled
- 1.000 bytes
- Health
- 29%
- Dependencies
- -
Health issues
- Name
- unknown_keywords_prefix
- Message
- Future versions of JSON Schema will refuse to evaluate unknown keywords or custom keywords from optional vocabularies that don't have an x- prefix
- Pointers
- /xml
- Name
- top_level_title
- Message
- Set a concise non-empty title at the top level of the schema to explain what the definition is about
- Pointers
- Name
- top_level_description
- Message
- Set a non-empty description at the top level of the schema to explain what the definition is about in detail
- Pointers
- Name
- top_level_examples
- Message
- Set a non-empty examples array at the top level of the schema to illustrate the expected data
- Pointers
- Name
- non_applicable_type_specific_keywords
- Message
- Avoid keywords that don't apply to the type or types that the current subschema expects
- Pointers
- /properties/id/format
- Name
- unknown_format_prefix
- Message
- For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification
- Pointers
- /properties/id/format
- Name
- non_applicable_type_specific_keywords
- Message
- Avoid keywords that don't apply to the type or types that the current subschema expects
- Pointers
- /properties/petId/format
- Name
- unknown_format_prefix
- Message
- For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification
- Pointers
- /properties/petId/format
- Name
- non_applicable_type_specific_keywords
- Message
- Avoid keywords that don't apply to the type or types that the current subschema expects
- Pointers
- /properties/quantity/format
- Name
- unknown_format_prefix
- Message
- For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification
- Pointers
- /properties/quantity/format
- Name
- enum_with_type
- Message
- Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types
- Pointers
- /properties/status/enum - /properties/status/type
{
"$id": "https://schemas.don.projects.digilab.network/schemas/api-register/directoraat-generaal-belastingdienst/swagger-petstore-open-api-3-0-pnkal4kdg/order",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"complete": {
"type": "boolean"
},
"id": {
"examples": [
10
],
"format": "int64",
"type": "integer"
},
"petId": {
"examples": [
198772
],
"format": "int64",
"type": "integer"
},
"quantity": {
"examples": [
7
],
"format": "int32",
"type": "integer"
},
"shipDate": {
"format": "date-time",
"type": "string"
},
"status": {
"description": "Order Status",
"enum": [
"placed",
"approved",
"delivered"
],
"examples": [
"approved"
],
"type": "string"
}
},
"type": "object",
"x-derived-from": [
"https://petstore3.swagger.io/api/v3/openapi.json#/components/schemas/Order"
],
"xml": {
"name": "order"
}
}