Semantic Grid Requirements for Ontology Technology

1
Oscar Corcho University of Manchester
OntoGrid Semantic Grid Tutorial Manchester,
February 2007
2
Outline

• Background
• The Grid and its characteristics
• Open Grid Services Architecture-OGSA
• Grid Standardization Activities
• Semantic Grid
• OntoGrid and Semantic-OGSA (S-OGSA)
• The S-OGSA model
• S-OGSA capabilities and mechanisms
• Lifetime specification
• S-OGSA scenarios of use
• Conclusions
• Agenda

3
What is a Grid?

• A grid is a system consisting of
• Distributed but connected resources and
• Software and/or hardware that provides and
  manages logically seamless access to those
  resources to meet desired objectives
• Infrastructure that will enable coordinated
  resource sharing and problem solving in dynamic,
  multi-institutional virtual organizations

Handheld
Supercomputer
Server
Data Center
Cluster
Workstation
Adapted from Hiro Kishimoto (GGF17 opening
keynote)
4
Virtual Organizations

• Dynamic confederations organized around common
  goals
• Diverse membership capabilities
• People, compute resources, data resources, etc.
• Diverse geographic distribution
• Sharing is well-controlled
• Minimum knowledge about physical characteristics
  of resources
• Construction of higher level capabilities via
  composition of existing ones similar to SOA

From http//www.globus.org
5
Grid Related Paradigms

• Cluster
• Tightly coupled
• Homogeneous
• Cooperative working

• Distributed Computing
• Loosely coupled
• Heterogeneous
• Single Administration

• Grid Computing
• Large scale
• Cross-organizational
• Geographical distribution
• Distributed Management

• Utility Computing
• Computing services
• No knowledge of provider
• Enabled by grid technology

Source Hiro Kishimoto (GGF17 opening keynote)
6
Open Grid Service Architecture - OGSA

• Cross cutting requirements
• Interoperable
• VO level
• Optimized
• Reliable
• Certain QoS Guarantee
• Scalable
• Available
• Extensible

• Characteristics
• Service Orientation
• Management operations
• Resource Representation/ State
• Lifetime

7
The Open Grid Services Architecture

• An open, service-oriented architecture (SOA)
• Resources as first-class entities
• Dynamic service/resource creation and destruction
• Built on a Web services infrastructure
• Resource virtualization at the core
• Build grids from small number of standards-based
  components
• Replaceable, coarse-grained
• e.g. brokers
• Customizable
• Support for dynamic, domain-specific content
• within the same standardized framework

Hiro Kishimoto Keynote GGF17
8
Grid Reality

• Requires experts to install, configure and
  maintain
• Not near the ambitious OGSA landscape in terms of
  cross-cut requirements

• Heavy use of XML

Virtual Homogeneity
OGSA - Vision
Realizations
. . . .
. . . .
9

• To realise the Next Generation Grid requires
  semantically rich information representation, the
  exploitation of knowledge, and
• co-ordination and orchestration that is aware
  of context and task

David Snelling, NextGRID, Fujitsu, OGF
Source Carole Goble
10
Semantic Grid. Motivation (II)
11
Dont we have Semantics in the Grid already?

• Its called metadata.
• Or vocabularies.
• Or glossaries.
• Its the state properties of a resource.
• Its in information services.
• And registries and catalogues.
• And configuration files.
• And policy definitions.
• And service level agreements.
• And file names.
• And file headers.
• And directory naming conventions

• And code libraries.
• And type systems.
• And schemas.
• And applications.
• And data formats.
• And best practice.
• And documentation.
• And workflows.
• And notification events
• And monitoring logs
• And embedded in XML tags
• And even ontologies!
• And protocols.
• And decision procedures.

12
Embedding and implicit meaning is the enemy of
shareability and reuse in an open and decoupled
and collaborative environment. Machine
processable descriptions are machine actionable
descriptions
13
In summary
Expressive models
Inference
Model fusion
Controlled vocabularies
Data fusion
Integration
Integration
Extensible metadata schemas that you dont have
to nail down
Annotation
Source Carole Goble
14
Metadata Matters

