Pierre-Antoine Champin

Thanks @Tpt for chiming in. > It might be interesting to build it as a separated crate and make Sophia and Oxigraph depend on it, just like Rio. I have...

> An other way to go would be to have an "rdf-api" crate similar to what RDF/JS This should probably be discussed in a separate thread. I created #23 for...

@dwhitney that would awesome... :-) Sophia has evolved quite a bit in the meantime, in order to be more usable as a common API for RDF in Rust. @Tpt and...

@yever asked > A question for @pchampin is whether having nom as a dependency is acceptable. and @MattesWhite replied > The aim of `sophia` is to provide a common API...

I have a very early implementation of a SPARQL engine for Sophia: https://github.com/pchampin/sophia_sparql It should be integrated in v0.9 (but it might not be fully compliant by that time).

> Modifying a graph in compressed form may not even make sense I agree. HDT is not designed for allowing mutations, AFAIK. But the idea of of an HDT serializer...

One way to do it could be to use [RockDB](https://rocksdb.org/). We could even try and use the same layout as used by [Oxigraph](https://github.com/Tpt/oxigraph), making it possible to share the same...

> A better way to go would probably to make Oxigraph usable with Sophia. Yes, implementing Sophia's traits *above* Oxigraph is also a way to go, and probably the fastest...

Not published on crates.io yet, but an adapter for Oxigraph is now available at https://github.com/pchampin/sophia_oxigraph.

Just pushed [a PR](https://github.com/oxigraph/oxigraph/pull/882) on [Oxigraph](https://github.com/oxigraph/oxigraph) to make it implement the relevant Sophia traits (behind a feature gate). Oxigraph could therefore serve as a reference implementation of a persistent dataset.