IMAS'08 obda plugin

Realizing Ontology Based Data Access

A Plugin for Protégé

Mariano Rodríguez-MuroLina Lubyte

Diego Calvanese

Free University of Bozen BolzanoKnowledge Representation meets Databases group

Bolzano, Italy

Thursday, August 8, 13

Ontologies

• What are Ontologies?

• Shared conceptualizations of a domain of discourse

Ontologies

• Formal Semantics

Ontologies

• Allow us to perform complex inferencing

Ontologies

• Allow us to perform complex inferencing

• Description Logics!!

Reasoners

• Software systems that allow us to perform inferences over ontologies

Reasoners

• Software systems that allow us to perform inferences over ontologies

• Examples of reasoning services in DL reasoners:

• Subsumption checking, Instance checking, consistency checking

Wouldn’t it be nice if...

Data SourceData Source

Data Source

Data Layer

User Ontology

Semantic LayerUserQueries

SemanticMappings

Data Source

Data Layer

User Ontology

SemanticMappings

Data Source

Data Layer

User Ontology

SemanticMappings

Semantic Layer Data Layer

QueriesOntology RDBMs

Data Layer

Semantic

Mappings

OBDA-Enabled Reasoner

Data Layer

Semantic

Mappings

Meet OBDA

Data Layer

Semantic

Mappings

Data Layer

Semantic

Mappings

Example

Scenario:Software consultant for financial institutions.Objective: Achieve better reusability and modularization of their software solutions.Preconditions: Requirements are fixed requirements that the users must meet.

StockBroker

Trader

StockExchangeMember

Investor

Dealer StockTrader

tradesOnBehalfOf

usesBroker

Person

1 .. *

<<ident>>financialInstrumentID: intFinancialInstrument

<<ident>listdate: dateStockExchangeList

<<ident>transactionID:inttransactionDate: Date

Transaction

amountOfShares: inttypeOfShares: Boolean

Stock 1 .. *0 .. *

listsStock

StockExchangeMemberisExecutedBy

1 .. 1

Company

involvesInstrument

isTradedIn

1 .. 1

0 .. 1

Acquisition Offer

isListedIn1 .. 1 0 .. *

hasStockbelongsToCompany

{disjoint}

InvestorisExecutedFor1 .. 1

companyName: StringmarketShares: IntegernetWorth: Real

Company

firstName: NamelastName: StringdateOfBirth: Datessn: String

PhysicalPersonLegalPerson

<<ident>personID: intPerson

<<ident>addressID: intinStreet: SringhasNumber: IntinCity: StringinState: StringinCountry: String

Address1 .. *

1 .. 1

hasAddress{disjoint}

StockBroker

Trader

StockExchangeMember

Investor

Dealer StockTrader

tradesOnBehalfOf

usesBroker

Person

1 .. *

Transaction

Stock 1 .. *0 .. *

listsStock

1 .. 1

Company

involvesInstrument

isTradedIn

1 .. 1

0 .. 1

Acquisition Offer

{disjoint}

Company

Address1 .. *

1 .. 1

StockBroker

Trader

StockExchangeMember

Investor

Dealer StockTrader

tradesOnBehalfOf

usesBroker

Person

1 .. *

Transaction

Stock 1 .. *0 .. *

listsStock

1 .. 1

Company

involvesInstrument

isTradedIn

1 .. 1

0 .. 1

Acquisition Offer

{disjoint}

Company

Address1 .. *

1 .. 1

Applications

StockBroker

Trader

StockExchangeMember

Investor

Dealer StockTrader

tradesOnBehalfOf

usesBroker

Person

1 .. *

Transaction

Stock 1 .. *0 .. *

listsStock

1 .. 1

Company

involvesInstrument

isTradedIn

1 .. 1

0 .. 1

Acquisition Offer

{disjoint}

Company

Address1 .. *

1 .. 1

Client

addressid

......

dateofbirth ssnid

lastname

...... ...

Broker

addressid

...... ...

name ssn

......

lastname dateofbirth

BrokerWorksFor

...... ...

brokerid companyid clientid

Company

addressid

networthmarketshares

Transaction

......

...... ...

brokerid forclientidtype forcompanyiddate stockid

... ...

StockBookList

stockid

Address

country

......

street

citynumber

StockInformation

companyid

sharetypeid

numberofshares

MiFIDNew Client

Applications

StockBroker

Trader

StockExchangeMember

Investor

