Some examples of ontology-based applications

1

Some examples of ontology-based applications

Oscar Corcho / Asunción Gómez-Pérez{ocorcho,asun}@fi.upm.eshttp://www.oeg-upm.net/

Ontological Engineering GroupLaboratorio de Inteligencia Artificial

Facultad de InformáticaUniversidad Politécnica de Madrid

Campus de Montegancedo sn,28660 Boadilla del Monte, Madrid, Spain

2

Common features in these domains

• A large amount of information

• Need to harmonize heterogeneous information sources

• Different formats (documents, databases, etc.)

• Different terms and structures

• Implicit knowledge hidden inside the application code

28

Procesamiento de información de satélites

30

Satellite Use Case: Technical issues

SpaceSegment

Ground Segment

DMOP files

Product files

SATELLITE FILES:

31

Satellite Use Case: Technical issues• Comparison between planning and product generation:

...Instr#n(RA_2)planning

DMOP_File#n(StartTime) DMOP_File#n(StopTime)

DMOP_File#(n+1)StartTime

DMOP#(n+1)_File(StopTime)

DMOP_er (ORBIT_NUMBER,ELAPSED_TIME)

Instr#1planning

DURATION

PRODUCT_FILEStart_time(SENSING_START)

PRODUCT_FILEStop_time(SENSING_STOP)

...

Instr#n(RA_2)ProductGeneration

RA2_CAL_1PStop_time(SENSING_STOP)

RA2_CAL_1PStart_time(SENSING_START)

PRODUCT_data_gap... ...

32


34


Satellite files:

• DMOP (PLANNING) FILES

FILE ; DMOP (generated by FOS Mission Planning System) RECORD fhr FILENAME="DMOP_SOF__VFOS20060124_103709_00000000_00001215_20060131_014048_20060202_035846.N1" DESTINATION="PDCC" PHASE_START=2 CYCLE_START=44 REL_START_ORBIT=404 ABS_START_ORBIT=20498

ENDRECORD fhr................................ RECORD dmop_er RECORD dmop_er_gen_part RECORD gen_event_params

EVENT_TYPE=RA2_MEA EVENT_ID="RA2_MEA_00000000002063" NB_EVENT_PR1=1 NB_EVENT_PR3=0 ORBIT_NUMBER=20521 ELAPSED_TIME=623635 DURATION=41627862 ENDRECORD gen_event_params ENDRECORD dmop_erENDLIST all_dmop_erENDFILE

RECORD ID

RECORD parameters

RECORD parameters corresponding to other

RECORD structure.

35

Satellite Use Case: Technical issuesSatellite Ontology (General view)

36

Satellite Use Case: Technical issuesSatellite Ontology (Hierarchies)

37

• Planning (DMOP) RECORD parameters


38


Satellite files

• PRODUCT FILES

PRODUCT="RA2_MW__1PNPDE20060131_231554_000061672044_00416_20510_0181.N1"PROC_STAGE=NREF_DOC="PO-RS-MDA-GS-2009_3/M " SENSING_START="31-JAN-2006 23:15:54.654195"SENSING_STOP="01-FEB-2006 00:58:41.702319" PHASE=2CYCLE=+044REL_ORBIT=+00416ABS_ORBIT=+20510STATE_VECTOR_TIME="31-JAN-2006 23:28:36.484942"DELTA_UT1=+.323875<s>X_POSITION=+6637305.306<m>Y_POSITION=-2700075.034<m>Z_POSITION=+0000000.000<m>X_VELOCITY=-0622.619862<m/s>Y_VELOCITY=-1507.628845<m/s>Z_VELOCITY=+7377.140620<m/s>

PRODUCT_ERR=0TOT_SIZE=+00000000000087159984<bytes>SPH_SIZE=+0000006975<bytes>NUM_DSD=+0000000019DSD_SIZE=+0000000280<bytes>NUM_DATA_SETS=+0000000004

Parameters NOT needed to be transformed at the moment

Parameters to be transformed

Parameters to be transformed at this moment

39

Satellite files: Annotated DMOP (PLANNING) FILES

