3 ms·

Adding reflection will be simple and backwards compatible with existing code as it would only come into play when someone hasn't manually mapped a type. This l

Adding reflection will be simple and backwards compatible with existing code as it would only come into play when someone hasn't manually mapped a type. This leaves the cases where reflection doesn't work(private member variables) still workable too. Haven't looked at JSONLD much, but it seems like it could be added but would be a library above I think. Extracting the mappings is already doable and is done in the JSON Schema export.

westurner 2y ago
"Exporting JSON Schema" https://github.com/beached/daw_json_link/blob/release/docs/cookbook/json_schema.md 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 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 https://news.ycombinator.com/item?id=32186878 re: json-ld-schema, which bridges JSONschema and SHACL for JSONLD