Dealer StockTrader

tradesOnBehalfOf

usesBroker

Person

1 .. *

Transaction

Stock 1 .. *0 .. *

listsStock

1 .. 1

Company

involvesInstrument

isTradedIn

1 .. 1

0 .. 1

Acquisition Offer

{disjoint}

Company

Address1 .. *

1 .. 1

Client

addressid

......

dateofbirth ssnid

lastname

...... ...

Broker

addressid

...... ...

name ssn

......

BrokerWorksFor

...... ...

Company

addressid

Transaction

......

...... ...

... ...

StockBookList

stockid

Address

country

......

street

citynumber

StockInformation

companyid

sharetypeid

numberofshares

Applications

MiFIDNew Client

StockBroker

Trader

StockExchangeMember

Investor

Dealer StockTrader

tradesOnBehalfOf

usesBroker

Person

1 .. *

Transaction

Stock 1 .. *0 .. *

listsStock

1 .. 1

Company

involvesInstrument

isTradedIn

1 .. 1

0 .. 1

Acquisition Offer

{disjoint}

Company

Address1 .. *

1 .. 1

Client

addressid

......

dateofbirth ssnid

lastname

...... ...

Broker

addressid

...... ...

name ssn

......

BrokerWorksFor

...... ...

Company

addressid

Transaction

......

...... ...

... ...

StockBookList

stockid

Address

country

......

street

citynumber

StockInformation

companyid

sharetypeid

numberofshares

Semantic Mapping!

Applications

MiFIDNew Client

Components revised

Data Layer

Semantic

Mappings

Components revised

Data Layer

Semantic

Mappings

Communication Facilities

Components revised

Data Layer

Semantic

Mappings

Reasoners need to be extended with

new paradigmThursday, August 8, 13

Components revised

Data Layer

Semantic

Mappings

Reasoners need to be extended with

new paradigm

Design Tools!

First stepsProtégé

ProtégéOWLPlugin

OBDA Plugin

DIG 1.2 + OBDAExtension

DS Info +Mappings

QuOnto

DIG Server for QuOnto

DS Info +Mappings

ProtégéOWLPlugin

OBDA Plugin

DS Info +Mappings

QuOnto

DS Info +Mappings

<?xml version="1.0" encoding="ISO-8859-1"?><tells xmlns="http://dl.kr.org/dig/lang" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://wasp.cs.vu.nl/sekt/digtest/dig-1.1.xsd"> <clearKB/> <defconcept name="a"/> <impliesc> <catom name="a"/> <and> <not> <or> <catom name="b"/> <catom name="c"/> </or> </not> </and> </impliesc</tells>

ProtégéOWLPlugin

OBDA Plugin

DS Info +Mappings

QuOnto

DS Info +Mappings

ProtégéOWLPlugin

OBDA Plugin

DS Info +Mappings

QuOnto

DS Info +Mappings

OBDA Plugin for Protégé

Demo, Ontology

StockBroker

Trader

StockExchangeMember

Investor

Dealer StockTrader

tradesOnBehalfOf

usesBroker

Person

1 .. *

Transaction

Stock 1 .. *0 .. *

listsStock

1 .. 1

Company

involvesInstrument

isTradedIn

1 .. 1

0 .. 1

Acquisition Offer

{disjoint}

Company

Address1 .. *

1 .. 1

Demo, scenario 1core services

Client

addressid

......

dateofbirth ssnid

lastname

...... ...

Broker

addressid

...... ...

name ssn

......

BrokerWorksFor

...... ...

Company

addressid

Transaction

......

...... ...

... ...

StockBookList

stockid

Address

country

......

street

citynumber

StockInformation

companyid

sharetypeid

numberofshares

Demo, Ontology

StockBroker

Trader

StockExchangeMember

Investor

Dealer StockTrader

tradesOnBehalfOf

usesBroker

Person

1 .. *

Transaction

Stock 1 .. *0 .. *

listsStock

1 .. 1

Company

involvesInstrument

isTradedIn

1 .. 1

0 .. 1

Acquisition Offer

{disjoint}

Company

Address1 .. *

1 .. 1

Mappings, populating concepts

Address(getAddressObj($address.id))

select * from address;

Mappings, populating attributes (datatype properties)

Address(getAddressObj($address.id)),addressID(getAddressObj($address.id),$address.id)

select * from address;

Mappings, populating roles (object properties)

hasAddress(getPersonObj($broker.id),getAddressObj($broker.addressid))