<?xml version='1.0' encoding='ISO-8859-1'?><rdf:RDF

xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'

xmlns:rdfs='http://www.w3.org/2000/01/rdf-schema#'

xmlns:NS0='http://protege.stanford.edu/kb#'

>

<rdf:Description rdf:about='http://protege.stanford.edu/kb#10822'>

<rdf:type rdf:resource='http://protege.stanford.edu/kb#Instrument_mode'/>

<NS0:instrument_mode_id>MS</NS0:instrument_mode_id>

</rdf:Description>

<rdf:Description rdf:about='http://protege.stanford.edu/kb#11224'>

<rdf:type rdf:resource='http://protege.stanford.edu/kb#DMOP_ER'/>

<NS0:event_id>"GOM_OCC_00000000541299"</NS0:event_id>

<NS0:duration rdf:datatype='http://www.w3.org/2001/XMLSchema#int'>53000</NS0:duration>

<NS0:orbit_number rdf:datatype='http://www.w3.org/2001/XMLSchema#int'>20552</NS0:orbit_number>

<NS0:elapsed_time rdf:datatype='http://www.w3.org/2001/XMLSchema#int'>2452293</NS0:elapsed_time>

<NS0:event_type rdf:resource='http://protege.stanford.edu/kb#10713'/>

</rdf:Description>

[...]


40

• Namefile (Product):

RA2_MW__1PNPDK20060201_120535_000000062044_00424_20518_0349.N1"

Corresponds to:


Satellite files: PRODUCT filename

41

Satellite Use Case: Technical issuesSatellite files: XMLed PRODUCT FILE

<PRODUCT>"RA2_MW__1PNPDE20060131_231554_000061672044_00416_20510_0181.N1“</PRODUCT><PROC_STAGE>N</PROC_STAGE><REF_DOC>"PO-RS-MDA-GS-2009_3/M "</REF_DOC>

<ACQUISITION_STATION>"PDHS-E "</ACQUISITION_STATION><PROC_CENTER>"PDHS-E"</PROC_CENTER><PROC_TIME>"01-FEB-2006 01:22:48.232601"</PROC_TIME><SOFTWARE_VER>"RA2/5.02 "</SOFTWARE_VER>

<SENSING_START>"31-JAN-2006 23:15:54.654195"</SENSING_START><SENSING_STOP>"01-FEB-2006 00:58:41.702319"</SENSING_STOP>

<PRODUCT_ERR>0</PRODUCT_ERR><TOT_SIZE>+00000000000087159984<bytes></TOT_SIZE><SPH_SIZE>+0000006975<bytes></SPH_SIZE><NUM_DSD>+0000000019</NUM_DSD><DSD_SIZE>+0000000280<bytes></DSD_SIZE><NUM_DATA_SETS>+0000000004</NUM_DATA_SETS>

Parameters NOT needed to be

transformed at this moment.

!!! FUTURE SCALABILITY

IMPROVEMENT !!

42

Satellite files: Annotated PRODUCT FILE [...] <rdf:Description rdf:about="http://protege.stanford.edu/kb#10605"> <rdf:type rdf:resource="http://protege.stanford.edu/kb#Product_file"/> <NS0:file_name>"RA2_MW__1PNPDK20060201_120535_000044792044_00424_20518_0334.N1"</NS0:file_name> <NS0:sensing_start rdf:datatype="http://www.w3.org/2001/XMLSchema#int">192110735</NS0:sensing_start> <NS0:sensing_stop rdf:datatype="http://www.w3.org/2001/XMLSchema#int">192115215</NS0:sensing_stop> <NS0:specific_product_header rdf:resource="http://protege.stanford.edu/kb#10608"/> </rdf:Description> <rdf:Description rdf:about='http://protege.stanford.edu/kb#10649'><NS0:file_name>"RA2_MW__1PNPDK20060202_160340_000058672044_00441_20535_0344.N1"</NS0:file_name> <NS0:sensing_start rdf:datatype='http://www.w3.org/2001/XMLSchema#int'>192211420</NS0:sensing_start> <NS0:sensing_stop rdf:datatype='http://www.w3.org/2001/XMLSchema#int'>192217287</NS0:sensing_stop> <NS0:specific_product_header rdf:resource='http://protege.stanford.edu/kb#10652'/> </rdf:Description>[...]


