dataverkennerbetrokkenbijmbetrokkenbij

betrokkenbij

Dialect2020-12

Typeobject

Eigenschappen

Eigenschappen van het JSON Schema
Eigenschap	Type	Verplicht	Beschrijving en details
_links	`object`	Ja	The contents of the `betrokkenbij._links` field. It contains all relationships with objects.
_links.schema	`string`	Ja	The schema field is exposed with every record Format: uri
_links.self	`$ref`	Ja	- $ref: ../_shared/dataverkennerbetrokkenbijbetrokkenbijlink
betrokkenBijIdentificatie	`string, null`	Nee	Identificatie van bovenliggende (gesplitste) A-percelen.
betrokkenBijKadastraleAanduiding	`string, null`	Nee	De unieke aanduiding van bovenliggende (gesplitste) A-percelen.
betrokkenBijKadastraleobjectenId	`string, null`	Nee	Id van bovenliggende (gesplitste) A-percelen.
betrokkenBijVolgnummer	`integer, null`	Nee	Volgnummer van bovenliggende (gesplitste) A-percelen. Format: int64 Minimum: -9223372036854776000 Maximum: 9223372036854776000
id	`string`	Ja	-
identificatie	`string`	Ja	De unieke aanduiding van een Kadastraal object.
kadastraleAanduiding	`string, null`	Nee	De unieke aanduiding van een Kadastraal Object samengesteld uit gemeentecode, kadastrale sectie, perceelnummer, indexletter en indexnummer.
neuronId	`integer`	Ja	Neuron ID Format: int64 Minimum: -9223372036854776000 Maximum: 9223372036854776000
volgnummer	`integer`	Ja	Uniek volgnummer van de toestand van het object. Format: int64 Minimum: -9223372036854776000 Maximum: 9223372036854776000

JSON Schema

{
  "$id": "https://schemas.don.projects.digilab.network/schemas/api-register/gemeente-amsterdam/dataverkenner-betrokkenbijm-sd3lfuehg/dataverkennerbetrokkenbijmbetrokkenbij",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "description": "betrokkenbij",
  "properties": {
    "_links": {
      "description": "The contents of the `betrokkenbij._links` field. It contains all relationships with objects.",
      "properties": {
        "schema": {
          "description": "The schema field is exposed with every record",
          "format": "uri",
          "readOnly": true,
          "type": "string"
        },
        "self": {
          "$ref": "../_shared/dataverkennerbetrokkenbijbetrokkenbijlink"
        }
      },
      "required": [
        "schema",
        "self"
      ],
      "title": " links",
      "type": "object"
    },
    "betrokkenBijIdentificatie": {
      "description": "Identificatie van bovenliggende (gesplitste) A-percelen.",
      "type": [
        "string",
        "null"
      ]
    },
    "betrokkenBijKadastraleAanduiding": {
      "description": "De unieke aanduiding van bovenliggende (gesplitste) A-percelen.",
      "type": [
        "string",
        "null"
      ]
    },
    "betrokkenBijKadastraleobjectenId": {
      "description": "Id van bovenliggende (gesplitste) A-percelen.",
      "type": [
        "string",
        "null"
      ]
    },
    "betrokkenBijVolgnummer": {
      "description": "Volgnummer van bovenliggende (gesplitste) A-percelen.",
      "format": "int64",
      "maximum": 9223372036854776000,
      "minimum": -9223372036854776000,
      "type": [
        "integer",
        "null"
      ]
    },
    "id": {
      "type": "string"
    },
    "identificatie": {
      "description": "De unieke aanduiding van een Kadastraal object.",
      "type": "string"
    },
    "kadastraleAanduiding": {
      "description": "De unieke aanduiding van een Kadastraal Object samengesteld uit gemeentecode, kadastrale sectie, perceelnummer, indexletter en indexnummer.",
      "type": [
        "string",
        "null"
      ]
    },
    "neuronId": {
      "description": "Neuron ID",
      "format": "int64",
      "maximum": 9223372036854776000,
      "minimum": -9223372036854776000,
      "type": "integer"
    },
    "volgnummer": {
      "description": "Uniek volgnummer van de toestand van het object.",
      "format": "int64",
      "maximum": 9223372036854776000,
      "minimum": -9223372036854776000,
      "type": "integer"
    }
  },
  "required": [
    "_links",
    "id",
    "identificatie",
    "neuronId",
    "volgnummer"
  ],
  "type": "object",
  "x-derived-from": [
    "https://api.data.amsterdam.nl/v1/dataverkenner/betrokkenbijm/openapi.json#/components/schemas/DataverkennerBetrokkenbijmbetrokkenbij"
  ]
}

Schema gebruiken

JSON Schema

Bundled JSON Schema

Open in JSON Schema Viewer

Dependencies

Gebruikt door dit schema
Schema	Locatie
dataverkennerbetrokkenbijbetrokkenbijlink	`/properties/_links/properties/self/$ref`

Dit schema wordt gebruikt door
Schema	Locatie
embedded	`/properties/betrokkenbij/items/$ref`

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	`/properties/_links/description`
Titles should not contain leading or trailing whitespace	`/properties/_links/title`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/betrokkenBijIdentificatie/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/betrokkenBijKadastraleAanduiding/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/betrokkenBijKadastraleobjectenId/description`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/betrokkenBijVolgnummer/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/betrokkenBijVolgnummer/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/betrokkenBijVolgnummer/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/identificatie/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/kadastraleAanduiding/description`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/neuronId/format`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/neuronId/format`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/volgnummer/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/volgnummer/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/volgnummer/format`

Schema-register: dataverkennerbetrokkenbijmbetrokkenbij

Details van JSON Schema: dataverkennerbetrokkenbijmbetrokkenbij

Details van JSON Schema: dataverkennerbetrokkenbijmbetrokkenbij

Beschrijving