JSONtext: JSON Schema?

[drjdpowell]

It's been suggested that I think about adding a basic JSON validation schema capability to JSONtext.  What do people think?  

An example:

{
  "type": "object",
  "properties": {
    "number": { "type": "number" },
    "street_name": { "type": "string" },
    "street_type": { "enum": ["Street", "Avenue", "Boulevard"] }
  }
}

[Thoric]

Would you interpret the schema during parsing, on demand, or just include it for the developer's benefit?

[drjdpowell]

---

@Thoric wrote:

Would you interpret the schema during parsing, on demand, or just include it for the developer's benefit?

---

There would be a new "Validate JSON Schema" VI, that would have inputs for both a JSON Schema, and a JSON Value to validate (ie. it is used on demand).  Would return "Valid" T/F, and hopefully reason for it not being valid.

A JSON Schema can specify things like "must include certain items", or "'Temperature' must be a number", or "'Position' must be an array of three numbers". 

[drjdpowell]

Could also have a "Generate JSON Schema from LV Datatype" subVI, that would generate the Schema from an input type (including things like cluster names and types, and enum values).  This could be used be a programmer in a different language to validate that their JSON is in the right form to be understood in LabVIEW.

[Thoric]

I have to say, these sound clever and potentially useful. Although I don't have a user case today it's not impossible in the future.

[ross.smyth]

I love JSON Schema and would love this feature to more easily validate configuration files.

[StefanLemmens]

This would be a great feature. Any plans to actually add this in the near future to the toolkit?

[lucian.grec]

I'd like this very much as well

[drjdpowell]

Here is a beta version with JSON Schema.  See the example "JSON Schema Validation".

[StefanLemmens]

Thanks James for adding this.

It would be nice if the "Failure Reason" would also contain the label of the element that failed.

Best Regards,

Stefan