Home
last modified time | relevance | path

Searched +full:json +full:- +full:schema (Results 1 – 25 of 787) sorted by relevance

12345678910>>...32

/openbmc/linux/Documentation/devicetree/bindings/
H A Dwriting-schema.rst1 .. SPDX-License-Identifier: GPL-2.0
3 Writing Devicetree Bindings in json-schema
6 Devicetree bindings are written using json-schema vocabulary. Schema files are
7 written in a JSON-compatible subset of YAML. YAML is used instead of JSON as it
11 Also see :ref:`example-schema`.
13 Schema Contents
14 ---------------
16 Each schema doc is a structured json-schema which is defined by a set of
17 top-level properties. Generally, there is one binding defined per file. The
18 top-level json-schema properties used are:
[all …]
/openbmc/phosphor-logging/extensions/openpower-pels/registry/tools/
H A Dvalidate_registry.py4 import json
8 Validates the PEL message registry JSON, which includes checking it against
9 a JSON schema using the jsonschema module as well as doing some extra checks
10 that can't be encoded in the schema.
20 registry_json: The message registry JSON
36 registry_json: The message registry JSON
57 registry_json: The message registry JSON
87 registry_json: The message registry JSON
113 def validate_schema(registry, schema): argument
115 Validates the passed in JSON against the passed in schema JSON
[all …]
/openbmc/qemu/storage-daemon/qapi/
H A Dqapi-schema.json1 # -*- Mode: Python -*-
4 # Note that modules are shared with the QEMU main schema under the assumption
5 # that the storage daemon schema is a subset of the main schema. For the shared
7 # from the main schema.
9 # If you wish to extend the storage daemon schema to contain things that are
10 # not in the main schema, be aware that array types of types defined in shared
12 # in the main schema. Therefore, if you use such arrays, you may need to define
13 # the array type in the main schema, even if it is unused outside of the
16 { 'include': '../../qapi/pragma.json' }
18 # Documentation generated with qapi-gen.py is in source order, with
[all …]
/openbmc/entity-manager/schemas/
H A Dglobal.json2 "$schema": "http://json-schema.org/draft-07/schema#",
5 "description": "The exposes property element schema. An element of the exposes property is always an array where elements are of type exposes entry.",
8 "$ref": "ibm.json#/$defs/PowerModeProperties"
11 "$ref": "ibm.json#/$defs/IBMCompatibleSystem"
14 "$ref": "ibm.json#/
[all...]
H A DREADME.md1 # Entity manager configuration file schema
3 Entity manager configuration files are JSON documents and can be validated with
4 a [JSON schema][1]. This document provides an overview of the general structure
8 configurations. This provides flexibility for system designers - the
11 most schema describes a single object or an array of objects.
14 entity manager configuration file and schema file names must be
30 supported types, consult the schema (global.json).
37 interfaces listed in openbmc-dbus.json will be added on
49 Each exposes element has its own schema which is outlined by the subschemas in
50 the schemas directory. Each schema must require a type and name (not to be
[all …]
/openbmc/bmcweb/redfish-core/lib/
H A Dredfish_v1.hpp1 // SPDX-License-Identifier: Apache-2.0
2 // SPDX-FileCopyrightText: Copyright OpenBMC Authors
41 asyncResp->res.jsonValue["v1"] = "/redfish/v1/"; in redfishGet()
48 asyncResp->res.addHeader(boost::beast::http::field::allow, ""); in redfish404()
63 messages::resourceNotFound(asyncResp->res, "", name); in redfish404()
78 asyncResp->res.result(boost::beast::http::status::method_not_allowed); in redfish405()
81 messages::resourceCannotBeDeleted(asyncResp->res); in redfish405()
85 messages::operationNotAllowed(asyncResp->res); in redfish405()
97 nlohmann::json& json = asyncResp->res.jsonValue; in jsonSchemaIndexGet() local
98 json["@odata.id"] = "/redfish/v1/JsonSchemas"; in jsonSchemaIndexGet()
[all …]
/openbmc/libcper/tests/
H A Dtest-utils.cpp2 * Defines utility functions for testing CPER-JSON IR output from the cper-parse library.
11 #include "test-utils.hpp"
14 #include <libcper/generator/cper-generate.h>
19 // validating the entire schema with validationbits=1
22 { "./sections/cper-arm-processor.json",
24 { "./cper-json-section-log.json", { "header" } },
25 { "./sections/cper-cxl-protocol.json",
27 { "./sections/cper-generic-dmar.json",
29 { "./sections/cper-cxl-component.json",
33 nlohmann::json loadJson(const char *filePath) in loadJson()
[all …]
/openbmc/phosphor-power/phosphor-regulators/tools/
H A Dvalidate-regulators-config.py4 import json
11 Validates the phosphor-regulators configuration file. Checks it against a JSON
12 schema as well as doing some extra checks that can't be encoded in the schema.
22 Finds all occurrences of a key within the specified JSON element and its
24 To search the entire configuration file, pass the root JSON element
25 json_element: JSON element within the config file.
48 config_json: Configuration file JSON
59 config_json: Configuration file JSON
72 config_json: Configuration file JSON
110 config_json: Configuration file JSON
[all …]
/openbmc/openpower-hw-diags/test/
H A Dtest-util-data-file.cpp10 using json = nlohmann::json; typedef
18 auto regexPattern = R"(openpower\-hw\-diags\-.*)"; in TEST()
56 // The json object that is used as schema for other json objects. in TEST()
58 // ./analyzer/ras-data/schema/ras-data-schema-v01.json in TEST()
59 json schema_obj = R"({ in TEST()
60 "$schema": "https://json-schema.org/draft/2020-12/schema", in TEST()
61 "title": "RAS Data schema for openpower-hw-diags", in TEST()
69 "pattern": "^[0-9A-Fa-f]{8}$" in TEST()
78 // The json objects
80 // ./analyzer/ras-data/data/ras-data-p10-20.json
[all …]
/openbmc/libcper/specification/json/
H A Dcper-json.json2 "$id": "cper-json",
3 "$schema": "https://json-schema.org/draft/2020-12/schema",
4 …"description": "JSON Schema for the CPER-JSON format, as described in the CPER-JSON specification …
7 { "$ref": "./cper-json-full-log.json" },
8 { "$ref": "./cper-json-section-log.json" }
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A DJsonSchemaFile.v1_1_5.json2 "$id": "http://redfish.dmtf.org/schemas/v1/JsonSchemaFile.v1_1_5.json",
4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
37 …ription": "The `JsonSchemaFile` schema contains the properties that describe the locations, as URI…
38 …"longDescription": "This resource shall represent the schema file locator resource for a Redfish i…
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
55 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/context"
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DJsonSchemaFile.v1_1_5.json2 "$id": "http://redfish.dmtf.org/schemas/v1/JsonSchemaFile.v1_1_5.json",
4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
37 …ription": "The `JsonSchemaFile` schema contains the properties that describe the locations, as URI…
38 …"longDescription": "This resource shall represent the schema file locator resource for a Redfish i…
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
55 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/context"
[all …]
H A DMediaControllerCollection.json2 "$id": "http://redfish.dmtf.org/schemas/v1/MediaControllerCollection.json",
4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
10 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/idRef"
17 … "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
32 … "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/context"
35 … "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/etag"
38 … "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/id"
41 … "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/type"
46 … "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Description"
[all …]
/openbmc/bmcweb/scripts/csdl-to-json-converter/
H A DREADME.md1 # Generating Json schema for OEM schemas
3 The config in this directory is for utilizing the DMTF json generation script
10 …-Tools/csdl-to-json-convertor/csdl-to-json.py --input ~/bmcweb/redfish-core/schema/oem/openbmc/csd…
14 https://github.com/DMTF/Redfish-Tools/blob/main/csdl-to-json-convertor/csdl-to-json.py
H A Dopenbmc-config.json3 "RedfishSchema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
4 "ODataSchema": "http://redfish.dmtf.org/schemas/v1/odata-v4.json",
5 …ion": "https://github.com/openbmc/bmcweb/tree/master/redfish-core/schema/oem/openbmc/json-schema/",
6 …ion": "https://github.com/openbmc/bmcweb/tree/master/redfish-core/schema/oem/openbmc/json-schema/",
/openbmc/qemu/docs/devel/
H A Dqapi-code-gen.rst7 Copyright (C) 2012-2016 Red Hat, Inc.
10 later. See the COPYING file in the top-level directory.
16 QAPI is a native C API within QEMU which provides management-level
18 users/processes, this interface is made available by a JSON-based wire
21 The remainder of this document uses "Client JSON Protocol" when
24 To map between Client JSON Protocol interfaces and the native C API,
25 we generate C code from a QAPI schema. This document describes the
26 QAPI schema language, and how it gets mapped to the Client JSON
28 Client JSON Protocol compatibility.
31 The QAPI schema language
[all …]
/openbmc/openpower-hw-diags/analyzer/ras-data/
H A Dmeson.build5 'data/ras-data-explorer-11.json',
6 'data/ras-data-explorer-20.json',
7 'data/ras-data-odyssey-10.json',
8 'data/ras-data-p10-10.json',
9 'data/ras-data-p10-20.json',
12 install_data(ras_data_files, install_dir: join_paths(package_dir, 'ras-data'))
14 # Install the RAS data schema
16 ras_data_schema = files('schema/ras-data-schema-v02.json')
18 install_data(ras_data_schema, install_dir: join_paths(package_dir, 'schema'))
/openbmc/bmcweb/redfish-core/schema/oem/openbmc/json-schema/
H A DOpenBMCComputerSystem.v1_0_0.json2 …ub.com/openbmc/bmcweb/tree/master/redfish-core/schema/oem/openbmc/json-schema/OpenBMCComputerSyste…
3 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
10 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
27 …github.com/openbmc/bmcweb/tree/master/redfish-core/schema/oem/openbmc/json-schema/OpenBMCComputerS…
53 …"ProvisionedAndLocked": "Platform firmware is provisioned and locked. So re-provisioning is not al…
54 …"ProvisionedButNotLocked": "Platform firmware is provisioned but not locked. So re-provisioning is…
62 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
79 …github.com/openbmc/bmcweb/tree/master/redfish-core/schema/oem/openbmc/json-schema/OpenBMCComputerS…
93 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
H A DOpenBMCVirtualMedia.json2 …/github.com/openbmc/bmcweb/tree/master/redfish-core/schema/oem/openbmc/json-schema/OpenBMCVirtualM…
3 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
/openbmc/qemu/tests/qapi-schema/
H A Dmeson.build3 test_env.set('PYTHONIOENCODING', 'utf-8')
6 'alternate-any.json',
7 'alternate-array.json',
8 'alternate-base.json',
9 'alternate-branch-if-invalid.json',
10 'alternate-clash.json',
11 'alternate-conflict-dict.json',
12 'alternate-conflict-enum-bool.json',
13 'alternate-conflict-enum-int.json',
14 'alternate-conflict-lists.json',
[all …]
/openbmc/entity-manager/scripts/
H A Dvalidate_configs.py2 # SPDX-License-Identifier: Apache-2.0
7 import json
14 DEFAULT_SCHEMA_FILENAME = "global.json"
19 # second group captures comments (//single-line or /* multi-line */)
37 "-s",
38 "--schema",
40 "Use the specified schema file instead of the default "
41 "(__file__/../../schemas/global.json)"
45 "-c",
46 "--config",
[all …]
/openbmc/phosphor-logging/extensions/openpower-pels/registry/
H A DREADME.md4 phosphor-logging using a message registry that provides the PEL related fields.
5 The message registry is a JSON file.
9 - [Component IDs](#component-ids)
10 - [Message Registry](#message-registry-fields)
11 - [Modifying and Testing](#modifying-and-testing)
30 Component IDs will be unique on a per-repository basis for errors unique to that
33 [here](O_component_ids.json). That file can used by PEL parsers to display a
39 The message registry schema is [here](schema/schema.json), and the message
40 registry itself is [here](message_registry.json). The schema will be validated
50 ```json
[all …]
/openbmc/libcper/specification/json/sections/
H A Dcper-generic-dmar.json2 "$schema": "https://json-schema.org/draft/2020-12/schema",
42 "$ref": "./common/cper-json-nvp.json"
47 "$ref": "./common/cper-json-nvp.json"
51 "description": "Either VT-d or IOMMU",
52 "$ref": "./common/cper-json-nvp.json"
56 "description": "The 64-bit device virtual address in the faulted DMA request"
/openbmc/libcper/
H A Djson-schema.c2 * A very basic, non-complete implementation of a validator for the JSON Schema specification,
3 * for validating CPER-JSON.
14 #include <json.h>
15 #include <libcper/json-schema.h>
21 //Private pre-definitions.
22 int validate_field(const char *name, json_object *schema, json_object *object,
24 int validate_integer(const char *field_name, json_object *schema,
26 int validate_string(const char *field_name, json_object *schema,
28 int validate_object(const char *field_name, json_object *schema,
30 int validate_array(const char *field_name, json_object *schema,
[all …]
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/json-schema-validator/json-schema-validator/
H A D0003-For-root-value-use-empty-pointer.patch6 Upstream-Status: Backport [https://github.com/pboettch/json-schema-validator/commit/59c9d6200bf3cd5…
8 Signed-off-by: Parian Golchin <Parian.Golchin@iris-sensing.com>
9 ---
10 src/json-validator.cpp | 8 ++++++++
13 diff --git a/src/json-validator.cpp b/src/json-validator.cpp
15 --- a/src/json-validator.cpp
16 +++ b/src/json-validator.cpp
17 @@ -553,6 +553,9 @@ class type_schema : public schema
18 else_->validate(ptr, instance, patch, e);
22 + patch.add(nlohmann::json::json_pointer{}, default_value_);
[all …]

12345678910>>...32