Module hdt::triples

Types for representing and querying triples.

Structs

• ObjectIter
  Iterator over all triples with a given object ID, answering an (?S,?P,O) query.
• OpIndex
  Inverse index from object id to positions in the object adjacency list. Used for logarithmic (?) time access instead of linear time sequential search.
• PredicateIter
  Iterator over all triples with a given property ID, answering an (?S,P,?O) query.
• PredicateObjectIter
  Iterator over all subject IDs with a given predicate and object ID, answering an (?S,P,O) query.
• SubjectIter
  Iterator over triples fitting an SPO, SP? S?? or ??? triple pattern.
• TripleId
  Type for a triple encoded as numeric IDs for subject, predicate and object, respectively. See https://www.rdfhdt.org/hdt-binary-format/#triples.
• TriplesBitmap
  BitmapTriples variant of the triples section.

Enums

• Order
  Order of the triple sections. Only SPO is tested, others probably don’t work correctly.

Type Aliases

• Id
  Subject, predicate or object ID, starting at 1. Subjects and predicate share IDs, starting at 1, for common values. A value of 0 indicates either not found (as a return value) or all of them (in a triple pattern). In the official documentation, u32 is used, however here, usize is used. While u32 caps out at 4 billion, more is not supported by the format anyways so this can probably be changed to u32.