• Particularly for the following activities
• Provenance
• Systems Configuration
• Policy representation and reconciliation
• Resource discovery
• Using
• Annotation
• Open, flexible and extensible self describing
  schemas
• Lets describe my data set, or the output format
  of this tool, that changes all the time
• Lightweight, referable, non-flat schemas
• Decoupled, interoperable systems, which resist to
  syntactic changes
• Global naming schemes
• Data integration
• Resource models
• Policy models
• Reasoning
• Complex problems

15
The Semantic Grid
The Semantic Grid is an extension of the current
Grid in which information and services are given
well-defined and explicitly represented meaning,
so that it can be shared and used by humans and
machines, better enabling computers and people to
work in cooperation D. De Roure, et. al
Semantics in and on the Grid

• Web Sites
• www.semanticgrid.org
• Setting up the www.semanticgridcafe.org
• GGF Semantic Grid Research Group (SEM-RG)
• Mailing List sem-grd_at_gridforum.org

16
Semantic Grid trajectory
Demonstration Phase
Efforts
Systematic Investigation Phase Specific
experiments Part of the Architecture
Dagstuhl Seminar Grid Resource Ontology Semantic
Grid workshops
Pioneering Phase Ad-hoc experiments, early
pioneers
SRB
GGF Semantic Grid Research Group Many workshops
Implicit Semantics OGSA generation
Implicit Semantics 1st generation
Time
17
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 phase
• We have to take these features into account
• And incorporate semantics as another Grid
  resource
• Our proposal is S-OGSA

18
Decision making
Knowledge Discovery
Lots
Ontology building
Workflow discovery and design
VO mgt
Configuration
Semantics
Resource discovery brokering
Information linking
Flexible extensible metadata schemas
Provenance
Not much
General language annotation
Not much
Lots
Grid
19
Outline

• Background
• The Grid and its characteristics
• Open Grid Services Architecture-OGSA
• Grid Standardization Activities
• Semantic Grid
• OntoGrid and Semantic-OGSA (S-OGSA)
• The S-OGSA model
• S-OGSA capabilities and mechanisms
• Lifetime specification
• S-OGSA scenarios of use
• Conclusions
• Agenda

20
EU-STREP Project OntoGrid

• Middleware for the Semantic Grid
• Metadata Storage Querying
• Ontology Access
• Annotation
• Data and provenance
• Services
• Business Process Monitoring
• Negotiation
• Coordination

• SEMANTIC OGSA
• Capabilites Behaviors for Semantic Grids
• Principled way of realization

• Applications
• Insurance Settlement
• Satellite Image Quality Analysis

21
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

22
S-OGSA

• Semantic-OGSA (S-OGSA) is...
• Our proposed Semantic Grid reference architecture
• A low-impact extension of OGSA
• Mixed ecosystem of Grid and Semantic Grid
  services
• Services ignorant of semantics
• Services aware of semantics but unable to process
  them
• Services aware of semantics and able to process
  (part of) them
• Everything is OGSA compliant
• Defined by
• Information model
• New entities
• Capabilites
• New functionalities
• Mechanisms
• How it is delivered

