Primer Taller en Grid Computing Universidad del Valle, Cali, Colombia January 2007 Semantic-OGSA Oscar Corcho University of Manchester.

Primer Taller en Grid ComputingUniversidad del Valle, Cali, Colombia

January 2007

Semantic-OGSA

www.ontogrid.eu

Oscar CorchoUniversity of Manchester

2Primer Taller en Grid Computing. Universidad del Valle, Cali, Colombia. January 2007

Outline

OntoGrid and Semantic-OGSA (S-OGSA)The S-OGSA modelS-OGSA capabilities and mechanismsLifetime specification

S-OGSA scenarios of use Semantic Provisioning Services Conclusions and Future Work


EU-STREP Project OntoGrid

Middleware for the Semantic GridMetadata Storage & Querying Ontology AccessAnnotation

• Data and provenance

• ServicesBusiness Process MonitoringNegotiation and Coordination

Applications Insurance SettlementSatellite Image Quality

Analysis

SEMANTIC OGSACapabilites & Behaviors for

Semantic GridsPrincipled way of realization

And other applications being analysed


CombeChem

Semantic Grid trajectory

Time

Efforts

Implicit Semantics1st generation

SRB

Implicit SemanticsOGSA generation

GGF Semantic Grid Research Group

Many workshops

Systematic Investigation Phase

Specific experimentsPart of the Architecture

Dagstuhl Seminar

Grid Resource Ontology

Semantic Grid workshops

Pioneering PhaseAd-hoc experiments, early

pioneers

Demonstration Phase


From the pioneering phase to the systematic investigation phase

In the pioneering phase...Ontologies and their associated technologies are not completely

integrated in the Grid applications• They are used as in Semantic Web applications

But there are distinctive features of Grid applications• Distribution of resources• Scale• Resource management and state• ... (non exhaustive and non compulsory list)

In the systematic investigation phaseWe have to take these features into accountAnd incorporate semantics as another Grid resource

Our proposal is: S-OGSA


S-OGSA Design Principles

• Conceptual: reference architecture that can be applied to any grounding (WSRF, WS-Man, WS-I+, etc.)

• Parsimony: Architecture as lightweight as possible: minimise the impact on tooling, not dictate content

• Extensibility: Extensible and customisable as opposed to complete and generic architecture

• Diversity : Mixed ecosystem of Grid and Semantic Grid services. Semantics Ignorant, Semantics aware but incapable, Semantics aware and capable

• Uniformity: Everything is OGSA compliant. Our services are Grid services, knowledge and Metadata are Grid Resources.

• Multiform-Multiplicity: Any resource can have multiple descriptions and any description can be in different formalisms

• Enlightenment: Straightforward migration path


S-OGSA

Semantic-OGSA (S-OGSA) is...Our proposed Semantic Grid reference architectureA low-impact extension of OGSA

• Mixed ecosystem of Grid and Semantic Grid servicesServices ignorant of semanticsServices aware of semantics but unable to process themServices aware of semantics and able to process (part of) them

• Everything is OGSA compliant

Defined by • Information model

New entities

• CapabilitesNew functionalities

• Mechanisms How it is delivered

Model

Capabilities Mechanisms

provide/consume

expose

use


S-OGSA Model. Semantic Bindings

Model

MechanismsCapabilities


METADATAas SemanticAnnotations

S-OGSA Model Example

Model



Optimization

Execution Management

Resourcemanagement

Data

Security

Information Management

Infrastructure Services

Application 1 Application N

OG

SA

Sem

antic

-OG

SA

Semantic Provisioning

Services

From OGSA to the S-OGSA

Ontology

ReasoningKno

wle

dge

Metadata

Annotation

Sem

antic

bin

ding

Semantic Provisioning Services

Model



Semantic ProvisioningService

Knowledge Resource

Grid Entity

Semantic Binding

Grid ServiceIs-a

0..m0..m

1..m1..m

Semantic aware Grid Service

consume

produce

0..m0..m

1..m1..m

uses

WebMDS

SAMLfile

DFDL file

JSDL file

Is-a

Knowledge Entity

Is-a

Ontology Service

Is-a

Reasoning Service

Semantic BindingProvisioning Service

Annotation Service

Metadata Service

Grid Resource

OGSA-DAI

CASIs-a Is-a

Is-a

Is-a

Knowledge Service

Is-a

Ontology

Rule set

Knowledge Semantic Grid Grid

S-OGSA Model and Capabilities. The complete picture

Model



OntoKit: An implementation of S-OGSA


