I was evaluating Semantica for a setup where we already have a graph store, and I got stuck on what the README means by polyglot graph storage. It says RDF and LPG are supported, but I couldn't tell whether that implies first-class adapters for specific engines, or whether users are expected to bring their own storage layer and wire it up themselves.
A small compatibility section would make onboarding much easier: which stores/backends are currently supported or tested, which features work with each (ingestion, context graph construction, reasoning/analytics, provenance), and any known limitations between RDF and LPG modes. Even one-line examples for connecting to a supported backend would help new users avoid guessing.
This seems especially useful given the project's focus on self-hosting and regulated domains, where teams often have constraints on which graph database they can deploy.
I was evaluating Semantica for a setup where we already have a graph store, and I got stuck on what the README means by polyglot graph storage. It says RDF and LPG are supported, but I couldn't tell whether that implies first-class adapters for specific engines, or whether users are expected to bring their own storage layer and wire it up themselves.
A small compatibility section would make onboarding much easier: which stores/backends are currently supported or tested, which features work with each (ingestion, context graph construction, reasoning/analytics, provenance), and any known limitations between RDF and LPG modes. Even one-line examples for connecting to a supported backend would help new users avoid guessing.
This seems especially useful given the project's focus on self-hosting and regulated domains, where teams often have constraints on which graph database they can deploy.