Advanced querying

On this page

The following guides explore some of the more advanced concepts when querying using Comunica.

Send authenticated HTTP requests by including username and password.

Bindings objects are used to represent results of SPARQL SELECT queries

When remote sources are requested, caching allows them to be reused in the future.

A context can be passed to a query engine to tweak its runtime settings.

Comunica detects and handles different types of destinations.

Display information about the logical and physical query plan

Providing implementations for SPARQL extension functions.

Query over the union of data within any number of sources

Using the power of JSON-LD contexts, GraphQL queries can be executed by Comunica

HDT offers highly compressed immutable RDF storage.

Loggers can be set to different logging levels to inspect what Comunica is doing behind the scenes.

Using the Memento protocol, time travel queries can be executed.

All HTTP requests can optionally go through a proxy.

If the built-in source types are not sufficient, you can pass a custom JavaScript object implementing a specific interface.

If the built-in destination types are not sufficient, you can pass a custom JavaScript object implementing a specific interface.

To achieve maximum interoperability between different JavaScript libraries, Comunica builds on top of the RDF/JS specifications.

Query results can be serialized in different formats.

Solid – the Web-based decentralization ecosystem – can be queried with Comunica.

Comunica detects and handles different types of sources.

Different SPARQL query types are possible, such as SELECT, CONSTRUCT, ASK, ...

Comunica supports several RDF-related specifications