OntoKit: An implementation of S-OGSA

OntologyRole-based

AuthZ

Semantically Aware


S-OGSA Patterns. Semantic-ignorant service

Lifetime

MetadataService

OntologyService

Service

ResourceMetadataSeekingClient

Properties

Others….

Access/Query MetadataRefers to

Resource props

Model



S-OGSA Patterns. Semantic Aware but Incapable Service

Lifetime

MetadataService

OntologyService

Service


Properties

Others…

Access/Query Semantic Bindings

Refers to

Get Semantic Binding Pointers

2

1Resource

properties

Model



S-OGSA Patterns. Semantic Aware and Capable Service

Lifetime

MetadataService

Service


Properties

Others…

Access/Query Semantic Bindings1Semantics

1.1

Farm out request

Semantic aware interface

OntologyService

Model



S-OGSA Grounding. Grid Ontology and S-OGSA Ontology

Grid OntologyCommon set of ontologies

to describe Grid entities (resources and services)

Based on work from UniGrids

Effort to be continued by OntoGridAvailable in OntoGrid’s

CVS


S-OGSA Metadata Access/Management Protocols

SB Factory

Client

Semantic Binding

Metadata Query

SBSB

SB

create

Query w/o Inference, UpdateContent

Query( over unified view)

WS-RP: Get/Set/Query Properties

WS-Addressing: epr

RDFRDF

create

query

Inspect-props . . .

query

Semantic Binding Service Suite

WS-RL: Destroy , SetTerminationTime

WS-RL ++: archive

WS-Notif: Subscribe / Notify


Semantic Binding Service. Lifetime Specification

What happens if... ...any or all of the Grid entities it refers to disappears?

• Instrument and planning files for satellites do not disappear

• Insurance contracts, cars, repair companies, etc., may disappear

...the Knowledge entities disappear or evolve?• Ontologies may change

... a SB is no longer available (its content is not useful any more)? • Damage claims: add witness reports, improve info about location,

create new hypothesis...

When do/should SBs become invalid? How often should this be checked?

What is the status of the content of a SB (e.g., content checked, stable, unchecked, etc.)?

Is a SB always active or can it be archived after a period of time? Satellite data that is not used after some time


Semantic Binding Service. WS-SBResourceLifetime

Lifetime specification based on WS-ResourceLifetime

Extension with Resource properties

(state) Updates Archive Notifications

SB Housekeeping service

ContentRefsProbablyStale

Stable

Destroyed

updatedOntology

Stale

Archived

SB Checked: stale

destroyedOntology

SB Checked: OK

archive

External Event

Internal Event

destroy

and it disappears

GridReferencesOutdated

Updated/destroyedGridEntity

updateGridEntityRefs

allGridEntitiesDestroyed

updateSBContent

SB Checked: stale

scheduledUpdate [time]

updateSBContent

destroy

archive


WS-SBResourceLifetime vs WS-ResourceLifetime

WS-SBResourceLifetime

- archive- setUpdateTime

WS-ResourceLifetime

- setTerminationTime- destroy

Basic Operations- createSemanticBinding (Factory)- addGridEntityReference/removeGridEntityReference- addKnowledgeEntityReference/removeKnowledgeEntityReference- getContent- updateSBContent- query- queryWithInference


Update Notifications

From entities to Semantic Binding

SemanticBindingService

EPR

key............................

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

key............................

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

Lifetime

Service

Resource

Properties

Others….

Resource props

Polling of resource property[lastModificationTime]

Grid Entity

Knowledge Entity

Lifetime

Service

Resource

Properties

Others….

Resource propsPolling of

resource property[lastModificationTime]


Update Notifications

Semantic Binding Update Description: Updates in the content or in the state of a Semantic

Binding Message content:

• updateTime

• updateType [stateChange,contentChange]

• newState [any of the ones defined in the state machine]

• updateReason

SemanticBindingService

MetadataService

EPR

key............................

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

key............................

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

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

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

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

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

SBHouseKeepingService

Check that SB content is still

valid


Outline

Background The Grid and its characteristicsOpen Grid Services Architecture-OGSA Grid Standardization ActivitiesSemantic Grid




Satellite Use Case: Technical issues

SpaceSegment

Ground Segment

DMOP files

Product files

SATELLITE FILES:



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... ...


Satellite Use Case: Deimos Integrated Prototype

WebDAV

WS-DAIOnt-RDF(S)

SatelliteDomain Ontology

Satellite FileWebDAV client

e.g. MS Windows Explorer HTTP PUT

Metadata Service

