Triplestore

A triplestore or RDF store is a purpose-built database for the storage and retrieval of triples[1] through semantic queries. A triple is a data entity composed of subject-predicate-object, like "Bob is 35" or "Bob knows Fred".

Much like a relational database, one stores information in a triplestore and retrieves it via a query language. Unlike a relational database, a triplestore is optimized for the storage and retrieval of triples. In addition to queries, triples can usually be imported/exported using Resource Description Framework (RDF) and other formats.

Implementations
Main article: Comparison of triplestores

Some triplestores have been built as database engines from scratch, while others have been built on top of existing commercial relational database engines (such as SQL-based)[2] or NoSQL document-oriented database engines.[3] Like the early development of online analytical processing (OLAP) databases, this intermediate approach allowed large and powerful database engines to be constructed for little programming effort in the initial phases of triplestore development. It seems likely that native triplestores will have the advantage for performance over a longer period of time. A difficulty with implementing triplestores over SQL is that although "triples" may thus be "stored", implementing efficient querying of a graph-based RDF model (such as mapping from SPARQL) onto SQL queries is difficult.[4]

Adding a name to the triple makes a "quad store" or named graph.

A graph database has a more generalized structure than a triplestore, using graph structures with nodes, edges, and properties to represent and store data. Graph databases might provide index-free adjacency, meaning every element contains a direct pointer to its adjacent elements, and no index lookups are necessary. General graph databases that can store any graph are distinct from specialized graph databases such as triplestores and network databases.

gollark: Going through BF probably still introduces a lot of inefficiency.
gollark: No, but it's likely better than... interpreting BF.
gollark: Well, yes.
gollark: ELVM is probably more *efficient*, though.
gollark: Ah, okay, good.

See also

References
  1. TripleStore, Jack Rusher, Simple Knowledge Organization System § SWAD-Europe (2002–2004), Workshop on Semantic Web Storage and Retrieval – Position Papers.
  2. US 2003145022, "Storage and Management of Semi-structured Data": use of SQL relational databases as an RDF triple store.
  3. Cagle, Kurt. "Semantics + Search : MarkLogic 7 Gets RDF". Retrieved 7 August 2015.
  4. Broekstra, Jeen (19 September 2007). "The importance of SPARQL can not be overestimated".

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.