Juan Cruz Viotti

Right. The issue might be coming from Chromium then, which both Google Chrome and Postman uses (through Electron). Assigning to @dsanders11 to investigate further.

@json-schema-org/docs-team @json-schema-org/tsc Can you help with your own reviews for this blog post? @agilevic and I have been talking for a while and SlashDB is a very nice "database gateway"...

No worries. Feel free to ignore that check. But let me ping the team again for reviews

Hey @erosb, thanks for suggesting this! Just some misc notes: - The project that implements the validator is https://github.com/sourcemeta/blaze. The JSON Schema CLI just offers a simple opinionated interface to...

> I don't have any input about the mapping overhead. Probably this heavily depends on the complexity of the schema and the size of the instance. If it turns out...

I think the options that were discussed in the call were: - Either the implementations made/maintained by the TSC, under the argument that a TSC member either knows what they...

I'm very interested in the outcome of this to improve my own validator. Let me know if I can help in any way

I love this, and I think it has some interesting overlap with my linting proposal: https://github.com/json-schema-org/community/issues/856. The things that should be normalised can make very good linting rules that we...

I personally like the idea and happy to volunteer to mentor them, being involved in the workshops (remotely), and guide them on contributions to either the org or any Sourcemeta...

Thanks for putting this issue together! If you need any help from me (as I plan to be there for the entire conference), just let me know.