QUARC-SG client JSP

2

UTC2SecondsSoaplab

3

45

7

2

1

1

3

6

Convert time to canonical representation

Annotate file

Obtain ontology

Type metadata

Store

Query

Convert time to canonical representationInput

criteria

Copy satellite file

Metadata generation processMetadata querying process



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.



Satellite Ontology (General view)



Satellite Ontology (Hierarchies)


Planning (DMOP) RECORD parameters



<fhr><FILENAME>"DMOP_SOF__VFOS20060124_103709_00000000_00001215_20060131_014048_20060202_035846.N1"</FILENAME><DESTINATION>"PDCC"</DESTINATION><PHASE_START>2</PHASE_START><CYCLE_START>44</CYCLE_START><REL_START_ORBIT>404</REL_START_ORBIT><ABS_START_ORBIT>20498</ABS_START_ORBIT></fhr>............................<EVENT_TYPE>GOM_PAU</EVENT_TYPE><EVENT_ID>"GOM_PAU_00000000011446"</EVENT_ID><NB_EVENT_PR1>1</NB_EVENT_PR1><NB_EVENT_PR3>0</NB_EVENT_PR3><ORBIT_NUMBER>20527</ORBIT_NUMBER><ELAPSED_TIME>5970047</ELAPSED_TIME><DURATION>65881</DURATION></gen_event_params></dmop_er_gen_part></dmop_er></FILE>


Satellite files: XMLed DMOP (PLANNING) FILES

Not yet transformed RECORD parameters.

Parameters NOT needed to be transformed at this moment

RECORD ID transformed to XML

RECORD parameters

transformed


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>

[...]




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



Satellite 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 !!


Namefile (Product):

RA2_MW__1PNPDK20060201_120535_000000062044_00424_20518_0349.N1"

Corresponds to:


Satellite files: PRODUCT filename


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>[...]



// 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):

http://195.134.67.205:8080/AtlasService/services/MetadataService






Timeline Planning-Product Generation:


Insurance Grid

Business values:• Value (cost reduction, billing)• Time to market / speed of implementation• Ahead of competitors• Fit within (human and technical) organization• Innovation drive

Solve existing problems:• Making processes more efficient with a new approach• (more) Reliable / Accepted• Proven / Cheaper • -> CarRepairGid

Solve problems that could not be solved before:• Lack of trust/ Unfamiliar• Politics • Technical / organizational limitations• -> CarFraudGrid


Business Case 1: Car Repair Business Case

Context: Repair damaged carsNegotiation 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


S-OGSA Scenario. Insurance settlement

Data and resources scenarios Register Repair Co. contract at

CarRepairGrid. Select Repair Companies for negotiation

Metadata scenarios Calculate offer by a Repair Company

(damage report) Judge Invoice sent by Repair Company

Process management scenarios Multi issue negotiation between Repair

Companies (repair) Multi issue negotiation between >3

insurance companies (Recovery) Services scenarios

Provide Policy Information Check coverage

Security scenarios Check client registration at insurance

companies Check Car Theft - automatic check on car

identity i.e. frame numbers and parts


S-OGSA Scenario. Insurance settlement

WS-DAIOnt

Negotitation Service (Manager)

JobNegotiation client

1

2

Do Negotiation

Atlas

RDF

RDFRD

F

RDF

RDF

RDFRD

F

RDF

RDF

RDF

InsurranceCo DB

Motor Vahicles

Car Parts

Repair CO. 1 (Nego. Srvc. Contractor)



Job + ContractorList

Job

Job

Cfp

Cfp

Cfp

propose Offer

Refuse

proposeOffer

2

2

4

4

4

accept5

Reject5

WS-DAIOnt

Car Repair

DB

RDF

RDFRD

F

RDF

RDF

RDF

Car Repair

DB

3 calculatePrice

3 calculatePrice

3 calculatePrice

Retrieve public Job desc.

LegacydatabasesLegacy

databases


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


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


Car Fraud Business Case Motivation


Car Fraud Business Case Motivation


Conceptual Architecture


Suggested Approach: Use case


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 ?


Ontology-based Role-based Authorisation

Insurance Security scenario cast as role based Grid Access Control Scenario.

Role based Access Control Policy is:Good Reputation Drivers are allowed to ask for an insurance

policy. Bad Reputation ones are not. VO ontology based on

KaOS ontologies (Actors, Groups and Actions)Role definitons

• Extend ontology with domain-specific classes and properties• Define roles wrt these extensions

E.g., a blacklistedDriver is a driver that has had at least 3 accident claims in the past

