jsonschema

Apache Avro provides a compact, fast, binary data format, rich data structure for serialization. However, it requires user to define a schema (in JSON) for object which need to be serialized. In some case, this can not be possible (e.g: the class of that Java object has some members whose types are external java classes in external libraries). Hence, I wonder there is a tool can get the information from object's .class file and generate the Avro schema for that object (like Gson use object's .class information to convert certain object to JSON string). MoustafaAAtta Take a look at the Java

Is there any way to programmatically generate a JSON schema from a C# class? Something which we can do manually using http://www.jsonschema.net/ Another option which supports generating JSON Schema v4 is NJsonSchema : var schema = JsonSchema4.FromType<Person>(); var schemaJson = schema.ToJson(); The library can be installed via NuGet . Update for NJsonSchema v9.4.3+: using NJsonSchema; var schema = await JsonSchema4.FromTypeAsync<Person>(); var schemaJson = schema.ToJson(); For those who land here from google searching for the reverse (generate the C# class from JSON) - I use those fine online

I was told recently that a proper RESTful API should define a schema for the resources representations it accepts and returns. For example XSD for XML and JSON Schema for JSON. However in all the books and articles on REST I went through this has never seem not only prominent, but even mentioned. Could someone provide some authoritative resources, to clarify if we should be providing schema when developing RESTful APIs? You have to define and communicate the request and response interfaces to your RESTful API somehow so that callers know what you expect in the request and what they can expect

I have Swagger API Declaration for services using Swagger v 1.2 My original feeling about Swagger was, that it is very close to JSON Schema (Draft 3 and lately Draft 4) and it shall be relatively easy to generate JSON Schema for request and response objects. However, while part of the Swagger reuses JSON Schema structures, it turned out, it uses only subset of features, and it also introduces it's own inheritance in Models (using subTypes and discriminator ) . Question: Is there any existing project or piece of code, which can generate usable JSON Schema from Swagger API Declaration ?

I am new to this json schema , i am able to write json schema if it has only one data set like below { "employees": [ { "id": 1, "name": "aaa" } } example json-schema for this is { "type" : "object", "required" : ["employees"], "properties" : { "employees" : { "type" : "Array", "items" : [ "properties" : { "id" : {"type" : "integer"}, "name" : {"type" : "string"}, }, "required" : ["id","name"] ] } } } but i got stuck to write json schema in ruby if we have multiple data sets { "employees": [ { "id": 1, "name": "aaa" }, { "id": 2, "name": "bbb" }, { "id": 3, "name": "cccc" }, { "id": 4, "name":

I have the following JSON schema that I want to validate and Python unittest. { "properties": { "traffic_parameters" { "capacity": { "oneOf": [ { "max_percentage": { "type": "integer", "minimum" : 1, "maximum" : 150 }, "min_percentage": { "type": "integer", "minimum" : 1, "maximum" : { "$ref": "#/properties/traffic_parameters/capacity/oneOf/max_percentage/minimum" } } }, { "percentage_range": { "type": "array", "minItems": 1, "maxItems": 10, "items": { "type": "integer" } } } ] } } } } Using jsonschema I validate the whole schema file OK. However, on writing unittests I get the following error

I have an object (from a 3rd party, so I can't change it) that have a property named "key", and another property called "value" that is optional, and it's type depends on the value of the "key" property. For instance: If the key is "comment", the type of value {"Text":"commentValue"} . If the key is "offset", the type of value is {"seconds":int} . If the key is "weather", the type of value is {"value": Enum["sun", "clouds", "rain"...]} Moreover, some of the keys do not have the value property, so the schema should forbid it from appearing with these keys. one of these keys is "standby" (as you