This HTML5 document contains 37 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Subject Item

n14:this

foaf:made

n4:VOSTPCHLinkedData

Subject Item

n19:this

sioc:creator_of

n4:VOSTPCHLinkedData

Subject Item

n2:item

n3:services_of

n4:VOSTPCHLinkedData

Subject Item

n6:this

sioc:creator_of

n4:VOSTPCHLinkedData

Subject Item

n9:VOS

sioc:container_of

n4:VOSTPCHLinkedData

atom:entry

n4:VOSTPCHLinkedData

atom:contains

n4:VOSTPCHLinkedData

Subject Item

n4:VOSIndex

sioc:links_to

n4:VOSTPCHLinkedData

Subject Item

n4:VOSTPCHLinkedData

rdf:type

sioct:Comment atom:Entry

dcterms:created

2017-06-13T05:42:03.610343

dcterms:modified

2017-06-13T05:42:03.610343

rdfs:label

VOSTPCHLinkedData

foaf:maker

n13:this n14:this

dc:title

VOSTPCHLinkedData

opl:isDescribedUsing

n22:rdf

sioc:has_creator

n6:this n19:this

sioc:attachment

n8:sql

sioc:content

%VOSWARNING% %VOSNAV% --+TPC H As Linked Data Bringing Linked Data to Analytics %TOC% --++Introduction This article takes the industry standard TPC-H decision support benchmark and shows how its data can be exposed as linked data from any relational database. Virtuoso can either host the data itself or attach the relevant tables from any other database. Here we will look at a miniature sample of the TPC-H benchmark database that comes with the demo database. Exposing this data consists of a mapping declaration which translates the contents of the tables into a virtual RDF graph. The triples involved are not physically stored but are created on demand as requested by SPARQL queries or dereferencing the URIs representing the logical entities in the database. --++Mapping See the attached SQL file: <a href="%ATTACHURLPATH%/tpch.sql" style="wikiautogen">tpch.sql</a> --++Queries See the attached SQL file: <a href="%ATTACHURLPATH%/tpch.sql" style="wikiautogen">tpch.sql</a> As of this writing, not all the queries are supported. Thus you will see some of them commented-out. The relevant optimizations and SPARQL extensions for running these are being developed at the time of this writing. --++Dereferenceable URIs See the attached SQL file: <a href="%ATTACHURLPATH%/tpch.sql" style="wikiautogen">tpch.sql</a> This file defines a virtual directory and URI-rewrite rules that capture references to the TPC-H entities. The URL rewrite rules in this file catch references to the the TPC-H entities and redirect these into a SPARQL describe queries on the URI in question. The redirect makes an HTTP 303 redirection reply that goes to the SPARQL endpoint with a `describe' query for the object in question. --++Running the Samples There is a live sample of this demo running at http://demo.openlinksw.com/DAV/home/demo/tpch/ Virtuoso Open Source Edition will come with an implementation of the TPC-H data and queries from version 5.0.6 onwards. Start the demo server and connect to http://localhost:8890/DAV/home/demo/tpch with a web browser. The host part of the URIs given to the TPC-H data is given by the DefaultHost entry in the URIQA section of the virtuoso.ini file. --++Running the Samples Against External Data With the commercial release of Virtuoso, the tables do not have to reside in Virtuoso itself. They can be attached from any supported database using the Virtual Database layer (VDB). These can then be mapped into a graph of their own by re-running the mapping statements with the graph and tables renamed. %VOSCOPY% CategoryWebSite CategoryVirtuoso CategoryOpenSource

sioc:id

b109c1bb5c31b2f13309cfebcae3baa6

sioc:link

n4:VOSTPCHLinkedData

sioc:has_container

n9:VOS

n3:has_services

n2:item

atom:title

VOSTPCHLinkedData

sioc:links_to

n16: n17:DefaultHost n4:CategoryVirtuoso n18:tpch n17:CategoryWebSite n4:CategoryOpenSource

atom:source

n9:VOS

atom:author

n14:this

atom:published

2017-06-13T05:42:03Z

atom:updated

2017-06-13T05:42:03Z

sioc:topic

n9:VOS