E.g., a goodReputationDriver is a driver that has been insured at least by one trusted company and that has had at most 2 accident claims

The Access Control Function uses a DL classifier to obtain roles of a Subject.


WS-DAIOnt

XACML_AuthZService(PDP)

CarFraudService (PEP)

XACML AuthZ Request

getInsurancePolicy

VO Ontology Class Hierarchy -RDFS

RDF

RDF

John Doe has had 2 distinct accidents

Role OpMapping

Pellet Reasoner

Obtain Semantic Bindings of John Doe

Obtain all classes that are subclass of ROLE

Classify John Doe wrt VO ont

Lookup whether the ROLE that is inferred permits or not

XACML AuthZ Response

1

2

3

4

5

6

7

Semantic BindingService

PIPProxy

PDPProxy

VO OntologyOWL

S-OGSA Scenario. Authorisation

8 Result or Exception

/C=GB/O=PERMIS/CN=User0


WS-DAIOnt



XACML AuthZ Request

getInsurancePolicy


RDF

RDF


Role OpMapping

Pellet Reasoner






1

2

3

4

5

6

7


PIPProxy

PDPProxy

VO OntologyOWL




WS-DAIOnt



XACML AuthZ Request

getInsurancePolicy


RDF

RDF


Role OpMapping

Pellet Reasoner






1

2

3

4

5

6

7


PIPProxy

PDPProxy

VO OntologyOWL




WS-DAIOnt



XACML AuthZ Request

getInsurancePolicy


RDF

RDF


Role OpMapping

Pellet Reasoner






1

2

3

4

5

6

7


PIPProxy

PDPProxy

VO OntologyOWL




WS-DAIOnt



XACML AuthZ Request

getInsurancePolicy


RDF

RDF


Role OpMapping

Pellet Reasoner






1

2

3

4

5

6

7


PIPProxy

PDPProxy

VO OntologyOWL




WS-DAIOnt



XACML AuthZ Request

getInsurancePolicy


RDF

RDF


Role OpMapping

Pellet Reasoner






1

2

3

4

5

6

7


PIPProxy

PDPProxy

VO OntologyOWL



Ignorant of semantics

Semantic aware and capable of processing semantics

Semantic provisioning services

Semantic aware but incapable of processing semantics


Outline

Background The Grid and its characteristicsOpen Grid Services Architecture-OGSA Grid Standardization ActivitiesSemantic Grid




Conclusions

A principled Semantic Grid reference architectureLow-impact extension of OGSAMixed ecosystem of Grid and Semantic Grid services

Ontology and metadata technology... ... can be used in Grid applications ... has to be adapted for its use in Grid environments

• Grid-compliant (provide Grid protocols, interfaces, etc.)• Grid-aware (use of Grid technology)

First use cases being deployedStill far from large-scale (production) deployment


Our future work

Semantic Binding ServiceLifetime managementFine-grained AuthZ

Prototypes demonstrating Knowledge-Aware Grid ServicesOGSA-DAI semantic extensionsEGEE information service consolidating

heterogeneous information sourcesMeta-scheduler using semantic technologies

Enlightenment Guidelines about how and when to apply semantic

technologies in Grid systems


More information

Publications An overview of S-OGSA: a Reference Semantic Grid Architecture.

Corcho O, Alper P, Kotsiopoulos I, Missier P, Bechhofer S, Goble C. Journal of Web Semantics 4(2):102-115. June 2006

http://www.ontogrid.eu/. Deliverable D1.2v2

Source code http://www.ontogrid.eu/, For Downloading Distributions Access to CVS

Connection type: pserveruser: ontogridpassword: not neededHost: rpc262.cs.man.ac.ukPort: 2401Repository path: /local/ontogrid/cvsrootmodule: prototype


Questions

Thank you for your attention!

Questions?

Acknowledgements OntoGrid Consortium

• Pinar Alper, Ioannis Kotsiopoulos, Paolo Missier, Wei Xing, Ian Dunlop, Sean Bechhofer, Carole Goble

Primer Taller en Grid ComputingUniversidad del Valle, Cali, Colombia

January 2007

Semantic-OGSA

www.ontogrid.eu

Oscar CorchoUniversity of Manchester

Primer Taller en Grid Computing Universidad del Valle, Cali, Colombia January 2007 Semantic-OGSA Oscar Corcho University of Manchester.

Documents

sogsa semanticogsa sogsa

grid resources

sogsa slide

ogsa compliant

semantic web applications

pioneering phase

semantics aware

semantics ignorant