error406 | Schema-register

Object gespecificeerd volgens https://tools.ietf.org/html/rfc7807.

Dialect2020-12

Typeobject

Eigenschappen

Eigenschappen van het JSON Schema
Eigenschap	Type	Verplicht	Beschrijving en details
acceptable	`array`	Ja	- Items type: string
detail	`string`	Ja	-
instance	`string`	Nee	-
status	`integer`	Ja	- Format: int32
title	`string`	Ja	-
type	`string`	Nee	URI naar een pagina met meer informatie over deze foutmelding voor de ontwikkelaar.

JSON Schema

{
  "$id": "https://schemas.don.projects.digilab.network/schemas/api-register/digitaal-stelsel-omgevingswet-dso/ruimtelijke-plannen-api-3zzh61mdr/error406",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "description": "Object gespecificeerd volgens https://tools.ietf.org/html/rfc7807.",
  "properties": {
    "acceptable": {
      "examples": [
        "[application/hal+json]"
      ],
      "items": {
        "type": "string"
      },
      "type": "array"
    },
    "detail": {
      "examples": [
        "HTTP 406 Not Acceptable"
      ],
      "type": "string"
    },
    "instance": {
      "examples": [
        "self"
      ],
      "type": "string"
    },
    "status": {
      "examples": [
        406
      ],
      "format": "int32",
      "type": "integer"
    },
    "title": {
      "examples": [
        "Not Acceptable"
      ],
      "type": "string"
    },
    "type": {
      "description": "URI naar een pagina met meer informatie over deze foutmelding voor de ontwikkelaar.",
      "examples": [
        "about:blank"
      ],
      "type": "string"
    }
  },
  "required": [
    "acceptable",
    "detail",
    "status",
    "title"
  ],
  "type": "object",
  "x-derived-from": [
    "https://ruimte.omgevingswet.overheid.nl/ruimtelijke-plannen/api/opvragen/v4/openapi.json#/components/schemas/Error406"
  ]
}

Schema gebruiken

JSON Schema

Bundled JSON Schema

Open in JSON Schema Viewer

Dependencies

Dit schema gebruikt geen andere schema's.

Dit schema wordt niet door andere schema's gebruikt.

Health issues

Health issues
Message	Pointer
Set a concise non-empty title at the top level of the schema to explain what the definition is about
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`
Only include instances in the `examples` array that validate against the schema	`/properties/acceptable/examples/0`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/status/format`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/status/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/type/description`

Schema-register: error406

Details van JSON Schema: error406

Details van JSON Schema: error406

Beschrijving