fdutton

Closed due to the lack of response from the OP.

Resolved in #716 and #749

This was resolved in pull-request #477

@kmalski I think so but added the research tag to remind me to look for the "paper" @Johnlon mentioned.

@Johnlon I have read this [discussion](https://github.com/json-schema-org/json-schema-spec/issues/556) and can confirm that we meet the requirements of the [JSON Schema specification](https://json-schema.org/specification.html) and pass the relevant conformance [tests](https://github.com/json-schema-org/JSON-Schema-Test-Suite). I sympathize that you have...

@suren39 @stevehu The reason this test-case fails in Draft 4 is because the `const` keyword did not exist prior to Draft 6. I have verified that this test-case passes in...

_Notes on my investigation so I don't forget what I've learned._ The reason this fails under Drafts 2019-09 and 2020-12 is that `type` validation is defined in `meta/validation` while `properties`...

@manuelwaltschek The JSON Schema Team introduced `unevaluatedProperties` specifically for this use-case. Apparently, there was a lot of demand for this recursive behavior but they did not want to redefine the...

@anthonyleonard You can track our progress in two places: - [Compliance with the JSON Schema Test Suite](https://github.com/networknt/json-schema-validator/blob/master/doc/compatibility.md) - [What is currently disabled](https://github.com/networknt/json-schema-validator/blob/master/src/test/java/com/networknt/schema/JsonSchemaTestSuiteTest.java) As you can deduce from the second link,...

I agree that this project should be rewritten in Java. I also encountered difficulties with its use of Scala. Mainly with the conflicts created with other libraries that also use...