Model
provide/ consume
expose
Capabilities
Mechanisms
use
23
S-OGSA Model. Semantic Bindings
Model
Mechanisms
Capabilities
24
S-OGSA Model Example
Model
Mechanisms
Capabilities
25
From OGSA to the S-OGSA
Application 1
Application N
Optimization
Security
Data
OGSA
Execution Management
Semantic-OGSA
Semantic Provisioning Services
Resource management
Information Management
Infrastructure Services
Model
Mechanisms
Capabilities
26
S-OGSA Model and Capabilities. The complete
picture
WebMDS
Annotation Service
Metadata Service
Ontology Service
OGSA-DAI
Grid Service
Semantic BindingProvisioning Service
Is-a
Knowledge Service
Reasoning Service
Is-a
CAS
Is-a
Is-a
Is-a
Semantic ProvisioningService
Knowledge Entity
Grid Entity
1..m
1..m
SAMLfile
uses
Is-a
Ontology
Is-a
Semantic aware Grid Service
Knowledge Resource
Grid Resource
DFDL file
Rule set
1..m
1..m
consume
produce
JSDL file
0..m
0..m
Semantic Binding
0..m
0..m
Model
Is-a
Mechanisms
Capabilities
Knowledge
Semantic Grid
Grid
27
OntoKit An implementation of S-OGSA
28
OntoKit An implementation of S-OGSA
Semantically Aware
OntologyRole-basedAuthZ
29
S-OGSA Patterns. Semantic-ignorant service
Ontology Service
Metadata Service
Refers to
Access/Query Metadata
Properties
Lifetime
Metadata Seeking Client
Resource
Resource props
Others.
Service
Model
Mechanisms
Capabilities
30
S-OGSA Patterns. Semantic Aware but Incapable
Service
Ontology Service
Metadata Service
Access/Query Semantic Bindings
Refers to
2
Properties
Lifetime
1
Metadata Seeking Client
Get Semantic Binding Pointers
Resource
Resource properties
Service
Others
Model
Mechanisms
Capabilities
31
S-OGSA Patterns. Semantic Aware and Capable
Service
Ontology Service
Metadata Service
Farm out request
1.1
Properties
Lifetime
1
Metadata Seeking Client
Access/Query Semantic Bindings
Resource
Semantics
Service
Others
Semantic aware interface
Model
Mechanisms
Capabilities
32
S-OGSA Grounding. Grid Ontology and S-OGSA
Ontology

• Grid Ontology
• Common set of ontologies to describe Grid
  entities (resources and services)
• Based on work from UniGrids
• Effort to be continued by OntoGrid
• Available in OntoGrids CVS

33
S-OGSA Metadata Access/Management Protocols
Semantic Binding Service Suite
create
SB Factory
WS-Addressing epr
create
SB
Semantic Binding
SB
WS-RP Get/Set/Query Properties
query
Client
SB
WS-Notif Subscribe / Notify
RDF
Inspect-props . . .
WS-RL Destroy , SetTerminationTime
WS-RL archive
Query w/o Inference, UpdateContent
query
Query( over unified view)
Metadata Query
34
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

35
Semantic Binding Service. WS-SBResourceLifetime

• Lifetime specification based on
  WS-ResourceLifetime
• Extension with
• Resource properties (state)
• Updates
• Archive
• Notifications

36
WS-SBResourceLifetime vs WS-ResourceLifetime

• Basic Operations
• createSemanticBinding (Factory)
• addGridEntityReference/removeGridEntityReference
• addKnowledgeEntityReference/removeKnowledgeEntity
  Reference
• getContent
• updateSBContent
• query
• queryWithInference

• WS-SBResourceLifetime
• archive
• setUpdateTime

• WS-ResourceLifetime
• setTerminationTime
• destroy

37
Notifications
38
Outline

• Background
• The Grid and its characteristics
• Open Grid Services Architecture-OGSA
• Grid Standardization Activities
• Semantic Grid
• OntoGrid and Semantic-OGSA (S-OGSA)
• The S-OGSA model
• S-OGSA capabilities and mechanisms
• Lifetime specification
• S-OGSA scenarios of use
• Conclusions
• Agenda

39
Satellite Use Case Technical issues
Space Segment
Ground Segment
SATELLITE FILES
DMOP files
Product files
40
Satellite Use Case Technical issues

• Comparison between planning and product
  generation

