86:(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. 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
109:
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.
221:
264:
62:. Unlike a relational database, a triplestore is optimized for the storage and retrieval of triples. In addition to queries, triples can usually be imported and exported using the
140:
triple (class, attribute) are pieces of some structural metadata having a defined semantic. The third element is a value, preferably from some controlled vocabulary.
74:
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
237:
352:
405:
422:
176:
564:
268:
200:
303:
489:
216:, Dingley, Andrew Peter, "Storage and management of semi-structured data", published 2005-04-27, assigned to
169:
63:
400:
128:
345:
438:
110:
General graph databases that can store any graph are distinct from specialized graph databases such as triplestores and
83:
559:
380:
241:
484:
79:
196:
569:
338:
531:
526:
584:
579:
40:
213:
479:
385:
148:
143:
48:
448:
217:
55:
44:
494:
474:
375:
153:
574:
499:
509:
395:
417:
32:
412:
361:
106:
59:
36:
553:
514:
390:
157:
111:
521:
458:
51:, like "Bob is 35" (i.e., Bob's age measured in years is 35) or "Bob knows Fred".
453:
99:
504:
443:
123:
319:
298:
293:
314:
160:, advanced query support, and implementations by many large organizations
133:
28:
324:
308:
226:, now expired; use of SQL relational databases as an RDF triple store.
163:
87:
203:, Workshop on Semantic Web Storage and Retrieval – Position Papers.
201:
Simple
Knowledge Organization System § SWAD-Europe (2002–2004)
330:
334:
166:– W3C specification involving subject-predicate-object triples
75:
58:, information in a triplestore is stored and retrieved via a
156:— an example of subject-predicate-object support for
98:
Adding a name to the triple makes a "quad store" or
467:
431:
368:
304:
How RDF Databases Differ from Other NoSQL Solutions
265:"The importance of SPARQL can not be overestimated"
238:"Semantics + Search : MarkLogic 7 Gets RDF"
346:
16:Database for storage and retrieval of triples
8:
353:
339:
331:
39:. A triple is a data entity composed of
189:
179:is a similar approach to data modeling.
82:engines. Like the early development of
263:Broekstra, Jeen (19 September 2007).
7:
299:Lehigh University Benchmark (LUBM)
14:
311:was RDF Data Access Working Group
90:) onto SQL queries is difficult.
31:for the storage and retrieval of
327:W3C Recommendation 21 March 2013
136:– The first two elements of the
170:List of SPARQL implementations
64:Resource Description Framework
1:
294:A list of large triplestores
177:Entity–attribute–value model
84:online analytical processing
565:Database management systems
601:
80:document-oriented database
129:Entity–relationship model
66:(RDF) and other formats.
309:W3C SPARQL Working Group
532:Ordered Key-Value Store
423:Entity–attribute–value
134:Metadata § Syntax
94:Related database types
315:SPARQL Query language
138:class-attribute-value
149:Semantic Integration
144:Outline of databases
401:Entity–relationship
271:on 19 December 2014
218:Hewlett-Packard Co.
56:relational database
27:is a purpose-built
560:Types of databases
154:Semantic MediaWiki
545:
544:
490:Object–relational
485:Document-oriented
439:Multi-dimensional
325:SPARQL 1.1 Update
112:network databases
78:-based) or NoSQL
592:
510:Transaction time
355:
348:
341:
332:
281:
280:
278:
276:
267:. Archived from
260:
254:
253:
251:
249:
244:on 8 August 2015
240:. Archived from
233:
227:
225:
224:
220:
210:
204:
194:
37:semantic queries
600:
599:
595:
594:
593:
591:
590:
589:
570:Database theory
550:
549:
546:
541:
527:Key–value store
480:Column-oriented
468:Implementations
463:
427:
418:Object-oriented
364:
362:Database models
359:
320:SPARQL Protocol
290:
285:
284:
274:
272:
262:
261:
257:
247:
245:
235:
234:
230:
222:
212:
211:
207:
199:, Jack Rusher,
195:
191:
186:
120:
96:
72:
70:Implementations
17:
12:
11:
5:
598:
596:
588:
587:
582:
577:
572:
567:
562:
552:
551:
543:
542:
540:
539:
534:
529:
524:
522:XML data store
519:
518:
517:
512:
507:
497:
492:
487:
482:
477:
471:
469:
465:
464:
462:
461:
456:
451:
446:
441:
435:
433:
429:
428:
426:
425:
420:
415:
410:
409:
408:
398:
393:
388:
383:
378:
372:
370:
366:
365:
360:
358:
357:
350:
343:
335:
329:
328:
322:
317:
312:
306:
301:
296:
289:
288:External links
286:
283:
282:
255:
228:
205:
188:
187:
185:
182:
181:
180:
174:
173:
172:
161:
151:
146:
141:
131:
126:
119:
116:
107:graph database
95:
92:
71:
68:
60:query language
15:
13:
10:
9:
6:
4:
3:
2:
597:
586:
583:
581:
578:
576:
573:
571:
568:
566:
563:
561:
558:
557:
555:
548:
538:
535:
533:
530:
528:
525:
523:
520:
516:
515:Decision time
513:
511:
508:
506:
503:
502:
501:
498:
496:
493:
491:
488:
486:
483:
481:
478:
476:
473:
472:
470:
466:
460:
457:
455:
452:
450:
447:
445:
442:
440:
437:
436:
434:
430:
424:
421:
419:
416:
414:
411:
407:
404:
403:
402:
399:
397:
394:
392:
389:
387:
384:
382:
379:
377:
374:
373:
371:
369:Common models
367:
363:
356:
351:
349:
344:
342:
337:
336:
333:
326:
323:
321:
318:
316:
313:
310:
307:
305:
302:
300:
297:
295:
292:
291:
287:
270:
266:
259:
256:
243:
239:
236:Cagle, Kurt.
232:
229:
219:
215:
209:
206:
202:
198:
193:
190:
183:
178:
175:
171:
168:
167:
165:
162:
159:
155:
152:
150:
147:
145:
142:
139:
135:
132:
130:
127:
125:
122:
121:
117:
115:
113:
108:
103:
101:
93:
91:
89:
85:
81:
77:
69:
67:
65:
61:
57:
52:
50:
46:
42:
38:
34:
30:
26:
22:
585:Triplestores
580:Semantic Web
547:
536:
459:XML database
432:Other models
381:Hierarchical
273:. Retrieved
269:the original
258:
246:. Retrieved
242:the original
231:
208:
192:
137:
104:
97:
73:
54:Much like a
53:
24:
20:
18:
537:Triplestore
454:Star schema
386:Dimensional
197:TripleStore
100:named graph
21:triplestore
554:Categories
505:Valid time
396:Relational
214:GB 2384875
184:References
124:Dataspaces
495:Deductive
475:Flat file
45:predicate
25:RDF store
575:Metadata
500:Temporal
449:Semantic
406:Enhanced
275:25 April
248:7 August
118:See also
35:through
29:database
391:Network
41:subject
33:triples
223:
164:SPARQL
88:SPARQL
49:object
444:Array
413:Graph
158:wikis
376:Flat
277:2014
250:2015
76:SQL
23:or
556::
114:.
105:A
102:.
19:A
354:e
347:t
340:v
279:.
252:.
47:–
43:–
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.