How about (creating) a Prolog interpreter which consumes and outputs JSON?
Then use #SheBang to make any such prolog-file interpreted by that interpreter to return JSON to the caller. Then it could be integrated to ANY program written in any language which uses the Unix shell-calling conventionss.
this is certainly a very useful idea. the Rego datalog language leans on this pretty heavily, although its emphasis is on access policy more than general transforms.
ddlog is another datalog variant that supports this, but I believe you need to specify the schema as a rust type
12 comments
[ 3.2 ms ] story [ 30.7 ms ] threadhttps://citeseerx.ist.psu.edu/document?repid=rep1&type=pdf&d...
Prolog -(ish)-> Datalog -> Rego & OPA
https://www.openpolicyagent.org/docs/latest/policy-language
https://pypi.org/project/opa-python-client/
https://www.swi-prolog.org/pldoc/man?section=janus-intro
https://swi-prolog.discourse.group/t/a-bundled-python-interf...
Then use #SheBang to make any such prolog-file interpreted by that interpreter to return JSON to the caller. Then it could be integrated to ANY program written in any language which uses the Unix shell-calling conventionss.
ddlog is another datalog variant that supports this, but I believe you need to specify the schema as a rust type
https://www.openpolicyagent.org/docs/latest/