DMOP_File(n1) StartTime
DMOP(n1)_ File (StopTime)
DMOP_Filen(StartTime)
DMOP_Filen(StopTime)
Instr1 planning
...
DMOP_er (ORBIT_NUMBER, ELAPSED_TIME)
Instrn (RA_2) planning
...
DURATION
Instrn(RA_2) Product Generation
...
...
PRODUCT_data_gap
PRODUCT_FILE Start_time (SENSING_START)
PRODUCT_FILE Stop_time (SENSING_STOP)
RA2_CAL_1P Stop_time (SENSING_STOP)
RA2_CAL_1P Start_time (SENSING_START)
41
Satellite Use Case Deimos Integrated Prototype
Satellite File
2
WebDAV client e.g. MS Windows Explorer
WebDAV
HTTP PUT
3
Annotate file
1
Copy satellite file
Convert time to canonical representation
5
4

UTC2Seconds Soaplab
Obtain ontology
6
Type metadata
Convert time to canonical representation
Store
7
Input criteria
1
2
QUARC-SG client JSP
3

WS-DAIOnt-RDF(S)
Metadata Service
Query
SatelliteDomain Ontology
Metadata for annotation
Metadata generation process
Metadata querying process
42
Satellite Use Case Technical issues
Satellite files PRODUCT filename

• Namefile (Product)
• RA2_MW__1PNPDK20060201_120535_000000062044_00424_2
  0518_0349.N1"
• Corresponds to

43
Satellite Use Case Technical issues

• Satellite files Annotated PRODUCT FILE
• ...
• ltrdfDescription rdfabout"http//protege.stanf
  ord.edu/kb10605"gt
• ltrdftype rdfresource"http//protege.stanford
  .edu/kbProduct_file"/gt
• ltNS0file_namegtquotRA2_MW__1PNPDK20060201_
  120535_000044792044_00424_20518_0334.N1quotlt/NS0
  file_namegt
• ltNS0sensing_start rdfdatatype"http//www.
  w3.org/2001/XMLSchemaint"gt192110735lt/NS0sensing_
  startgt
• ltNS0sensing_stop rdfdatatype"http//www.w
  3.org/2001/XMLSchemaint"gt192115215lt/NS0sensing_s
  topgt
• ltNS0specific_product_header
  rdfresource"http//protege.stanford.edu/kb10608
  "/gt
• lt/rdfDescriptiongt
• ltrdfDescription rdfabout'http//protege.stanfor
  d.edu/kb10649'gt
• ltNS0file_namegtquotRA2_MW__1PNPDK20060202_160340
  _000058672044_00441_20535_0344.N1quotlt/NS0file_
  namegt
• ltNS0sensing_start rdfdatatype'http//www.w3
  .org/2001/XMLSchemaint'gt192211420lt/NS0sensing_st
  artgt
• ltNS0sensing_stop rdfdatatype'http//www.w3.
  org/2001/XMLSchemaint'gt192217287lt/NS0sensing_sto
  pgt
• ltNS0specific_product_header
  rdfresource'http//protege.stanford.edu/kb10652
  '/gt
• lt/rdfDescriptiongt
• ...

44
Satellite Use Case Technical issues

• Satellite files
• DMOP (PLANNING) FILES

FILE DMOP (generated by FOS Mission
Planning System) RECORD fhr
FILENAME"DMOP_SOF__VFOS20060124_103709_00000000_0
0001215_20060131_014048_20060202_035846.N1"
DESTINATION"PDCC" PHASE_START2
CYCLE_START44 REL_START_ORBIT404
ABS_START_ORBIT20498 ENDRECORD
fhr ................................ RECORD
dmop_er RECORD dmop_er_gen_part
RECORD gen_event_params
EVENT_TYPERA2_MEA
EVENT_ID"RA2_MEA_00000000002063"
NB_EVENT_PR11 NB_EVENT_PR30
ORBIT_NUMBER20521
ELAPSED_TIME623635
DURATION41627862 ENDRECORD
gen_event_params ENDRECORD dmop_er ENDLIST
all_dmop_er ENDFILE
45
Satellite Use Case Technical issues
Satellite Ontology (General view)
46
Satellite Use Case Technical issues

• Timeline Planning-Product Generation

