community

The JSON Schema organization is looking for honest feedback on how we can make our Community Working Meetings and Office Hours more engaging with the community. We would love to see new recurrent faces in there to help improve JSON Schema. Did you attend an Office Hours or Open Community Working Meeting in the last 12 months? If so, please fill in this 1 minute survey to help us improve! https://docs.google.com/forms/d/e/1FAIpQLSenQIBMSQ1LZ2Y5Ar-35FgL9q3KQ9Y3dyHiDwljbj… You can also find a record of this discussion here: https://github.com/json-schema-org/community/issues/566

> the json response from APIs don't have json schema defined for you. But you could define schema from their api documentation, right? Yes exactly. > it's been in draft for a decade https://json-schema.org/blog/posts/future-of-json-schema#sta... https://github.com/json-schema-org/community/discussions/69 I can see they're working on this issue. Hopefully they get it resolved sooner rather than later.

At crossref.org we are building out a form-based application using this library, and also working on the development of the VueJS/Vuetify renderer set https://github.com/eclipsesource/jsonforms-vuetify-renderers. The UISchema is a compromise, and I think that largely is a result of the limitations of JSON Schema when applied to form generation - it's good, but it's not perfect. There is an open discussion on the JSON Schema GH about creating a custom JSON Schema vocabulary for form generation, which could answer some of these limitations https://github.com/json-schema-org/community/discussions/70