Abstract functions for interacting with RDF & RDF backends, such as
RDF4j.

Symbols used to specify different Linked Data Serializations.

Includes functions to coerce formats from clojure keywords / file
extension strings into their underlying RDF4j RDFFormat object.

Supported format keywords are:

:brf
:json
:n3
:nq
:nt
:rdf (also :owl :rdfs :xml)
:rj
:trig
:trix
:ttl

Functions & Protocols for serializing Grafter Statements to (and from)
any Linked Data format supported by RDF4j.

Functions for constructing and working with various RDF4j repositories.

Namespace containing functions to manage the global registry of
Sesame parsers.

Normally you should not need to adjust the default global
registries, however if you need tighter control over what
serialisation format is negotiated on a SPARQL endpoint; for example
if the endpoint you are talking to has a serialisation bug then you
can force the use of different parser by removing the problematic
one.

Be warned though, these registries apply globally (process wide), so
altering them may have unintended consequences.

Functions for executing SPARQL queries with grafter RDF
repositories, that support basic binding replacement etc.

An implementation of SPARQL Property Paths[1] for `grafter`/`rdf4j`.

  [1] https://www.w3.org/TR/sparql11-query/#propertypaths

  Syntax Form | Property Path Expression Name | Matches
  =====================================================
  iri         | PredicatePath      | An IRI. A path of length one.
  ^elt        | InversePath        | Inverse path (object to subject).
  elt1 / elt2 | SequencePath       | A sequence path of elt1 followed by elt2.
  elt1 | elt2 | AlternativePath    | A alternative path of elt1 or elt2 (all possibilities are tried).
  elt*        | ZeroOrMorePath     | A path that connects the subject and object of the path by zero or more matches of elt.
  elt+        | OneOrMorePath      | A path that connects the subject and object of the path by one or more matches of elt.
  elt?        | ZeroOrOnePath      | A path that connects the subject and object of the path by zero or one matches of elt.
  !expression | NegatedPropertySet | Negated property set. An IRI which is not one of `expression`. !iri is short for !(iri).
  (elt)       |                    | A group path elt, brackets control precedence.A zero occurrence of a path element always matches.

The order of IRIs, and reverse IRIs, in a negated property set is not significant and they can occur in a mixed order.

The precedence of the syntax forms is, from highest to lowest:

  * IRI, prefixed names
  * Negated property sets
  * Groups
  * Unary operators *, ? and +
  * Unary ^ inverse links
  * Binary operator /
  * Binary operator |

Precedence is left-to-right within groups.

Functions for converting tree's of turtle-like data into Linked
Data statements (triples/quads).

DEPRECATED: Use grafter-2.rdf.protocols instead, this namespace contains the
old sesame implementation.

Functions and macros for creating RDF data.  Includes a
small DSL for creating turtle-like templated forms.

DEPRECATED.  Use grafter.rdf4j.formats instead, this namespace
contains the old sesame implementation.

Symbols used to specify different Linked Data Serializations.

DEPRECATED.  Use grafter.rdf4j.formats instead, this namespace
contains the old sesame implementation.

Functions & Protocols for serializing Grafter Statements to (and from)
any Linked Data format supported by Sesame.

DEPRECATED: Use grafter-2.rdf.protocols instead.  This namespace contains the old
sesame implementation.

Grafter protocols and types for RDF processing

DEPRECATED.  Use grafter.rdf4j.repository instead.  This namespace
contains the old sesame implementation.

Functions for constructing and working with various Sesame repositories.

DEPRECATED.  Use grafter.rdf4j.repository.registry instead, this namespace
contains the old sesame implementation.

Namespace containing functions to manage the global registry of
Sesame parsers.

Normally you should not need to adjust the default global
registries, however if you need tighter control over what
serialisation format is negotiated on a SPARQL endpoint; for example
if the endpoint you are talking to has a serialisation bug then you
can force the use of different parser by removing the problematic
one.

Be warned though, these registries apply globally (process wide), so
altering them may have unintended consequences.

DEPRECATED: Use grafter.rdf4j.sparql instead.  This namespace contains the
old sesame implementation.

DEPRECATED.  Use grafter.rdf4j.templater instead this namespace
contains the old sesame implementation.

Functions for converting tree's of turtle-like data into Linked
Data statements (triples/quads).