47
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
• -gt CarRepairGid
• Solve problems that could not be solved before
• Lack of trust/ Unfamiliar
• Politics
• Technical / organizational limitations
• -gt CarFraudGrid

48
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

Metadata for data integration
49
S-OGSA Scenario. Insurance settlement
Negotiation client
Job
2
Cfp
Refuse
4
1
Do Negotiation
calculatePrice
3
Job Contractor List
accept
5
Job
Cfp

2
Retrieve public Job desc.
Negotitation Service (Manager)
propose
Offer
4
calculatePrice
3
Reject
5
Job
Cfp
2

WS-DAIOnt
RDF
RDF
Offer
RDF
propose
calculatePrice
4
3
InsurranceCo DB
WS-DAIOnt

Atlas

RDF
RDF
RDF
RDF
RDF
Legacydatabases
Car Parts
Legacydatabases
Motor Vahicles
Car Repair DB
Car Repair DB
50
Business Case 2CarFraudGrid

• 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

Metadata for data integration Metadata for
reasoning
51
Car Fraud Business Case Motivation
52
Conceptual Architecture
53
CFG Technical Design
I. Company A
1
DB
Damage Report
WS-DAIOnt
Local Semantic Adapter (Grid-KP or S-OGSA-DAI)
1
doc
Car Fraud Ontology
Red Flag Detector
Damage Report
Suspicious Case
Submit for fraud detection
6
2
decision
Semantic Binding Service
Fraud Diagnosis Service
S. Case Info
IC Info
query
. . . .
3
5
Do diagnosis
4
4
RDF Query for similar cases
RDF Query for similar cases
Company C Semantic Data Access Service
Company B Semantic Data Access Service
sql
sql
. . . .
. . . .
Local Damage Report DB
Local Damage Report DB
I. Company B
I. Company C
54
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.

Metadata for reasoning
55
S-OGSA Scenario. Authorisation
/CGB/OPERMIS/CNUser0
CarFraudService (PEP)
getInsurancePolicy
1
PIP Proxy
PDP Proxy
Result or Exception
8
XACML AuthZ Request
XACML AuthZ Response
3
7
Lookup whether the ROLE that is inferred permits
or not
XACML_AuthZService(PDP)
6
2
Obtain Semantic Bindings of John Doe
Semantic BindingService
Obtain all classes that are subclass of ROLE
RDF
4
Classify John Doe wrt VO ont
5
John Doe has had 2 distinct accidents
WS-DAIOnt
VO Ontology Class Hierarchy -RDFS
Pellet Reasoner
VO OntologyOWL
56
S-OGSA Scenario. Authorisation
CarFraudService (PEP)
getInsurancePolicy
1
PIP Proxy
PDP Proxy
Result or Exception
8
XACML AuthZ Request
XACML AuthZ Response
3
7
Lookup whether the ROLE that is inferred permits
or not
XACML_AuthZService(PDP)
6
2
Obtain Semantic Bindings of John Doe
Semantic BindingService
Obtain all classes that are subclass of ROLE
RDF
4
Classify John Doe wrt VO ont
5
John Doe has had 2 distinct accidents
WS-DAIOnt
VO Ontology Class Hierarchy -RDFS
Pellet Reasoner
VO OntologyOWL
57
S-OGSA Scenario. Authorisation
CarFraudService (PEP)
getInsurancePolicy
1
PIP Proxy
PDP Proxy
Result or Exception
8
XACML AuthZ Request
XACML AuthZ Response
3
7
Lookup whether the ROLE that is inferred permits
or not
XACML_AuthZService(PDP)
6
2
Obtain Semantic Bindings of John Doe
Semantic BindingService
Obtain all classes that are subclass of ROLE
RDF
4
Classify John Doe wrt VO ont
5
John Doe has had 2 distinct accidents
WS-DAIOnt
VO Ontology Class Hierarchy -RDFS
Pellet Reasoner
VO OntologyOWL
58
S-OGSA Scenario. Authorisation
CarFraudService (PEP)
getInsurancePolicy
1
PIP Proxy
PDP Proxy
Result or Exception
8
XACML AuthZ Request
XACML AuthZ Response
3
7
Lookup whether the ROLE that is inferred permits
or not
XACML_AuthZService(PDP)
6
2
Obtain Semantic Bindings of John Doe
Semantic BindingService
Obtain all classes that are subclass of ROLE
RDF
4
Classify John Doe wrt VO ont
5
John Doe has had 2 distinct accidents
WS-DAIOnt
VO Ontology Class Hierarchy -RDFS
Pellet Reasoner
VO OntologyOWL
59
S-OGSA Scenario. Authorisation
CarFraudService (PEP)
getInsurancePolicy
1
PIP Proxy
PDP Proxy
Result or Exception
8
XACML AuthZ Request
XACML AuthZ Response
3
7
Lookup whether the ROLE that is inferred permits
or not
XACML_AuthZService(PDP)
6
2
Obtain Semantic Bindings of John Doe
Semantic BindingService
Obtain all classes that are subclass of ROLE
RDF
4
Classify John Doe wrt VO ont
5
John Doe has had 2 distinct accidents
WS-DAIOnt
VO Ontology Class Hierarchy -RDFS
Pellet Reasoner
VO OntologyOWL
60
S-OGSA Scenario. Authorisation
CarFraudService (PEP)
getInsurancePolicy
1
PIP Proxy
PDP Proxy
Result or Exception
8
XACML AuthZ Request
XACML AuthZ Response
3
7
Lookup whether the ROLE that is inferred permits
or not
XACML_AuthZService(PDP)
6
2
Obtain Semantic Bindings of John Doe
Semantic BindingService
Obtain all classes that are subclass of ROLE
RDF
4
Classify John Doe wrt VO ont
5
John Doe has had 2 distinct accidents
WS-DAIOnt
VO Ontology Class Hierarchy -RDFS
Pellet Reasoner
Ignorant of semantics
VO OntologyOWL
Semantic aware but incapable of processing
semantics
Semantic aware and capable of processing semantics
Semantic provisioning services
61
Outline

