ID Based Triple Storage

Created on Feb. 23, 2013, 12:46 p.m. by Hevok & updated by Hevok on May 2, 2013, 5:20 p.m.

If one does not need always in the Triple Table the full URIs, which takes lots of Space and simple case of efficiency one can have a Translation Table where one has the name or the URI of the things referring to and it uses some Index (ID) to qualify that URI.

Then there is a Table that is simply filled with IDs which is much shorter and to interpret the IDs one has to rely on that Translation Table.

This architecture is much faster than Giant Triple Storage as one does not need to make large String comparison and one can simply deal with Numericals.

  • Use numeric identifier for each RDF Term in the Dataset
  • Saves space and enhances efficiency

Tags: architecture, coding, programming, database, storage
Categories: Tutorial
Parent: Storing RDF Data

Update entry (Admin) | See changes

Comment on This Data Unit