Your SlideShare is downloading. ×
0
ESWC2008 SPARQL BI OpenLink- SPARQL for Business Intelligence
ESWC2008 SPARQL BI OpenLink- SPARQL for Business Intelligence
ESWC2008 SPARQL BI OpenLink- SPARQL for Business Intelligence
ESWC2008 SPARQL BI OpenLink- SPARQL for Business Intelligence
ESWC2008 SPARQL BI OpenLink- SPARQL for Business Intelligence
ESWC2008 SPARQL BI OpenLink- SPARQL for Business Intelligence
ESWC2008 SPARQL BI OpenLink- SPARQL for Business Intelligence
ESWC2008 SPARQL BI OpenLink- SPARQL for Business Intelligence
ESWC2008 SPARQL BI OpenLink- SPARQL for Business Intelligence
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

ESWC2008 SPARQL BI OpenLink- SPARQL for Business Intelligence

2,812

Published on

Published in: Business, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,812
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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

×