1
How to Find the Right Data? Ontology Based Access to NPD FactPages Optique 1.0 Modules Optique 1.0 Architecture Ontology Based Data Access Consortium Challenges in data access Data access has to go via an IT expert Miscommunica6on between end users and IT experts IT experts have to write specialised queries for different DBs Restricted crea6vity and explora6on capabili6es for end users Bo0leneck: access to IT expert Up to 70% time on data access Turnaround time: days ©Harald Pettersen/Statoil Ontology Visualisation Answer Visualisation Visual Query Formulation SPARQL Editor Ontology and Mapping Management Visualisation Query Formulation Interface System Interface Query Answering NPD FactPages Triple Store Presentation Layer Application Layer Data Layer Reasoner Reasoner Expert users End users NPD FactPages Bootstrapped Ontology 70 classes, 276 proper6es 192 domain, range restr. 10 subclass rela6ons NPD FactPages 70 tables, 276 at. names 96 foreign keys 46 MB RDB 125 MB = 2.342.597 triples Mappings 346 direct mappings Imported petro ontology 209 classes 131/229 object/data prop. 1271 axioms Op@que 1.0 Querying Visual query formula6on interface SPARQL end point Op@que 1.0 Query processing Query rewri6ng over ontology Query unfolding with mapping Query execu6on over RDBs Op@que 1.0 Installa@on module Ontology bootstrapping Mapping bootstrapping Ontology alignment Ontology approxima6on HermiT Reasoner Optique 1.0 over NPD FactPages 1.0 Philosophy of OBDA User is confronted to an ontology and not to databases Ontology is connected to DBs via declara6ve mappings Queries are formulated over the ontology Queries are pushed to DBs and evaluated over DBs mappings Ontology

Optique - poster

  • Upload
    dbonto

  • View
    136

  • Download
    4

Embed Size (px)

DESCRIPTION

Optique poster

Citation preview

Page 1: Optique - poster

How to Find the Right Data?!

Ontology Based Access to NPD FactPages

Optique 1.0 Modules!

Optique 1.0 Architecture !

Ontology Based Data Access!

Consortium!

Challenges  in  data  access  •  Data  access  has  to  go    

via  an  IT  expert  •  Miscommunica6on  between  

end  users  and  IT  experts  •  IT  experts  have  to  write  specialised  

queries  for  different  DBs  •  Restricted  crea6vity  and      

explora6on  capabili6es  for  end  users  

Bo0leneck:  access  to  IT  expert  

defaultUse Case Partners know Big Data

Up to 80% timeon data access

Up to 70% timeon data access

Turnaround time:weeks

Turnaround time:days

© Siemens AG © Harald Pettersen/Statoil

5 / 18

Ontology Visualisation

Answer Visualisation

Visual Query Formulation

SPARQL Editor

Ontology and Mapping

Management

VisualisationQuery Formulation Interface System Interface

Query Answering

NPD FactPages

Triple Store

PresentationLayer

Application Layer

Data Layer

ReasonerReasoner

Expert users

End users

NPD FactPages

Bootstrapped  Ontology  •  70  classes,  276  proper6es  •  192  domain,  range  restr.  •  10  subclass  rela6ons  

NPD  FactPages    •  70  tables,  276  at.  names  •  96  foreign  keys  •  46  MB  RDB  •  125  MB  =  2.342.597  triples  

Mappings  •  346  direct  mappings  

Imported  petro  ontology  •  209  classes  •  131/229  object/data  prop.  •  1271  axioms  

Op@que    1.0  Querying    •  Visual  query  formula6on  interface    •  SPARQL  end  point  

Op@que    1.0  Query  processing  •  Query  rewri6ng  over  ontology  •  Query    unfolding  with  mapping    •  Query  execu6on  over  RDBs  

Op@que    1.0  Installa@on  module  •  Ontology  bootstrapping  •  Mapping  bootstrapping  •  Ontology  alignment  •  Ontology  approxima6on  

HermiT Reasoner

Optique 1.0 over NPD FactPages!

1.0  

Philosophy  of  OBDA  •  User    is  confronted  to  an  ontology  

and  not  to  databases  •  Ontology  is  connected  to  DBs  via  

declara6ve  mappings  •  Queries  are  formulated  over  the  

ontology  •  Queries  are  pushed  to  DBs  and  

evaluated  over  DBs  

mappings

Ontology