Bureaucrats, developer, Administrators
9,867
edits
(more linking. split to headings for closer examination) |
(expanding on === Triplestore === + w:object database) |
||
Line 5: | Line 5: | ||
* [[w:Triplestore]] may be native implementation or on top of RDBMS and like the name implies it stores information as [[w:RDF]]-[[w:triplet|triplet]]s almost always in the subject-predicate-object form. | * [[w:Triplestore]] may be native implementation or on top of RDBMS and like the name implies it stores information as [[w:RDF]]-[[w:triplet|triplet]]s almost always in the subject-predicate-object form. | ||
* [[w:Graph databases]] would intuitively appear more advanced than using RDF-triplet composed semantic networks. | * [[w:Graph databases]] would intuitively appear more advanced than using RDF-triplet composed semantic networks. | ||
* [[w:Object database]]s were a supposed fad in the late 80's and early 90's as [[w:relational algebra]] based systems are quite old. | |||
=== RDBMS === | === RDBMS === | ||
Line 13: | Line 14: | ||
=== Triplestore === | === Triplestore === | ||
A triple store maybe a native implementation from ground up or be standing on the shoulders of a standard RDBMS system where actual SQL is formulated by the interpreter and then queried from SQL. This probably has upsides and downsides. | |||
* [[w:List of subject-predicate-object databases]] | * [[w:List of subject-predicate-object databases]] | ||
=== Graph database === | === Graph database === | ||
* [[w:Graph_database#List_of_graph_databases|Wikipedia's list of graph databases]] | * [[w:Graph_database#List_of_graph_databases|Wikipedia's list of graph databases]] |