43

// Use to get a proxy class for MetadataService private java.lang.String MetadataService_address = "http://195.134.67.205:8080/AtlasService/services/MetadataService"; public java.lang.String getMetadataServiceAddress() { return MetadataService_address; }

[…]

public eu.ist.ontogrid.ontokit.MetadataService.MetadataService getMetadataService() throws javax.xml.rpc.ServiceException { java.net.URL endpoint; try { endpoint = new java.net.URL(MetadataService_address); } catch (java.net.MalformedURLException e) { throw new javax.xml.rpc.ServiceException(e); } return getMetadataService(endpoint); }

[…]

public static void main(String[] args) { MetadataServiceProxy proxy = new MetadataServiceProxy(); String query1 ="SELECT X FROM {X}kb:instrument_mode_id{Y} WHERE Y=\"STB\" USING NAMESPACE kb=&http://protege.stanford.edu/kb#"; String query2 = "SELECT Z FROM {X}kb:plan_file_name{Y},{Y}kb:file_id{Z}, {Y}kb:start_time{T1}, {Y}kb:stop_time{T2} WHERE T1>192067200 AND T1<

197247599 OR T2 > 192067200 AND T2<197247599 USING NAMESPACE kb=&http://protege.stanford.edu/kb#"; try { System.out.println("submitting test query"); String result = proxy.query(query2); System.out.println(result); AtlasResultSet results = new AtlasResultSet(result);


Satellite files (Metadata Queries):

44


45

Generar organizaciones virtuales Precio?Garantia?

Disponibilidad?

Coche de sustitución !

46

Business Case 1: Car Repair Business Case

• Context: – Repair damaged cars

– Negotiation between insurance and repair company• Speed, Price, Quality

• Method of repair, Selection of material,Paint, Coalition

• Now:– negotiation by hand

– long term (yearly)

• Challenge: – Automated negotiation

– short term (every claim)

– Include SLA

47

• Situation:• A lot of tricks to get money from insurance companies

• Now:• Ad hoc manual techniques

• Only pattern search on local or national scale

• Most tricks found on accident

• Challenge:• Automated fraud detection

Business Case 2:CarFraudGrid

48

Detección del fraude en seguros del coche

49

Known trick: Berliner Model

• Trick:• Buy damaged expensive car• Change some features• Have stolen cars have accidents

with it• Claim money from insurance

company of stolen car

• Search for:• Similar cars combined with similar

situations combined with similar participants

• National / International scale

50

Domain model

• Every insurance company uses its own database/domain model. Every claim database contains in some form important data about:

• * cars• * situation

• To find evidence we will look in claim history based on the current claim.

• We look at car for:Car

• * brand, e.g. Peugeot• * model, e.g. 307• * type, e.g. SW• * mileage• * license plate• * owner• * color• * chassisnumber• * constructionyear• * countryofregistration

Situation

* place of damage (angle of impact)

* description of accident

* time of accident

* accident location

* price of damage

* damaged objects

* witnesses ?

51

Conceptual Architecture

54

Ontology-based application that automatically generates and manages

knowledge portals for intranets and extranets

2. Permission-based

1. Semantic Driven

3. User Oriented

4. Interoperate

5. Synchronization with the ontologies

FP6-507482http://knowledgeweb.semanticweb.org/

IST-2001-34373 http://www.esperonto.net/

FP6-002006http://www.agentlink.org/

http://kw.dia.fi.upm.es/w3c/

FP6-511513http://www.ontogrid.net/ http://www.oeg-upm.net/

FP6-027595

Portal Web Semántico: ODESeW

55

O1

O2

Oi

Oj

Portal AdministratorsOntologies and Software

Extranet Users

Agents

Permission-based

Semantic Driven

User Oriented

External resources

Interoperability and management of Semantic portals

56

Ontologías para la Gestión de Proyectos

PersonOntology

Project Ontology

OrganizationOntology

EventOntology

DocumentationOntology

belongs to / is formed by

is author of / has author

has

pers

on le

ader

/

lead

s has associated event

is deliver in / has associated

generates / is generated by

participates in / is developed by

leads / has contractor leader

has authoring partner

has associated / is associated

has

asso

ciat

ed

is contact person /

has contact person

has contact person

has / is associated with

is a

ssoc

iate

d w

ith

has lead partic

ipanthas Q.A.

partner

has involved partner / works

in

wor

ks in

/ ha

s p

p

is in

volv

ed in

/ ha

s p

lead

er

is W

P le

ader

/ ha

s pe

rson

lead

er

57

Ontología de Documentos

Documentation

Article

PublicationManagement

DocumentationAdditional

Documentation

Agenda

Book

TechnicalDocumentation

Manual Slides Deliverable

Thesis

Templates PhDThesis

MasterThesis

CostStatement

ECTemplates

Fax Mail Minutes PeriodicReport

ProjectProposal

... ...

...

...

58

Ontología de Eventos

Event

Review

Management ProjectMeeting

InternationalWorkshop

InternationalConference

PMB MeetingEPMB Meeting

KW AreaMeeting

Industry AreaMeeting

Research AreaMeeting

Education AreaMeeting

KW PlennaryMeeting

59

Relaciones entre personas, proyectos y documentos

MilestoneWP workload

is made up of

has participant with workload has

Deliverable

has associated

is deliver in

is author of

has contact person

Person

Workpackage Task

works in is involved in

leads

is WP leader

60

Person

MilestoneWP workload

is made up of

has participant with workload has

Deliverableis author of

has associated

is deliver in

has contact person

Documentation

Ontology

Workpackage Task

works in is involved in

leads

is WP leader

PersonOntology

ProjectOntology

Relaciones entre personas, proyectos y documentos

61

Proceso de Generación del Portal Semántico

1. Construir las ontologías

2. Importar las ontologías en ODESeW

3. Crear tipología de usuarios y usuarios concretos

4. Definición de permisos para los distintos grupos de usuarios

5. Definir la visualización personalizada para cada grupo de usuario

62

http://knowledgeweb.semanticweb.org/

Acceso directo a las instancias de los conceptos más importantes

Descripción del proyectoOtros links a información útil

63

External User

• Visuliazation– Project description

• Objectives

• Workpackages

• Task

• Management Board

– List of deliverables• Description

• Download the public

documents

– List of partnets

– List of participants

– List of publications

– Calendar of events

64

Visualización basada en Semántica

Workpackage

Deliverable

has associated

65

Workpackage

Deliverable

has associated

has Q.A. partneris generated by

Organization

Visualización basada en semántica

66

Visualización de la instancia

Tipos de atributos

Nombres de

los atributos

Nombres

de las relaciones

Rango de las relaciones

Atributos

Relaciones

67

KW Users

• Kweb members Insert/update new information:– Events

– Upload deliverables

– Personal information

– Publications

• No access to – effort reports

– management documentation

68

Edición de los contenidos del portal (Atributos)

69

Inserted values

Potencial values

Edición de los contenidos del portal (Relaciones)

70

Contenidos del portal

Ontology

Instances

KnowledgeWebOntologies

71

Managing director

• Monitoring progress report– Area overviews

– WP progress reports

• Effort report– Kweb year effort report

– Partner effort report

• Progress report draft generation

72

Progress Report Draft Generation

WP Progress & Effort Report FormHTML Format of the draft of the Progress Report

MSWord Format of the draft of the Progress Report

73

Reporting

Workpackage

Organization

workpackage workload

is workload on workpackage

is workload of

Annual Period Annual Effort

performed byperformed by

performed in

performed in

DeliverableOrganization

Annual Period

has associated

Deliverable.Contractual Date of Delivery

[Annual Period.Start date, AnnualPeriod.End date]

Documents

Some examples of ontology-based applications