A new package, rdf_json_ld implements part of the JSON-LD API: context processing, expansion, deserialization to RDF and serialization to Json-ld. Note that serialization produces a flat Json-ld rather than implementing the algorithm from the recommandation. It’s worth noting that the specification seems to have been written by javascript developers with little notion of typing. Moreover, JSON-LD format is far more complicated (and undoubtedly more energy-consuming) than simpler formats such as XML, Turtle or N-quads. I therefore advise against its use (but several activitypub servers seem to communicate only with this format…).
Packages rdf, rdf_ppx, rdf_json_ld, rdf_mysql, rdf_postgresql, and rdf_lwt are avalable in opam.
I fear that was the innovation from ActivityStreams 2.0 over 1.0. Syntactic and operational complication (ssl cert expiry plagues ActivityPub itself) without semantic gains but broken tooling. Before we had raptor, roqet, xmllint, xslt, trang and could even cat turtle.
About the technical reasons which prevented you to use OCaml-RDF: the library is not really tied to Cryptokit or Pcre, since there is a hook system to set the corresponding required functions (sha1, sha256, pcre_match, pcre_regexp). See lib/stubs.ml. The default rdf library should not require Cryptokit and Pcre (as it does from the package description by now), and I realize that a package rdf_impls, which initializes the required functions, is not installed. This will be fixed in a next release. So you should be able to use rdf with js_of_ocaml.
I understand the other reasons, no problem.
Regarding my post-JSON-LD sanity, it slowly recovers . There have been difficult moments, for example when my code failed on some provided test cases, until I realize that the reference implementation gave the same results as my code
. There have been difficult moments, for example when my code failed on some provided test cases, until I realize that the reference implementation gave the same results as my code 