• Background
• The Grid and its characteristics
• Open Grid Services Architecture-OGSA
• Grid Standardization Activities
• Semantic Grid
• OntoGrid and Semantic-OGSA (S-OGSA)
• The S-OGSA model
• S-OGSA capabilities and mechanisms
• Lifetime specification
• S-OGSA scenarios of use
• Conclusions
• Agenda

62
Conclusions

• A principled Semantic Grid reference architecture
• Low-impact extension of OGSA
• Mixed 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 deployed
• Still far from large-scale (production) deployment

63
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 pserver
• user ontogrid
• password not needed
• Host rpc262.cs.man.ac.uk
• Port 2401
• Repository path /local/ontogrid/cvsroot
• module prototype

64
Outline

• Background
• The Grid and its characteristics
• Open Grid Services Architecture-OGSA
• Grid Standardization Activities
• Semantic Grid
• OntoGrid and Semantic-OGSA (S-OGSA)
• The S-OGSA model
• S-OGSA capabilities and mechanisms
• Lifetime specification
• S-OGSA scenarios of use
• Conclusions
• Agenda

65
Agenda

• Semantic Grid middleware
• Ontology access (WS-DAIOnt-RDF(S)
• Focus on RDF(S)
• Grid ontologies
• Metadata management (Semantic Binding Service)
• Future of Semantic Grid
• Service-Oriented Knowledge Utilities
• Ongoing work on S-OGSA

66
Questions

• Thank you for your attention!
• Questions?
• Acknowledgements
• OntoGrid Consortium
• Pinar Alper, Ioannis Kotsiopoulos, Paolo Missier,
  Wei Xing, Ian Dunlop, Sean Bechhofer, Carole
  Goble

67
Oscar Corcho University of Manchester
OntoGrid Semantic Grid Tutorial Manchester,
February 2007