triplestore or RDF store is a database created specifically for storage and triple retrieval through semantic queries. Triple is a data entity consisting of subject-predicate-objects, such as "Bob is 35" or "Bob knows Fred".
Just like a relational database, one stores information in a triplestore and retrieves it through a query language. Unlike relational databases, triplestore is optimized for triple storage and retrieval. In addition to queries, threefold can usually be imported/exported using the Resource Description Framework (RDF) and other formats.
Video Triplestore
Implementations
Some triplestore have been built as database engines from scratch, while others have been built on existing commercial relational database machines (such as SQL-based) or document-oriented database engine NoSQL. Like the initial development of online analytical processing (OLAP) databases, this intermediate approach enables large and powerful database engines to be built for small businesses in the early phase of triplestore development. It looks like the original triplestora will have an advantage for performance over a longer period of time. The difficulty with implementing triplestores over SQL is that even if "threefold" can be "stored", implement efficient queries from graphical RDF models (such as mapping from SPARQL) to difficult SQL queries.
Maps Triplestore
Related database types
Adding a name to a triple creates a "quad store" or a named graph.
The graphics database has a more general structure than the triplestore, using a graph structure with nodes, edges, and properties to represent and store data. The graphics database may provide a free-index adjacency, which means each element contains a direct pointer to an adjacent element, and no index search is required. A common graphical database that can store graphics differs from specialized graphics databases such as triplestores and network databases.
See also
- Wall Space
- Entity relationship model
- ISO/IEC 19788 - In the MLR (metadata for learning resources) threefold, the subject is always a literal of the source identifier, such as a URI or ISBN. The predicate is also literal, the specification identifier of MLR data elements. Finally, the object can be either a literal or a resource class (a set of accepted values, such as a list of term identifiers from a controlled vocabulary list).
- Metadata Ã,§ Syntax - The first two elements of the triple-class
triple (class, attribute) are part of some structural metadata that has the specified semantics. The third element is the value, preferably from some controlled vocabulary. - Outline of the database
- RDFLib - a Python library for working with RDF including backend in-memory and persistent Graph, supports subject-predicate-object triple pattern matching
- Semantic data model
- Semantic wiki and Semantic MediaWiki - two examples of subject-predicate subject support for wikis, advanced query support, and implementations by many large organizations
- SPARQL - a W3C specification that involves subject-predicate-objects threefold
- List of SPARQL implementations
- Entity-attribute-value_model is a similar approach to data modeling.
References
External links
- Large triplestore list
- Lehigh University Benchmark (LUBM)
- How the RDF Database is Different from Other NoSQL Solutions
- The W3C SPARQL Working Group is the RDF Data Access Working Group
- SPARQL Query Language
- SPARQL Protocol
- SPARQL 1.1 Update W3C Recommendation March 21, 2013
- Metaweb's Graphd tuple store (owned by Google) used in Freebase and Knowledge Graphs
Source of the article : Wikipedia
0 Comments