jeffery - Community Grids Lab

The Information and Knowledge
Layers of the GRIDs Architecture
Keith G Jeffery
Director, IT & Head, ITD
[email protected]
http://www.itd.clrc.ac.uk/
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
1
CLRC-RAL Site
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
2
CLRC
• RAL and DL
• e-Science
– Paul Durham
• e-Business and everything else
– Keith Jeffery
– e-Government, e-Information, e-Learning, eCulture…
– W3C and ERCIM
• UK Grid Support Centre
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
3
Structure of Presentation
• Proposition
• The Idea
• Planned Enhancements
– Issues to be dealt with
• Applications
– why use GRIDs
– target
– what has to be done
• Conclusion
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
4
Proposition (1)
• Most of the work to date on GRID
technology has centred on high performance
computing and metacomputing
• alternative approach: 3-layer view
– knowledge
– information
– computation / data
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
5
Proposition (2)
• Technologies from distributed computing,
database and IR, formal software
engineering, knowledge engineering…..
• Intersection with W3C
– web of trust
– semantic web
– web services
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
6
Proposition (3)
• permits pullthrough
– from e-Science grand challenges
– to e-business
• thus promoting sustainability and
widespread buy-in
– for greater benefit of commercial and noncommercial sectors
– and especially e-health, e-environment, eculture, e-learning…...
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
7
Structure of Presentation
• Proposition
• The Idea
• Planned Enhancements
– Issues to be dealt with
• Applications
– why use GRIDs
– target
– what has to be done
• Conclusion
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
8
Data to Knowledge
The GRIDs Architecture
Knowledge Layer
Information Layer
Computation / Data Layer
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
9
The Big Idea:
What it Provides
‘The Wall’
The GRIDs
Environment
User
Appliance
Plug-in
Personal Communication
Personal Shopping
Hobbies, family activities
Business Communication
Business Dealing
Business Information
PC
Palmtop
Mobile..
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
10
A POSSIBLE ARCHITECTURE
USER
The GRIDs
Environment
User
Metadata
Source Source
Metadata Agent
User
Agent
RESOURCE
SOURCE
©CLRC/ITD/Keith G Jeffery
Resource Resource
Agent Metadata
GRIDsN+N:San Francisco
20010804
11
Classification of Metadata
view to users
SCHEMA
NAVIGATIONAL
ASSOCIATIVE
constrain it
data
(document)
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
12
Structure of Presentation
• Proposition
• The Idea
• Planned Enhancements
– Issues to be dealt with
• Applications
– why use GRIDs
– target
– what has to be done
• Conclusion
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
13
Planned Enhancements (1)
• Full scalable directory
– (full graph including cycles, not tree)
– e.g. person <dates,role> orgunit <dates,role> project
• Authentication:
– multiple modes convergent to certificate
• Authorisation:
– by authenticated person / role
– against accessing / utilising services, sources, resources,
other users
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
14
Planned Enhancements (2)
• Metadata
– for description of
• users,
• sources (data / information/ software or services),
• resources (engines eg computation, visualisation or services)
– based on RDF/XML;
– using the Metadata 3 kinds classification
• schema,
• navigational,
• associative [descriptive, restrictive, supportive]
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
15
Planned Enhancements (3)
• Thesauri and Domain Ontologies
– based on DAML+OIL over RDF/XML?
– Beyond simple FOPL: F-logic?
• Web Tools (Services)
– (with functional signatures as interfaces)
• Intelligent Agents
– probably conforming to FIPA
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
16
Issues to be Dealt With
• Can we simplify the architecture so that
– all entities {users, sources, resources}
– are represented as services
– and define a metadata for description of
services (acting as a kind of service functional
signature)
• Is the CERIF model
suitable for the directory?
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
(www.cordis.lu/cerif)
20010804
17
Structure of Presentation
• Proposition
• The Idea
• Planned Enhancements
– Issues to be dealt with
• Applications
– why use GRIDs
– target
– what has to be done
• Conclusion
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
18
Applications
• The target application areas are e-business, e-commerce, elearning, e-publishing, e-health, e-environment, eculture….etc etc
• At the information layer includes database, information
retrieval, web (e.g. digital libraries sensu lato)
• At the knowledge layer includes decision support, advisor
systems, constraint-based process systems (e.g. virtual
organisations)
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
19
Applications: Why use GRIDs
• The GRIDs architecture can provide ubiquitous pervasive
homogeneous access to
– heterogeneous distributed data / information sources with
– data ==> information ==> knowledge enhancement and to
– computation or visualisation resources to generate (eg through data
mining) insight.
• It can also provide such access to heterogeneous
distributed engines (eg for computation or visualisation)
• It can also provide such access to services.
• All invisible to the end-user behind a helpful UI
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
20
Application Environment Target
• The target is
– user-friendly e-information and e-business
– more supportive, intelligent, easy to use and
integrated with lifestyle
– than current web-based solutions.
• This implies
– the user does not know (or care) from whence
comes the information or compute-power to
solve her problem
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
21
What has to be done to
Applications to use GRIDs
• Need to take legacy applications and
GRIDs-wrap them
• Developing applications will develop in this
direction to converge
• New applications can be built from the
beginning to this architecture
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
22
Structure of Presentation
• Proposition
• The Idea
• Planned Enhancements
– Issues to be dealt with
• Applications
– why use GRIDs
– target
– what has to be done
• Conclusion
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
23
CONCLUSIONS
• GRIDs technology will ‘come of age’ when:
– it is as / more ubiquitous than WWW
– it is as / more pervasive than WWW
– it provides the end-user with more leverage
than WWW
• implies when
– supported by mainstream IT companies
– used in commercial and non-commercial
©CLRC/ITD/Keith G Jeffery
GRIDsN+N:San Francisco
20010804
24