Presentation Transcript
SPARQL for Business Intelligence :1 © 2008 OpenLink Software, All rights reserved. SPARQL for Business Intelligence Orri Erling - Program Manager, Virtuoso 1
For The Data Web to Deliver :2 © 2008 OpenLink Software, All rights reserved. For The Data Web to Deliver Promise of limitless integration and analysis
Existing SQL workloads should naturally fall within SPARQL’s scope
Surfing and joining between relational data and RDF should be seamless 2
What Is Missing? :3 © 2008 OpenLink Software, All rights reserved. What Is Missing? Aggregation
Nested Queries
Expressions 3
Mapped vs. Physical RDF :4 © 2008 OpenLink Software, All rights reserved. Mapped vs. Physical RDF Predicates are unspecified
Combining lots off different data sources
Lots of A-box inference (SameAs, Transitivity)
Mapped is better, if: Can push all to RDBMS - about 10x faster
Data is time-sensitive, frequently changing, very large Physical is better, if:
When defining mappings... :5 © 2008 OpenLink Software, All rights reserved. When defining mappings... Be careful when many tables make one entity - you may get lots of unions
Make explicit IRI scheme to limit pointless joining
Know what the mapper and SQL can and cannot optimize 5
Some Present Work :6 © 2008 OpenLink Software, All rights reserved. Some Present Work Refining generated SQL
There is no reason why SPARQL mapped should not equal SQL in performance, when going to single DBMS
Joining Between Mapped and Physical :7 © 2008 OpenLink Software, All rights reserved. Joining Between Mapped and Physical Special SQL logic is needed when joining IRI IDs of physical quads with IRI strings of virtual triples
SameAs requires special attention 7
Use Cases :8 © 2008 OpenLink Software, All rights reserved. Use Cases OpenLink MIS
All accounts, CRM, products, emails, support cases have URIs
MusicBrainz
OpenLink Data Spaces
PHPbb, Mediawiki, Drupal, etc. 8
OpenLink Software :9 © 2008 OpenLink Software, All rights reserved. OpenLink Software Thank You! http://virtuoso.openlinksw.com