JSON Schema reference

JSON Schema reference

Unknown Attachment

This section provides an in-depth reference to all JSON file types and validation keywords supported by UsageCloud, based on the official https://json-schema.org/.
It covers:

  • Official definitions and allowed values for each keyword and data type.

  • Full explanations of validation rules, interoperability, encoding, security, and advanced considerations.

  • How UsageCloud applies and interprets schema rules for comprehensive data integrity.

See:

Interoperability considerations

Validation in UsageCloud aligns with official JSON Schema specifications. Below is a list of considerations used by UsageCloud to maintain interoperability. No exceptions are made unless explicitly specified in the UsageCloud documentation, and you must enter the JSON Schema according to the official specifications found here:https://json-schema.org/draft/2020-12/json-schema-validation.

Validation consideration

Description

Validation consideration

Description

Validation of string instances

The null character (\u0000) is considered a valid JSON string.

Validation of numeric instances

The JSON Schema does not impose any bounds on numbers with arbitrary precision. Such instances can be arbitrarily large and/or can contain long decimal parts.

Regular expressions

The use of keywords that utilize regular expressions or constrain the value to such an expression should conform to the core JSON Schema specifications.

Meta-schemes

The latest JSON Schema dialect meta-schema release specifications are supported.

Note!
All JSON Schema keywords apply at the schema location where they are defined. If a keyword is included in multiple places within your schema, it independently affects validation or annotation at each of those locations.

Additional reading

For more information, see the following documents: