Open j-steinbach opened 1 year ago
HDT would definitely be a good match as back-end for certain Solid use cases (mostly for non-write-intensive cases, since HDT doesn't support updates).
Related to this there is the need for being able to expose a query interface at pod-level (or container-level) that could be backed by triple stores such as HDT (https://github.com/SolidLabResearch/Challenges/issues/43). This would remove the requirement on the client to understand HDT (which can be quite tricky), and only having to interact with the query API.
Related work:
(Unrelated, but maybe also interesting: Is it possible to export parts of the KG? Maybe as HDT :))
E: Similar to how we select tables in SQL and then export them. Create a view > export.
(Unrelated, but maybe also interesting: Is it possible to export parts of the KG? Maybe as HDT :)) E: Similar to how we select tables in SQL and then export them. Create a view > export.
Certainly, such materialized views are really interesting for query optimization.
Pitch
Desired solution
Acceptance criteria
Pointers
Scenarios
Use-Case / Origin
I want to put the Wiktionary data on a pod and then be able to re-create dictionary entries from the RDF data. I also want to be able to extend/annotate the dictionary entries (add new triples: my own example sentences, related words, ...) and export the data.
[The data is available as .ttl and .hdt. Comunica fails to read/query the Turtle data because it goes OOM (locally on the CLI, 16 GB RAM). The HDT however works.]