fge / sample-json-schemas Goto Github PK
View Code? Open in Web Editor NEWSample JSON Schemas
Sample JSON Schemas
No definitions for:
MultiPoint
MultiLineString
MultiPolygon
How difficult would it be to write a schema for http://json-stat.org/format/ ?
Maybe my parser is not correct, but to get my code to parse some of the schema I had to make a few changes, shown below. I honestly did not try to understand the details of these schema, but was just trying to grab some valid schema on the net to pass through a visualizer I'm working on. These schema and a couple more can be viewed at: https://github.com/patefacio/json_schema/tree/master/dot_samples/schemaout
Hopefully these changes are helpful, but I'm not sure.
diff dot_samples/original/avro-schema.json dot_samples/schemas/avro-schema.json
32,33c32,33
< "name": { "$ref": "#/definitions/nameOrNamespace" },
< "nameOrNamespace": { "$ref": "#/definitions/namespace" },
---
> "name": { "$ref": "#/definitions/name" },
> "nameOrNamespace": { "$ref": "#/definitions/nameOrNamespace" },
48,49c48,49
< "name": { "$ref": "#/definitions/nameOrNamespace" },
< "nameOrNamespace": { "$ref": "#/definitions/namespace" },
---
> "name": { "$ref": "#/definitions/name" },
> "nameOrNamespace": { "$ref": "#/definitions/nameOrNamespace" },
101,102c101,102
< "name": { "$ref": "#/definitions/nameOrNamespace" },
< "nameOrNamespace": { "$ref": "#/definitions/namespace" },
---
> "name": { "$ref": "#/definitions/name" },
> "nameOrNamespace": { "$ref": "#/definitions/nameOrNamespace" },
110a111,115
> "name": {
> "description": "what a name can be",
> "type": "string",
> "pattern": "^[A-Za-z_][A-Za-z0-9_]*$"
> },
bash-3.2$ diff dot_samples/original/json-home.json dot_samples/schemas/json-home.json
95c95
< "uniqueItems": "true",
---
> "uniqueItems": true,
102c102
< "uniqueItems": "true",
---
> "uniqueItems": true,
114c114
< "uniqueItems": "true",
---
> "uniqueItems": true,
bash-3.2$ diff dot_samples/original/crs.json dot_samples/schemas/crs.json
32c32
< "linkObject": {
---
> "linkedObject": {
47c47
< "linkedCRS": {
---
> "linkedCrs": {
According to the examples on the JSON RPC 2.0 Specification, an empty array is not a valid request, but using the jsonrpc-request-2.0.json
schema in the json-schema-validator-demo yields 'success'.
Same thing with an empty array response (see the last paragraph of the Batch section of the spec).
Is this still the 'definitive' schema for GeoJSON (as of Sep.2017)?
Hi, these items need addressing in the schemas:
Request: This needs to be either a single instance of the current definition, or an unbound array of such objects (batch). Other than that I think it looks good.
Response: Result can be any type, not just an object. Same thing about batch, and needing to be an instance or an array of instances.
Handling in general should be to use the confirm the object shape, but not exclude any additional data fields.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.