daw_json_link

On the other end of the spectrum there is [1]. It's both performance and usability oriented, although compile times are probably higher. Nlohmann is the slowest out of the popular libraries, AFAIK, and not particularly more usable than rapidjson, in my experience. So "better than nlohmann" is not very novel. [1] https://github.com/beached/daw_json_link

"Exporting JSON Schema" https://github.com/beached/daw_json_link/blob/release/docs/c... : include <daw/json/daw_json_schema.h> std::string daw::json::to_json_schema<MyType>( "identifier", "title" ); From https://westurner.github.io/hnlog/#comment-38526588 : > SHACL is used for expressing integrity constraints on complete data, while OWL allows inferring implicit facts from incomplete data; SHACL reasoners perform validation, while OWL reasoners do logical inference. - "Show HN: Pg_jsonschema – A Postgres extension for JSON validation" https://news.ycombinator.com/item?id=32186878 re: json-ld-schema, which bridges JSONschema and SHACL for JSONLD

re Serde: If you want JSON, https://github.com/beached/daw_json_link is about as close as we can get. It interop's well with the reflection(or like) libraries such as Boost Describe or Boost PFR and will work well with std reflection when it is available.

This lib does something like that: https://github.com/beached/daw_json_link

They exist, for instance https://github.com/beached/daw_json_link , uses mappings of JSON <-> class members/construction. It handles a bunch of types out of the box and allows custom types to be mapped. Also, it integrates with some of the reflection like libraries out there now(Boost.Describe/Boost.PFR) and will be trivial to add C++26 static reflection when available. Because the library doesn’t need to allocate unless the underlying types being parsed to do, it has been constexpr since C++17 too. A bunch of people have used libraries that use macros for reflection like or PFR to integrate other C++ JSON Libraries too.