Cristian Le

Oh, interesting point. I thought fetchcontent is only usable for cmake projects, but let me do a bit of researching and I'll get back to you on this.

Thanks for the idea. FetchContent does indeed work for that. There is one design problem though, how to make this compatible with Fedora packaging. For that, it must be buildable...

True, still needs to be redesigned so that the contents are untouched and it is easier to update it. (would also make it possible to add the tests as experimental...

Would you be able to make a break-down of the issues needed for the other drafts, mostly the big redesign roadblocks needed, e.g. the relative path parser.

If we use the latest version of the test-suite, would it reflect all of the new specifications, relative path, etc.?

Ok, maybe not the drafts version, but the test-suite repo version. I.e. within the draft, is it complete to cover all use-cases or are there some things that need to...

Indeed I understand that, I was asking of e.g. [draft7](https://github.com/json-schema-org/JSON-Schema-Test-Suite/tree/main/tests/draft7) tests if itself is complete. I see that they are complete with respect to previous ones, e.g. both draft4 and...

Wouldn't those still be built on top of the current drafts?

## CMake project name Proposed `nlohmann_json_schema_validator` -> `Json_Validator` ### Affects - Naming convention of other targets/options etc. There is no agreed standard but the most common one is: - options:...

I don't know about bazel/conan side if there is anything to be discussed there.