SPARQL 1.1 query language framework for @metreeca/wire storage connectors.
Provides a uniform Repository interface for issuing SPARQL queries and updates against any backend (an embedded store,
a remote endpoint, or a managed server), without binding application code to a specific store or client. It also bundles
the building blocks for working with the data exchanged, such as an RDF term model, DSLs for composing SPARQL queries
and RDF graphs, and codecs for RDF serialisations.
Install this framework together with a backend connector for your target engine, plus any peer dependency the connector requires:
npm install @metreeca/wire-sparql # the SPARQL query API (this framework)
npm install @metreeca/wire-sparql-<backend> # backend connector from the table below
npm install <peer-dependency> # connector's peer dependency, where required
TypeScript consumers must use "moduleResolution": "nodenext"/"node16"/"bundler" in tsconfig.json.
The legacy "node" resolver is not supported.
| Connector Package | Peer Dependency | Engine |
|---|---|---|
| @metreeca/wire-sparql-http | - | SPARQL 1.1 Protocol endpoint |
| @metreeca/wire-sparql-rdf4j | - | RDF4J REST API endpoint |
| @metreeca/wire-sparql-oxigraph | oxigraph >=0.5.0 |
Oxigraph in-memory WASM store |
This section introduces essential concepts; for complete coverage, see the API reference.
Obtain a Repository from any backend connector, then run SPARQL queries and updates through its methods:
import { createHTTPRepository } from "@metreeca/wire-sparql-http";
const repository = createHTTPRepository({
query: "https://example.org/sparql",
update: "https://example.org/sparql/statements"
});
await repository.update(`
INSERT DATA { <https://example.org/widget> <https://schema.org/name> "Widget" }
`);
const tuples = await repository.select(`
SELECT ?name { ?product <https://schema.org/name> ?name }
`); // readonly Tuple[]: each maps the ?name token to a Term
const present = await repository.ask(`ASK { ?s ?p ?o }`);
const triples = await repository.construct(`
CONSTRUCT { ?s ?p ?o } WHERE { ?s ?p ?o }
`); // readonly Triple[]
await repository.close();
Bracket related operations with execute: the task runs on a per-call Repository and commits together, or rolls back
if it throws:
await repository.execute(async tx => {
await tx.update(`DELETE WHERE { <https://example.org/widget> ?p ?o }`);
await tx.update(`INSERT DATA { <https://example.org/widget> <https://schema.org/name> "Gadget" }`);
});
Transaction isolation is backend-dependent. A backend with native transactions brackets the task for atomic commit
and rollback; one without runs the task directly against the same Repository, with no atomicity or rollback. Each
connector documents the level it provides on its factory function.
A backend connector implements the Repository interface (ask, select, construct, update, execute, and
close), lifting native backend nodes into the shared term model with the reference, tagged, and typed
constructors, and parsing or serialising RDF payloads with the codecs/ntriples module.
A minimal connector has the shape:
import type { Repository, SPARQL } from "@metreeca/wire-sparql";
function createMyRepository(/* endpoint, client, … */): Repository {
const repository: Repository = {
ask: async (query: SPARQL) => { /* run ASK; return the boolean */ },
select: async (query: SPARQL) => { /* run SELECT; map bindings to Tuples of Terms */ },
construct: async (query: SPARQL) => { /* run CONSTRUCT; map statements to Triples */ },
update: async (update: SPARQL) => { /* apply the UPDATE */ },
execute: async task => task(repository), // or bracket the task in a backend transaction
close: async () => { /* release resources, or no-op */ }
};
return repository;
}
Each SPARQL connector in the @metreeca/wire monorepo is a complete, working implementation that you can read to learn the approach or adapt for a new engine.
This project is licensed under the Apache 2.0 License – see LICENSE file for details.
A SPARQL query, update, or syntactic fragment as serialised text.
A SPARQL query-solution mapping.
A SPARQL triple pattern, as a subject/predicate/object statement with optional variables.
An allocated SPARQL variable.
An RDF graph, as a flat sequence of triples.
An RDF triple, as a subject/predicate/object statement.
The subject position of an RDF Triple.
The predicate position of an RDF Triple.
The object position of an RDF Triple.
An RDF term.
An RDF blank node.
An IRI reference.
An RDF language-tagged string, as a lexical-form/language-tag pair.
An RDF datatype-typed literal, as a lexical-form/datatype-IRI pair.
SPARQL repository.
Checks whether a value is a SPARQL solution Tuple.
Checks whether a value is a SPARQL triple Pattern.
Checks whether a value is a SPARQL Variable.
Checks whether a value is an RDF Graph.
Checks whether a value is an RDF Triple.
Checks whether a value is an RDF Term.
Checks whether a value is an RDF blank node.
Checks whether a value is a Reference.
Checks whether a value is an RDF language-Tagged string.
Checks whether a value is an RDF datatype-Typed literal.
Constructs a SPARQL triple Pattern.
Constructs a SPARQL solution Tuple.
Constructs a SPARQL Variable.
Constructs an RDF Graph.
Constructs an RDF Triple.
Constructs an RDF blank node.
Constructs an IRI Reference.
Replaces blank nodes in a Triple sequence with minted IRI references.
SPARQL repository API and data model.
Provides a single, backend-independent API for working with SPARQL stores. Consumers query and update through the Repository interface and exchange data as the RDF and SPARQL types defined here, regardless of which connector backs the store.
Vocabularies and formats
Repository
ask/select/construct,update, transactionalexecute, andcloseSPARQL data model
SELECTquery-solution mapping?-prefixed SPARQL variableRDF data model
ashorthand_:-prefixed blank-node labelSPARQL type guards
RDF type guards
SPARQL factories
RDF factories
Utilities
See