select * from broker;

Scenario II, conceptual model extraction

shares: int<<ident> id: int

Stock_Unit

1 .. 1

Stock_Company

average: int<<ident>date: dateTransaction_List1 .. *

0 .. *

Stock_TransactionList

descr: string date: date<<ident> id: int

Purchase

SalePurchase_Stock

0 .. *

Stock_Exchange_Company

1 .. 1

Sale_Stock

0 .. 10 .. 1 1 .. 1

type: stringname: string<<ident> id: int

Broker

name: string<<ident> id: intShare_Holder

1 .. 11 .. 1 Broker_SaleBroker_Purchase

1 .. *

Share_Holder_Broker

STOCK_UNIT

...... ...

company_idsharesid

PURCHASE

broker_id

......

stock_iddescr

......

broker_id

......

stock_iddescr

......

TRANSACTION_LIST

... ...

averagedate

stock_id

trans_date

STOCK_TRANSACTIONLISTSTOCK_EXCHANGE_COMPANY

shares

......... ...

networthnameid

BROKER

...... ...

typenameid

TRADER_CLIENT

...... ...

broker_idnameid

STOCK_UNIT

...... ...

company_idsharesid

PURCHASE

broker_id

......

stock_iddescr

......

broker_id

......

stock_iddescr

......

TRANSACTION_LIST

... ...

averagedate

stock_id

trans_date

shares

......... ...

networthnameid

BROKER

...... ...

typenameid

TRADER_CLIENT

...... ...

broker_idnameid

STOCK_UNIT

...... ...

company_idsharesid

PURCHASE

broker_id

......

stock_iddescr

......

broker_id

......

stock_iddescr

......

TRANSACTION_LIST

... ...

averagedate

stock_id

trans_date

shares

......... ...

networthnameid

BROKER

...... ...

typenameid

TRADER_CLIENT

...... ...

broker_idnameid

shares: int<<ident> id: int

Stock_Unit

1 .. 1

Stock_Company

average: int<<ident>date: dateTransaction_List1 .. *

0 .. *

Stock_TransactionList

Purchase

SalePurchase_Stock

0 .. *

Stock_Exchange_Company

1 .. 1

Sale_Stock

0 .. 10 .. 1 1 .. 1

type: stringname: string<<ident> id: int

Broker

name: string<<ident> id: intShare_Holder

1 .. 11 .. 1 Broker_SaleBroker_Purchase

1 .. *

Share_Holder_Broker

Final Remarks

• Plugin and server are now going trough extensive testing

• Public releases of both tools will happen by the end of april

• The software will be downloadable from

• http://www.inf.unibz.it/~rodriguez/obda/

• Future work: Explanations for all inferences and queries, Extending Protege/DIG with more expressivity regarding roles.

IMAS'08 obda plugin

Technology

Transcript of IMAS'08 obda plugin

obda 2014 (Autosaved).rtf

Personas Funcionarias IMAS

Portofolio Imas TH

Ungur obda 2014-11-10.docx

IMAS - Luxury 2015

Imas empaques

IMAS - Classico 2015

Lapsus ALL Imas

Open Data Bay Area (OBDA) | Kurt Bollacker: Public Metadata Commons

Open Data Bay Area (OBDA) | John Wilbanks

IMAS - Esterni 2015

Remember Imas family

Ontology-Based Data Access - UFPEin1099/162/Seminars/OBDA...NICOLLE CHAVES CYSNEIROS Roteiro Introdução Aplicações Arquitetura de um Sistema OBDA Trabalhos Relacionados Bringing

IMAS · МИР, КОТОРЫЙ МЫ ХОТИМ СОЗДАТЬ imas aeromeccanica imas aeromeccanica imas aeromeccanica azienda certificata en iso 9001. iiiiiii' illi/////i///// 111

Imas 2010 brass

Inicio - IMAS

The NPD Benchmark: Reality Check for OBDA Systemscalvanese/papers/lant-rezk-xiao-calv... · 2015. 3. 31. · The NPD Benchmark: Reality Check for OBDA Systems Davide Lanti, Martin

Imas firenze novelties catalogues 2011 2012 imas

The Combined Approach to OBDA: Taming Role Hierarchies ...clu/combined/fullpaper.pdfThe Combined Approach to OBDA: Taming Role Hierarchies using Filters Carsten Lutz1, _Inan˘c Seylan

Imas firenze luxury