Turns any SPARQL 1.1 Repository into a fully featured Store, so shape-driven retrieval and
persistence run against a graph backend without hand-written queries. A ready-made connector from the
@metreeca/wire collection (Oxigraph, generic HTTP endpoints, RDF4J, …)
covers the common backends; a new backend is supported by implementing Repository directly.
Wiring a Connector
A ready-made connector is passed to createSPARQLStore to obtain a store:
A new SPARQL backend is supported by implementing a Repository. The
repository exchanges SPARQL text and
Tuple solution rows, whose values are @metreeca/trioTerm values. Backend node values are lifted into terms with the
named, tagged and typed
constructors. The reference implementation in @metreeca/wire-sparql-oxigraph follows this pattern:
SPARQL 1.1 repository connector.
Turns any SPARQL 1.1 Repository into a fully featured Store, so shape-driven retrieval and persistence run against a graph backend without hand-written queries. A ready-made connector from the @metreeca/wire collection (Oxigraph, generic HTTP endpoints, RDF4J, …) covers the common backends; a new backend is supported by implementing Repository directly.
Wiring a Connector
A ready-made connector is passed to createSPARQLStore to obtain a store:
Implementing a Connector
A new SPARQL backend is supported by implementing a Repository. The repository exchanges SPARQL text and Tuple solution rows, whose values are
@metreeca/trioTerm values. Backend node values are lifted into terms with the named, tagged and typed constructors. The reference implementation in@metreeca/wire-sparql-oxigraphfollows this pattern:See