Ben Hutton

We discussed this on OCWM call https://github.com/json-schema-org/community/issues/133 Rather than relicencing, we woundered if it was preferable to add the licenses already mentioned to a licence file. Basec on the above,...

Related: https://github.com/json-schema-org/json-schema-spec/issues/532

Sorry it has taken so long to get an update on this. My email got lost in the ether. I had a breif chat with Brian from the OpenJS Foundation,...

Response from OpenJS Foundation is as follows: > I connected with counsel on this. Here’s the recommendation. > > “I suggest adding a license file that makes clear that the...

The meta-schema is still used to validate a given schema, and it will check for the correct formatting of that value. However, it has no implications. "Ignored" in the sense...

Yes yes! Immediate action!

I've seen people trip over this more than a few times.

Yeah, I noticed the issue around how `default` as an annotation will not be collected if the property doesn't exist. I feel this IS the correct behaviour. I would suggest...

> It's ironic that `{"not":{"required”:[...]}}` doesn't do this... I've seen people trying to do it this way though. `not` is often confused.

> The best suggestion I have is `requireAllExcept`. I agree this is the best we have. I suggest we leave it open for a week, and barign further comments, call...