Lines Matching refs:data
5 It comes with a schema-driven script tool that can validate your data, or even generate code.
8 The validation and conversion part of the tool works with YAML and JSON data, in addition to CBOR.
12 …CBOR encoding and decoding using the C library, while also validating the data against all the rul…
14 …DDL (Concise Data Definition Language) which is a powerful human-readable data description languag…
28 - Decode and validate incoming CBOR data into human-readable YAML/JSON.
41 …ther with generated code, and how to use the script tool to do code generation and data conversion.
73 …ecoding_ if there are any lists, maps, or CBOR-encoded strings (`zcbor_bstr_*_decode`) in the data.
100 …. When decoding, if `enforce_canonical` is true, ensure that the incoming data conforms to canonic…
111 The zcbor.py script can directly read CBOR, YAML, or JSON data and validate it against a CDDL descr…
112 It can also freely convert the data between CBOR/YAML/JSON.
113 It can also output the data to a C file formatted as a byte array.
120 …alized examples for validating, and for converting (which also validates) data from the command li…
121 The script infers the data format from the file extension, but the format can also be specified exp…
125 zcbor validate -c <CDDL description file> -t <which CDDL type to expect> -i <input data file>
126 …c <CDDL description file> -t <which CDDL type to expect> -i <input data file> -o <output data file>
132 …or/zcbor.py validate -c <CDDL description file> -t <which CDDL type to expect> -i <input data file>
133 …c <CDDL description file> -t <which CDDL type to expect> -i <input data file> -o <output data file>
140 DataTranslator can be used to programmatically perform the translations, or to manipulate the data.
141 When accessing the data, you can choose between two internal formats:
147 2. A custom format which allows accessing the data via the names from the CDDL description file.
148 … immutable, meaning that it can be used for inspecting data, but not for changing or creating data.
153 Since CBOR supports more data types than YAML and JSON, zcbor can optionally use a bespoke format w…
155 This is relevant when handling YAML/JSON conversions of data that uses the unsupported features.
156 The following data types are supported by CBOR, but not by YAML (or JSON which is a subset of YAML):
158 …tr": <any type>}` if the CBOR bytestring contains CBOR-formatted data, in which the data is decode…
160 …`. In YAML, these are represented as `{"zcbor_tag": <tag number>, "zcbor_tag_val": <tagged data>}`.
177 …ates code that uses the C library to decode CBOR data into the structs, and/or encode CBOR from th…
190 CDDL allows placing restrictions on the members of your data.
244 …gainst the Pet type in the CDDL description in pet.cddl, and writes binary CBOR data to mypet.cbor.
310 …g. `Foo = bstr .cbor Bar` where Foo is a bstr whose contents must be CBOR data decodable as the Ba…
322 The label is only for readability and does not impact the data structure in any way.
351 Encoded CBOR data elements look like this.
395 It was inspired by the need to securely decode the complex manifest data structures in the [IETF SU…
397 Decoding/deserializing data securely requires doing some quite repetitive checks on each data eleme…
400 The script was also expanded so it could directly manipulate CBOR data.
401 … in roughly the same way internally in Python, it was easy to expand that data manipulation to sup…
558 Read CBOR, YAML, or JSON data from file or stdin and validate it against a
571 Input data file. The option --input-as specifies how
579 Name of the type (from the CDDL) to interpret the data
583 is specified. It is only relevant when handling data
589 data is guaranteed to convert into YAML/JSON. JSON and
590 YAML do not support all data types that CBOR/CDDL
610 decodes the CBOR/YAML/JSON data from a file or stdin and verifies that it
611 conforms to the CDDL description. The script fails if the data does not
624 Input data file. The option --input-as specifies how
632 Name of the type (from the CDDL) to interpret the data
636 is specified. It is only relevant when handling data
642 data is guaranteed to convert into YAML/JSON. JSON and
643 YAML do not support all data types that CBOR/CDDL
648 Output data file. The option --output-as specifies how