relequestual
Joined 15 years ago
Karma
125
Submissions
53
Member since
Feb 16
Recent submissions
Comment · 11 months ago
The JSON Schema community would LOVE some more detailed feedback on this.
We would ideally like to do that in our slack or via a GitHub Discussion. Can you reach either of those OK? Please ping/mention me, same username.
Comment · 3 years ago
The team at JSON Schema finally got access to deeper network traffic analytics via CloudFlare. We knew there were lots of requests being made, but details were limited. We dive into the data and make some interesting discoveries.
Comment · 3 years ago
We (JSON Schema) did a case study/interview with the guy behind it https://www.youtube.com/watch?v=-yYTxLZZk58&list=PLHVhS4Tj1Y...
Comment · 3 years ago
Here's a YouTube playlist of 6 case studies with companies of various sizes: https://www.youtube.com/watch?v=fkziMQD7pqQ&list=PLHVhS4Tj1Y...
There are also two written case studies on the JSON Schema blog: https://json-schema.org/blog/
Comment · 3 years ago
It is not =]
Additionally, the value is a "schema" as opposed to a boolean, meaning you can apply a subschema to any additional fields. Useful if you for instance want to make sure any additional fields start with a specific prefix.
Booleans are valid schemas. It's subschemas all the way down! I wrote an article around this topic: https://json-schema.org/blog/posts/applicability-json-schema...
Comment · 3 years ago
Part of the problem is they wrote that site and its content for a specific version of JSON Schema.
The `items` keyword no longer takes an array form value in the latest version of the specification, while their documentation shows that it does.
I seem to recall other issues, but can't find them now. We may have raised issues which were resolved, but I don't recall the specifics.
Comment · 3 years ago
Actually, currently, this is not the case.
The specification explicitly allows for additional fields for the purposes of extensions.
We are considering changing that, and only allowing pre-defined fields, or having a way to mark specific fields as limited extensions.
Comment · 3 years ago
A project exists which does this, and the team even support its development: https://github.com/sourcemeta/alterschema
Personally, I'd like to see it become officially supported. We have work to do!
Comment · 3 years ago
Thanks for sharing. This is useful commentary to see.
We try to be helpful to maintainers. If any have questions, the JSON Schema server has an implementers channel!
We would like to be able to support implementers financially, but we need other companies to add their support in order to do that.
And for that, we need to better communicate our value proposition. We're working on it!
Comment · 3 years ago
The OP actually created a tool that allows you to upgrade your schemas between versions of JSON Schema. It's pretty neat, and has had the eyes of those who write the spec.
https://github.com/sourcemeta/alterschema