Expand description
JSON-LD documents in oxilite: each document is stored verbatim in a keyed table and its
RDF in a named graph (by default the document’s id), queryable with SPARQL.
This crate is sans-IO like oxilite-core: operations are oxilite_core::Jobs that
produce SQL requests. The oxilite crate (feature jsonld) drives them from
Store::jsonld() and AsyncStore::jsonld().
Re-exports§
pub use convert::blank_prefix;pub use convert::Converted;pub use error::JsonLdError;pub use error::Result;pub use loader::NoContexts;pub use options::ContextFetcher;pub use options::GraphStrategy;pub use options::JsonLdOptions;pub use options::KeyStrategy;pub use options::MetadataIndexes;pub use options::MissingKey;pub use options::ProcessingMode;pub use options::RdfDirection;pub use jobs::*;
Modules§
- convert
- JSON-LD → RDF with the
json-ldcrate, thenrdf-types→oxrdf. - error
- Errors raised by JSON-LD document storage.
- jobs
- Step machines of document storage: write (put, replace, remove), read, check, rebuild.
- loader
- Context loading without I/O: registered contexts, an optional first loader (bundled
contexts), then contexts read from
jsonld_contextsby the job itself. - options
- How documents are keyed and where their RDF goes.
- schema
- Tables of JSON-LD document storage, created on demand (stores that never use JSON-LD do not have them).
Traits§
- Loader
- Document loader.