vhwdebugger-binding.yaml
Configuration of the Vector CANoe hardware debugger binding
vhwdebugger-binding.yaml*.vhwdebugger-binding.yamlvhwdebugger-binding.yml*.vhwdebugger-binding.yml
Validate
Check your file against this schema
Opens the validator with this schema already loaded. Paste your
vhwdebugger-binding.yaml and it validates in your browser — nothing is uploaded.
Reference
Fields
Generated directly from the schema, following local
$refs, to two levels of nesting.
| Field | Type | Description |
|---|---|---|
versionrequired | string | The version of the configuration. Controls what features are available |
default-debugger | string | The default debugger if a distributed object is not assigned explicitly. Must reference an element from the `debuggers` list |
debuggersrequired | object | List of all configured debuggers. The elements' key determines the name of the debugger |
versionrequired | string | The version of the configuration. Controls what features are available |
default-debugger | string | The default debugger if a distributed object is not assigned explicitly. Must reference an element from the `debuggers` list |
debuggersrequired | object | List of all configured debuggers. The elements' key determines the name of the debugger |
versionrequired | string | The version of the configuration. Controls what features are available |
default-debugger | string | The default debugger if a distributed object is not assigned explicitly. Must reference an element from the `debuggers` list |
debuggersrequired | object | List of all configured debuggers. The elements' key determines the name of the debugger |
Audit
What we found in this schema
- Declared draft: draft-07
- Validates cleanly against its own meta-schema.
- Has 1 place(s) where keywords sit beside
$ref. Under draft-07 those keywords are silently ignored by every conforming validator — first at#. - Uses non-standard keywords that generic validators ignore:
annotations. - 106 properties, 89% carrying a description, max nesting depth 18.
Standards
Specification sections for the keywords in this schema
| Keyword | Document | Section |
|---|---|---|
$comment | JSON Schema Core, draft 2020-12 | §8.3 — Comments With "$comment" |
$ref | JSON Schema Core, draft 2020-12 | §8.2.3.1 — Direct References with "$ref" |
$schema | JSON Schema Core, draft 2020-12 | §8.1.1 — "$schema" |
additionalProperties | JSON Schema Core, draft 2020-12 | §10.3.2.3 — "additionalProperties" |
const | JSON Schema Validation, draft 2020-12 | §6.1.3 — "const" |
default | JSON Schema Validation, draft 2020-12 | §9.2 — "default" |
description | JSON Schema Validation, draft 2020-12 | §9.1 — "title" and "description" |
examples | JSON Schema Validation, draft 2020-12 | §9.5 — "examples" |
maximum | JSON Schema Validation, draft 2020-12 | §6.2.2 — "maximum" |
minLength | JSON Schema Validation, draft 2020-12 | §6.3.2 — "minLength" |
minProperties | JSON Schema Validation, draft 2020-12 | §6.5.2 — "minProperties" |
minimum | JSON Schema Validation, draft 2020-12 | §6.2.4 — "minimum" |
oneOf | JSON Schema Core, draft 2020-12 | §10.2.1.3 — "oneOf" |
pattern | JSON Schema Validation, draft 2020-12 | §6.3.3 — "pattern" |
patternProperties | JSON Schema Core, draft 2020-12 | §10.3.2.2 — "patternProperties" |
properties | JSON Schema Core, draft 2020-12 | §10.3.2.1 — "properties" |
required | JSON Schema Validation, draft 2020-12 | §6.5.3 — "required" |
type | JSON Schema Validation, draft 2020-12 | §6.1.1 — "type" |
Documents
- JSON Schema Core, draft 2020-12 — JSON Schema: A Media Type for Describing JSON Documents, A. Wright, H. Andrews, B. Hutton, G. Dennis, Eds., 2022. draft-bhutton-json-schema-01. An expired Internet-Draft with no formal standing in the IETF standards process; it is nonetheless the specification of record for JSON Schema 2020-12, published by json-schema.org.
- JSON Schema Validation, draft 2020-12 — JSON Schema Validation: A Vocabulary for Structural Validation of JSON, A. Wright, H. Andrews, B. Hutton, Eds., 2022.
- RFC 8259 (STD 90) — The JavaScript Object Notation (JSON) Data Interchange Format, T. Bray, Ed., 2017. The format a schema describes.
- RFC 6901 — JavaScript Object Notation (JSON) Pointer. Defines the pointer syntax used by $ref fragments and the ~0 / ~1 escapes.
Source
Attribution
This schema comes from SchemaStore, distributed under the Apache License 2.0. Copyright 2015–present Mads Kristensen and contributors. View the original file. The field table and audit on this page are generated by JSONTools.tools; the schema itself is unmodified.