JSON schema to C and C++ mapping

"type":"null"
"type": []

Not supported

"$schema":"http://json-schema.org/draft-04/schema#"

This keyword is ignored, but it is assumed to be compatible with the draft 04 JSON Schema specification.

"title": "same text"
"description": "more text"

These keywords are ignored.

"format": "<predefined values>"

The "format" keyword is used to modify either the generated structure or runtime value. See the following information for the supported use of "format".

"type":
"array",
"items": {<JSON Sub-schema>},
"additionalItems": false,
"maxItems":m,
"minItems":n

Multidimensional arrays are supported from mapping level 4.3 or higher, and mixed type arrays are not supported.

"additionalItems" is assumed to be false, and no other value is supported.

If both "minItems" and "maxItems" are present, and they are equal, then the array is treated as fixed cardinality, otherwise it is treated as varying cardinality. See Variable arrays of elements in DFHJS2LS.

"type": "array",
"uniqueItems": true

"uniqueItems" is not supported with JSON arrays. The <JSON Sub-schema> must define a supported "type" , but that "type" cannot be "array" . This is a restriction on the language structure generated.

"type": "object",
"additionalProperties": false,
"properties": { [ "<element name>": {<JSON Sub-schema>} [,] ]* }
"required": [ [ "<element name>" [,] ]* ]

The only form of JSON object currently supported is a fixed set of named elements.

This will generate a structure (or sub-structure) using the element names.

"additionalProperties" is assumed to be false if a value is not set in the ADDITIONAL-PROPERTIES-DEFAULT parameter.

Any element in the "properties" object is considered "optional" if it is not in the "required" array or if no "required" array exists. An "optional" element is given a variable ordinality of zero to X; where X is either 1 or the maximum number of items in the array, where that item is defined as an array. See Variable arrays of elements in DFHJS2LS.

"type": "object",
"additionalProperties": true

If enabled, space is allocated up to the value specified in the ADDITIONAL-PROPERTIES-MAX parameter. The number of characters in each space is set by the ADDITIONAL-PROPERTIES-SIZE parameter. Each individual property is mapped to a PIC X(z) field where z is defined by the ADDITIONAL-PROPERTIES-SIZE parameter. If the value of ADDITIONAL-PROPERTIES-MAX is greater than 0 then the properties are mapped in an equivalent fashion to that of an array with maxItems set.

"type": "object",
"maxProperties": m,
"minProperties": n,
"patternProperties": {},
"dependencies":

None of these keywords are supported with JSON objects.

"type":"string"
"maxLength":m
"pattern": "regular expression>",
"minLength":l

char[ z ]

where the value of z is based on m , but dependent on the settings of the CHAR-VARYING parameter.

m is based on the "maxLength" keyword and treated as fixed length string.

"pattern" and "minLength" restrictions are passed through to the language structure only as a comment.

"type":"string"
"maxLength":m

When CCSID=1200 at mapping level 4.0 and higher:

char16_t[ z ]

where the value of z is based on m , but dependent on the settings of the CHAR-VARYING parameter.

m is based on the "maxLength " keyword and treated as fixed length string.

"*name*":{ 
     "type":"string",
   "format":"date-time"
          }

char[ 8 ]

All supported when DATETIME=PACKED15

"*name*":{ 
     "type":"string",
   "format":"uri"
          }

char[ m ]

where m is based on the "maxLength" keyword and treated as fixed length string.

When CCSID=1200 at mapping level 4.0 and higher:

char16_t[ m ]

where m is based on the "maxLength" keyword and treated as fixed length string.

"*name*":{ 
     "type":"string",
   "format":"base64Binary"
          }

char[ m ]

where m is based on the "maxLength" keyword.

"*name*":{ 
      "type":"string",
   "format":"hexBinary"
          }

char[ m ]

where m is based on the "maxLength" keyword.

"*name*":{ 
     "type":"string",
   "format":"<predefined>"
          }

char[ m ]

where m is based on the "maxLength" keyword and treated as fixed length string, and where <predefined> is one of: email , hostname , ipv4 or ipv6. A relevant "pattern" is used and passed to the comment.

When CCSID=1200 at mapping level 4.0 and higher:

char16_t[ m ]

where  m  is based on the "maxLength"  keyword and treated as fixed length string, and where  <predefined>  is one of:  email ,  hostname ,  ipv4 , or  ipv6 . A relevant "pattern" is used and passed to the comment.

"type":"boolean"

"type": "integer",
"exclusiveMaximum": true,
"exclusiveMinimum": true,
"multipleOf": n

"multipleOf" is ignored.

"type":"integer",
minimum:-128,
maximum:127

signed char

"type":"integer",
minimum:0,
maximum:255

unsigned char

"type":"integer",
minimum:-32768,
maximum:32767

short

"type":"integer",
minimum:0,
maximum:65535

unsigned short

"type":"integer",
minimum:-2147483648,
maximum:2147483647

int

"type":"integer",
minimum:0,
maximum:4294967295

unsigned int

"type":"integer",
minimum:-9223372036854775808,
maximum:9223372036854775807

long long

"type":"integer",
minimum:0,
maximum:18446744073709551615

unsigned long long

"type": "number",
"maximum": m,
"minimum": n,
"exclusiveMaximum": true,
"exclusiveMinimum": true,
"multipleOf": n

"maximum" , "minimum" , "exclusiveMaximum" and "exclusiveMinimum" restrictions are passed to the language structure only as a comment.

"multipleOf" is ignored.

"type":"number"
"format":"float"

"type":"number"
"format":"double"

oneOf: [ { "properties": { "A": {...} } } ,
    { "properties": { "B": {...} } } ]
anyOf: [ { "properties": { "A": {...} } } ,
    { "properties": { "B": {...} } } ]
allOf: [ { "properties": { "A": {...} } } ,
    { "properties": { "B": {...} } } ]

The logical paths through the array of options are merged together as though a single Object had been defined of type { "properties": { "A":..., "B":... } }. Each of the JSON properties is treated as optional. If the sub-options contain conflicting definitions for the same property name, an error message is issued; for example, if a single property is defined as both a String (in path A) and an Object (in path B), then such a definition is not supported and will result in an error message.

It is possible for a JSON schema to define complex logical structures; however, the subtleties implied in the complex logical structures might be lost in the mapping to a language structure. The transformation process does not attempt to enforce the combinatorial rules from the schema; it only interacts with the language structure fields that indicate whether a given JSON property is present or absent.

If the sub-options contain compatible definitions for the same property name, DFHJS2LS attempts to merge the associated pattern of constraints, though some subtleties might be lost in the process. For example, assume the following definition:

"A": { "oneOf": [ { "type": "string", "maxLength": 5}, {"type": "string", "minLength": 7, "maxLength": 8} ] }

A is defined as either a string up to 5 characters long or a string between 7 and 8 characters long. The merged composition might result in mappings to a string between 0 and 8 characters long, without recognizing that length of 6 characters is invalid.

Most scenarios involving logical composition will map to simple language structures, but complicated logical composition might result in compromises during the mapping process. For best results, avoid using logical composition in a JSON schema to define alternative declarations for the same JSON property.