Factoring and Mapping the Research Domain Table of Contents

advertisement
Factoring and Mapping the Research Domain
A Report Commissioned by JISC and DEST
By Jane Hunter and Matthew Dovey
University of Queensland, University of Oxford
April 2006
Table of Contents
]
1.
2.
3.
4.
5.
6.
7.
8.
9.
Background and Introduction
Overview across Service Domains
Factoring of Service Genres within Service Domains
Factoring of Service Expressions and Service Patterns within Service Genres
e-Research Services
e-Learning Services
Overlap
Recommendations
References
1. Background and Introduction
]
The e-Framework is an initiative by the U.K's Joint Information Systems Committee (JISC), Australia's Department
of Education, Science and Training (DEST) to produce an evolving and sustainable, open standards based, service
oriented technical framework to support the education and research communities. The initiative builds on the eLearning Framework and the JISC Information Environment as well as other service oriented initiatives in the areas
of scholarly information, research support and educational administration. A briefing paper provides an overview of
the e-Framework and describes how the partners intend to use it. The current version of the e-Framework has
concentrated on factoring the services within the Learning and Teaching domain and includes those services
identified in the JISC Information Environment. There is an urgent need to include services from other domains particularly the Research domain.
The aims of this discussion paper are to:







Review the common functionalities of the Research domain in order to factor the set of services needed to
support these functions.
Review the current set of services in the e-Framework in order to identify where there are overlaps, new
services, near matches and conflicts (eg variants in terminology) to those services factored for the Research
domain.
For each service identified produce a draft abstract definition including a scope and definition statement that
articulates the scope and purpose of the service.
For each service identified do an initial mapping of the specifications and standards associated with the
implementation of that service and where possible point to any implementations and projects ? initiatives
which address this service.
Where possible and appropriate, develop clusters of services that will be recognisable to the Research
communities to support them in understanding and navigating the e-framework.
Identify priority areas on which focus the development of 'Reference Models' in two areas:
o 'quick win demonstrators' - areas where reference models can be rapidly developed to demonstrate to
the Research community the value of the reference model and e-Framework approach.
o 'pain points' - areas where the reference model approach might help address recurring problems or
issues, or move forward an issue.
Raise any issues or conflicts encountered in this process that need to be addressed which may fall outside the
scope of this work.
2. Overview across Service Domains and Subdomains
[Table of
Contents]
Learning/
Education
eLearning
Course Management
Activity Management
Curriculum
Development
Learner Profile Mgt
Learning Resource
Management
Assessment
Research/
Grid
eScience
Remote Instrument
VR/Immersive
e-Lab notebook
Visualisation
Simulation/Modelling
Computational
Job Management
Collaboration
AV Conferencing
Access Grid
Whiteboard
Chat
Email
Presence
Library/Information
Environment
Data/Metadata Capture
Provenance
Workflows
Ontology Services
Metadata Services
Registry Services
Search/Delivery
Notification
Personalisation
Presentation/Delivery
Information Integration
Search Services
Publishing
Annotation
Bibliography
Publication
Forum
Messaging
Wiki
Application Sharing
Organisational
Project Management
Personal Organisation
Personal
Development
Documentation
Digital Rights Management
Licenses
Languages
Content Management
Information Management
Digital Repository
Data Management
Preservation
Preservation Metadata
Obsolescence Detection
Emulation
Migration
Normalisation
IT
Services
Admin
Common
IT Services
Network
Management
Resource
Management
User Management
Group/VO
Management
Identifier/Resolver
System
Management
Service
Management
Software
Management
Financial/Accounting
Security
Authentication
Authorisation
Access Policies
Firewalls
Proxies
Certificates
3. Factoring of Service Genres within Service Subdomains
[Table of Contents]
Data/MetadataCapture
"Data/Metadata Capture" services are those services which facilitate and streamline the capture of data, events and metadata associated
with
eResearch or eLearning activities. They include services for capturing provenance and managing workflows, metadata, schemas and
ontologies.





Provenance
Workflows
Ontology Services
Metadata Services
Registry Services
Search/Delivery
"Search/delivery" services are those services are enable both the finding of resources through searching and browsing of repositories or
collections (pull)
as well as those that filter information feeds and deliver personalized information views based on users' preferences (push).





Notification
Personalisation
Presentation/Delivery
Information Integration
Search Services
Content Management
"Content Management" services are those that support the uploading, retrieval, description/indexing, organization and management of
data and information resources
within databases or digital repositories.


Information Management
Data Management

Digital Repository
Digital Rights Management
"Digital Rights Management" services are those that support the management of rights associated with content, data or software.
It includes services for defining, attaching and editing licenses as well as languages for defining licenses.


Licenses
Languages
eScience/eResearch
eScience or eResearch services are those specifically provided to enable researchers to capture, analyse, visualize and
model scientific data. We have distinguished these from "Grid" services which manage jobs, network and compute power.






Remote Instrument
VR/Immersive
Visualisation
e-Lab notebook
Simulation/Modelling
Computational
Collaboration
Collaboration services are those services that enable groups of physically distributed users to work together over networks.


AV Conferencing
Access Grid








Whiteboard
Chat
Email
Presence
Forum
Messaging
Wiki
Application Sharing
Preservation
Preservation services are those services that support the processes required to ensure long term access to digital
resources





Preservation Metadata
Obsolescence Detection
Emulation
Migration
Normalisation
Publishing
"Publishing" services are those related to either publishing content, reports, annotations or data - or managing references to such
publications.



Annotation
Bibliography
Publication

Documentation
eLearning
"eLearning" services are those services that support access to learning materials as well as the activities undertaken by both learners
and trainers in a managed learning environment






Course Management
Activity Management
Curriculum Development
Learner Profile Management
Learning Resource Management
Assessment
Organisational
"Organizational" services are those that enable users to organize their projects, activities and personal information



Project Management
Personal Organisation
Personal Development
Financial/Accounting
"Financial/Accounting" services are those administrative services that enable management of finances associated
with the online use of resources or services. They include:


Pricing
Usage Logging



Auditing
Charging
Billing/Invoicing
Grid/IT Services
"Grid/IT" services are those low-level services that support the management of a Grid environment or infrastructure.
They are typically invisible to end-users but available to and used by systems administrators.









System Management
Service Management
Software Management
User Management
Group/VO Management
Identifier/Resolver
Network Management
Job Management
Resource Management
Security
"Security" services are those services that enable data or resources to be protected against unauthorized access.






Authentication
Authorisation
Firewalls
Access Policies
Firewalls
Proxies

Certificates
4. Factoring of Service Expressions and Service Patterns within Service Genres
Annotation
Provides support for the creation, management and use of secondary metadata.
Peer review
Rating/assessment
Textual annotation
Spoken annotation
Hyperlink annotation
Semantic annotation
Assessment
Assess position of student in learning space. Could be via a testing service or by logging continual performance. An Assessment service
supports the use of automated assessments.
Storing, retrieving, deleting and updating Items (individual questions). Storing, retrieving, deleting and updating Sections (groups of
questions). Storing, retrieving, deleting and updating Assessments (groups of sections or questions). Publishing Assessments against a
Course, Module, or other unit of learning. Storing and retrieving Results from Assessments.
[Table of
Contents]
Middleware and tools implementing this functionality include:
Appropriate specifications include: IMS Question and Test Interoperability (QTI) provides data models for assessments, sections, items,
and results reports; OKI Assessment OSID provides APIs for managing banks of items, sections, and assessments, and for publishing
assessments.
Authentication
How to gain access, e.g. using an X.509 proxy certificate as proof of having passed an authentication process. Needs a unique identifier
to be passed to the services to support multi-user access. Service will normally presume an identifiable user rather than just a role.
Aspects of this service may be required to determine that the digital id being presented is actually being used by the real-world individual
who has the rights to use it. This is often achieved through the use of a pass phrase or other mechanism depending on the degree of
assurance required.
See additional services under Security.
Logon
Ask for access via userid, e-mail address, DN, password, smartcard, biometrics?
Logoff
Say: I'm finished for today.
Revokation revoke a user's or service's rights to access a system
Middleware and tools implementing this functionality include: Athens; OpenSSL; Globus GSI; Kerberos or Shibboleth tokens; MS
Passport.
Appropriate specifications include: OKI Authentication OSID; Lightweight Directory Access Protocol (LDAP); Public Key
Infrastructure (PKI); X.509l; CIM-users.
Authorization
Supports the management of access to resources by agents. Typically role-based method of access control.
Support for giving and revoking access rights to resources/ services by individuals and other services. Informing services whether
authenticated users or services have access to services when they request access. Important aspect of VO management.
VO membership Do I belong? or join me!
Role
Describe or create my role in this VO
Rights
Describe or create my rights in this role
Access
Do these rights gain me access to X?
Revokation
Revoke a user's or service's rights to access to X?
Middleware and tools implementing this functionality include: MyProxy, CAS, PERMIS, Shibboleth.
Appropriate specifications include: OKI Authorization OSIDl; CIM-users
AV Conferencing
One of the collaborative services. It includes functions like audio and videoconferencing.
Chat
Manages one on one messaging as well as multiple users.
Course Management
A Course management service allows applications or services to access and manage courses, modules and other units of learning. This
may be a specialisation of Group management.
Support creating, reading, updating and deleting units of learning. Support creating, reading, updating and deleting data regarding
membership of units of learning. Support creating, reading, updating and deleting people information.
Middleware and tools implementing this functionality include:
Appropriate specifications include: IMS Enterprise. IMS Enterprise Services (not yet available). OKI Course Management OSID,
Data Management
Search, find information about and ultimately access or publish data objects on the Grid, typically in a distributed file system or database.
Management of private work spaces is covered under File Mangement.
Distributed Query
Find data sets based on keyword query
Processing
Data Cache
Local/ remote temporary copy for private use
Data Replication
Copy a data set and mark it as master/ slave. Log copies.
Mobile Code
Move code to data rather than the other way.
Data input
Convert to electronic format
Markup
Automatically insert XML or other tags into data
Data mining
Insert trigger
Move special code to a database engine
Define Data
storage needs
A User will be able to define their storage needs and manage their local, scratch, workspace and archive space.
Note that data can be stored both locally and on remote machines
Search for data
A user will be able to search for data based on selection criteria and their access rights. Data will be made available
to individuals, groups or all users and may be selected from local space, workspace or archives, published or
private.
Review Data
Users will be able to review metadata about published or archived data subject to their access rights.
Select Data
Data will be selectable by users if they have the rights to access it. On selection of data, this will be available for
download, or use for rendering and visualisation. Access to data will be audited.
Publish data
A user will be able to publish raw data for others to share.
Archive Data
A user will be able to move published data into their workspace or archive so long as they 'own' the data or are
systems administrators
Archive
Executable
A user will be able to move published executables into archive so long as they 'own' the executables or are systems
administrators
Archive Workflow
A user will be able to move published workflows into archive so long as they 'own' the workflows or are systems
administrators
Review data
storage use
A user will be able to review the sotrage they are using and tidy their space.
Setup security for
data
A user will be able to add and edit the security rules for data both published and archived.
Mark data a
sensitive
Users will be able to mark data as sensitive, e.g. may need to be encrypted for moving.
Review audit of
data use
A user may review who has accessed their data and the actions taken on it - reviewed, run or downloaded
Backup Data
Data in workspace or archives will be automatically backed-up. Local data can be registered for automatic backup?
Provide data
provenance
Data generated within a project will automatically be provided with some provenance data. Users will have to
provide additional data, or provide full provenance data for other data imported in a project. This may require data
to be watermarked.
Provide metadata
Data generated within a project will automatically be provided with some metadata. Users will have to provide
additional data, or provide full metadata for other data imported onto a project.
Check data
integrity
The user will be able to confirm that the data, and metadata dincluding provenance are as originally generated/
provided.
Middleware and tools implementing this functionality include: SRB, DSpace, RLS, ...
Appropriate specifications include: OAIS
Digital Rights Management (DRM)
Supports the allocation and application of rights policies against resources, consuming data in a digital rights expression language
(DREL) to determine access. Works through Authorization services, and is generally intended to be called by Authorization
implementations as the result of a request to use a resource.
Support for the allocation and updating of rights associated with objects; Support for validation of the use of objects at run time.
Middleware and tools implementing this functionality include:
Appropriate specifications include: IEEE Digital Rights Expression Language; XRML; ODRL; CreativeCommons; CIM-users.
e-Publication
Range of services to support publication of research results and experiences for many purposes including adding to the scientific theory
and teaching.
Includes traditional formats such as research theses, papers and monographs but also Web and TV.
Middleware and tools implementing this functionality include:
Appropriate specifications include:
Email
Support for email management (as provided by IMAP, POP and SMTP)
Forum
Supports the use of asynchronous collaborative messaging, as offered by fora and message boards.
Group and VO Management
Defines membership of virtual organisations and their rights. In learning applications, a group management service is an abstraction of
course management, with applicability to groups other than units of learning.
Support creating, reading, updating and deleting groups. Support creating, reading, updating and deleting data regarding membership of
groups. Support creating, reading, updating and deleting people information. Group can index information about members, such as
profiles viewable by peers or instructors. Could also include items of profile information, including upload optional photo. Profile items
are viewable by others if permissions are set.
Set up an group
Creates a new VO to establish the security boundary for an group. Access to the group's resources
should be restricted to this VO
Add user to an group
The PI will be able introduce new collaborators to the group.
Remove a user from an group The PI will be able expel a collaborator from the group.
Add a resource/ data to an
group
The PI will be able introduce new resources to the group.
Remove a resource/ data to an
The PI will be able remove resources from the group.
group
Authorize a user/ action pair
Allow or deny the given user to carry out the requested action
Middleware and tools implementing this functionality include: CAS, VOM, VOMS
Appropriate specifications include: IMS enterprise, IMS enterprise services (not yet available), OKI group management OSID (not yet
available); CIM-users?
Identifier/Resolver
Service that allows the creation, assignment and management of identifiers (DOI, PURL, Handle) to resources (including management of
appropriate metadata about each identifier).
Assignment/ creation/ registration of identifier. Update/management of identifier mapping to URL and associated metadata. Also a
system support service.
Provides services for resolving identifiers into locations including OpenURL metadata, DOI, PURL, Handle etc. This includes
redirection to document delivery services, redirection to online bookshops, to local library services, and other discovery activities.
Resolver services will use institutional and individual preferences to determine resolution preferences. Used in context-sensitive linking.
Resolving identifier to the URL of the current location of a resource. Resolving metadata to a set of links to appropriate copies of a
resource. Providing links to value-added services based on metadata about resource.
Middleware and tools implementing this functionality include:
Appropriate specifications include: OpenURL; DOI; URI; PURL; Handle; OKI ID OSID
Middleware and tools implementing this functionality include: SFX
Job Management
Submit jobs to the Grid, log and monitor their status. This is different to the testing phase of executable management. Involves brokering
and scheduling, potentially as part of a workflow.
Input taken from IB project.
Define computation
resources required
A User will be able to define their computational needs and manage their allocations on multiple
computational resources
Locate resources
Users will be able to see what resources are available, and see what capabilities each offers.
Setup input parameters
for a job
A user will be able to setup the input parameters for a job either by uploading input parameter files or
entering information into a GUI for that job
Specify data
requirements
The users will be able to specify the temporary storage required for a given run, including source/destination
for streamed data. The security precautions to be taken for this data, e.g. encryption, can also be specified.
Submit a job
Submission of a job will be through easy to use interfaces requiring no knowledge of the architecture behind
it. A user may submit it to any project-accessible resource, e.g. NGS or to the test infrastructure
Specify steering
behaviour
A User can specify what parameters are to be monitored and what parameters can be steered. Checkpointing
behaviour must also be specified.
Check status of
submitted job
A user will be able to check the status of a job submitted to NGS or the test infrastructure
Select run parameters
for a workflow
A user will be able to set up the input parameters for a workflow either by uploading files for the workflow to
access or by entering the information into a GUI for that workflow.
Execute a workflow
Execution of a workflow will be through easy to use interfaces requiring no knowledge of the architecture
behind it.
Provide metadata
The user must provide metadata concerning the simulation
Check workflow status
A user will be able to check the status of a workflow.
Monitor state
Logging
resource usage vs. job details
Notification
Tell me when its finished or failed!
Middleware and tools implementing this functionality include: Globus; Condor; Platform Computing LSF; United Devices; Sun Grid
Engine
Appropriate specifications include: DRMAA; DAG; RSL; NPI; CI-apps; etc.
Messaging
Allows broadcast of messages to users and groups using appropriate communication technology.
A Messaging service should support handling requests to deliver a message to a specified recipient, delivering the content of the message
using a delivery technology appropriate to the context of the request, such as the preferences of the recipient, and available
communication channels.
Typically a Messaging service will deliver messages using Email, Chat, SMS, or possibly even by actioning a manual postal delivery,
such as to a "pigeon hole" within a department.
The main criteria for a successful Messaging service is that the requesting agent is able to send a message to a recipient without being
required to understand in advance the specific delivery mechanism that the service implementation will use.
Metadata Registry
Database service to register metadata based on a pre-defined data model. A metadata registry provides machine-readable information
about the metadata schemas in use by particular metadata-based services. The primary intention of this service is to allow service
consumers to automatically determine information about appropriate search terms and the structure of metadata records that will be
returned to them. However, metadata registries also provide a useful human-oriented service, allowing people to see what metadata
schemas are in use by which services - providing a basis for metadata schema sharing and re-use.
Providing machine-readable declarations of metadata schemas. Providing mappings between metadata schemas. Providing humanreadable view of metadata schemas. May be static or stream-based, e.g. metadata on the state of collaboration services streamed via a
notification service to keep views in sync. Not there are also other kinds of registries such as service registry, metadata schema registry,
etc.
Description What is the data and what is it for?
Provenance Deposited by who, when, why?
Location
Where can I get it and how?
Middleware and tools implementing this functionality include:
Appropriate specifications include: RDFS; OWL.
Network Management
Variety of services related to networks as opposed to locally managed computers or databases. Infrastructure hardware the enables
communication between components.
Monitoring
Protocol
Unicast, multicast, etc.
Optimisation
Routing
DNS
Reservation
VPN management
QoS
guarantee a particular behaviour
Middleware and tools implementing this functionality include: NWS; IPPM; iperf; DMF; GridMon; etc.
Appropriate specifications include: SNMP
Personal Development
Supports the management of a learner's personal development plans and personal development records.
Personalisation
Allow administrator or user to select a new skin/ theme from a list of installed themes. Themes are associated with images (e.g. top left
corner of site, bullets and lines) and styles (colour schemes/ css). A large collection of themes should be available to reflect different
disciplines and of course an institution's logo and associated colours.
Could upload components into registry, e.g. logos.
Middleware and tools implementing this functionality include:
Appropriate specifications include:
Presence
Provides information about a user's on-line status, much like a chat application.
Search
A search service allows application services to support resource discovery by sending a query formatted according to a particular query
syntax and returning a result set formatted according to a particular syntax. We want to be able to support distributed searching.
accept query, return results
Middleware and tools implementing this functionality include:
Appropriate specifications include: SOAP; XML; SRU; SRW; ZING; Z39.50; XQuery; RDF; Dublin Core; UK LOM Core; IEEE LOM;
IMS Digital Repositories Specification.
User Management
Whilst roles need to be more rigourously defined, we introduce the concept of a group (or project) PI who will carry out or delegate the
tasks of accepting users and assigning roles/ rights to them with associated resources.
Input taken from IB project
Create a user A systems administrator or an group's PI will be able to set up user accounts for the project and manage groups of users.
Edit a user
A user account will be editable
Set up user
rights
A user will have their access rights set up and they will be associated with a group that will have generic rights.
Subsequent rights will be allocated by the PI of any group in which that user is to participate.
Revoke user
Users accounts will be disabled as required.
rights
Middleware and tools implementing this functionality include:
Appropriate specifications include:
Visualisation and Interactive Services
Visualise data on Grid resources, either using a remote or local tool. Data may be output from a Grid job or even used for steering the
application.
Input taken from IB project.
Data transformation
Search for visualisation
tools
A user will be able to select a visualisation tool based on agreed selection criteria
Review visualisation
tools
A user will be able to review the metadata about a visualisation service before selecting it.
Select visualisation
methods
On selecting a visualisation method, a user will be able to render and view results
Compare results
Users will want to be able to compare results from a job with results from earlier runs, other executables,
experimental results etc. Comparisons could vary from side by side visualisation to overlaying/ merging
different visualisations.
Publish visualisation
method
A new visualisation tool or service will be publishable for others to use.
Select data to be
visualised
Setup user defined
filtering
The user specifies the filtering algorithms, and there should be defaults
Setup user rendering
Render data
View results
A user will be able to view results using selected visualisation tools and data sets
Invoke collaborative
visualisation
A user will be able to set up and commence collaborative visualisation selecting a user or group to work with.
Perform collabrative
visualisation
As the data is viewed and interacted with, all users will be able to see the changes.
Steer visualisation
A user will be able to interact with a visualisation to steer a procedure.
Generate Movies
A user will be able to generate movies from timeslice data using a simple to use tool
Direct Manipulation
A user will be able to use different methods for direct manipulation of visualisation, appropriate to different
systems
Ability to create
visualisation scenarios
A user is able to define visualisation scenarios
Middleware and tools implementing this functionality include:
Appropriate specifications include:
Whiteboard
Supports the use of collaborative tools that focus on shared editing and idea sharing, such as electronic whiteboards.
Workflow Management
Supports creation and management of multi-service transactions or aggregations of choreographed services, sometimes for administrative
purposes and often to direct a user through a complex procedure. Users can create workflows from components which are executables
with defined states and input/ output requirements. These can be published via a registry along with appropriate metadata for adaptation
and re-enactment by other group or general users.
Supports appropriate usage pattern of a collection of Web Services, in such a way that the resulting composition describes how to
achieve a particular business process. Supports the interaction pattern of a collection of Web Services; in this case, the result is a
description of the overall partner interactions. Additional input taken from IB project.
Composition/
development
Experts or users will be able to create a workflow by selecting workflows and associating them with other
workflows in a graph like coordination structure. This process can be facilitated by a user friendly GUI.
Edit an workflow
Users will be able to edit a workflow using a GUI.
Test an workflow
On selecting a workflow, published or not, a user will be able to test it on the infrastructure provided
Create a registry
A 'PI' can create a registry for their group (i.e. restricted to group members only). Initially, their registry contains
only published workflows (copied from the master registry).Metadata is required.
Add a workflow
User is able to upload a workflow to a group's registry, providing they are a valid user with an e-Science certificate
and have been authorized to do so by the PI. Metadata is required.
Delete a workflow
User is able to remove an workflow from their registry providing they 'own' the workflow or have been authorised
to do so by the PI.
Replace a
workflow
User is able to overwrite a workflow with a new one (= Add + Delete). Metadata is required.
Version and
workflow
Users will be able to version their workflows and keep historic information for later retrieval.
Search for a
Users will be able to search for workflows with selection criteria.
workflow
Review a
workflow
Users will be able to review metadata about a workflow before selecting
Select and edit a
workflow
On selecting a workflow, the user will be able to run it in the infrastructure provide. The user can also edit the
workflow and will be able to publish it once completed.
Test a workflow
Users will be able to select a workflow and test it on the infrastructure provided
Publish a
workflow
Workflows will be publishable by users so that they may be accessed by other users in or beyond their group.
Publishing a workflow will require the user to provide test data (?) and metadata for that workflow for later
retrieval. Accepted (peer review?) workflows will be added to the master registry.
Add metadata to a
Users may add metadata to a workflow on publication or in their group's registry.
workflow
Setup security for
a workflow
On adding or publishing a workflow, a user will be able to set access rights to that workflow, either by individuals,
groups or user attributes. Validity of user will be determined by this security and also the security of individual
executables within the workflow.
Review audit of
workflow use
A user may review who has accessed a workflow and the actions taken on it - reviewed, run or downloaded
Languages and
programming
flexibility
Compiler/
Interpretor
optimisation
Runtime engine
support execution
Middleware and tools implementing this functionality include: Taverna, Kepler, Triana, DAGMan, GridANT
Appropriate specifications include: OKI Workflow OSID; Web Services Flow Language (WSFL), Business Process Execution Language
(BPEL), SCUFL, Xlang, BPEL4WS, DPML, XPDL, GSFL, WSCL, OWL.
5. Mapping between e-Research Services and e-Learning Framework Services
The table below lists the complete set of eResearch services in column 1 and the mapping to e-Learning Framework services
(both common and learning domain services) in column 2.
eResearch/eScience Services
Management Services
Identifier Manager
Resolver
ELF Services
Group/Virtual Organisation Management
Create group
Specify Group/Institutional Profile
Add user/member to group
Add resource to group
Role management
Remove user/member from group
Dissolve group
Access information about groups
Group
User Management
Create user (login/password)
Person
Identifier
Resolver
Member
Role
[Table of
Contents]
Identity Management
Edit
Set user profile/preferences
Set user access rights
Associate user with groups
Manage roles
Disable user
Access user profile/information
Job Management
Setup job parameters
Submit job
Job scheduling
Job queuing
Job monitoring
Change parameters
Check status
Recovery
Network Management
Monitoring
Protocol (unicast, multicast, etc.)
Optimisation
Routing
User preferences
Roles
Scheduling
DNS
Reservation
VPN Management
QoS (Quality of Service)
Resource Management
Grid resource scheduling
Resource monitoring
Resource service/maintenance
Diagnostic services
Fault Management
Instrument Management
Software/System Management
Version control
Bug tracking
Documentation
Service Management
Add service to registry
Describe service
Service description language
Remote service from a registry
Discover service
Service Registry
Get service description
Download service
Invoke service
Test service
Compose services
Choreograph services
Data Management
Data input
Data storage
Data compression
Data replication
Data transfer
Data synchronisation
Data backup
Data cleaning
Data reformatting
Data fusion
Real-time data stream filtering
Data verification/validation
Version control
Filing
Information Management
Information access
Packaging
Format Conversion
Information aggregation
Information content registration
Information query
Information metadata
Information presentation
Information notification
Information update
Digital Rights Management
Licensing (Creative Commons,
Science Commons)
Define
Attach
Edit
Revoke
Languages (XRML, ODRL, IEEE Digital Rights
Expression Language)
DRM
Metadata Services
Indexing/Metadata extraction
Semantic labelling
Automatic Recognition
Speech, image, video
Automatic segmentation
Metadata Management
Metadata input tools
Metadata editing
Metadata standards
Metadata validation
Metadata schema registry
Metadata harvesting
Terminology
Terminology mapping
Dictionary
Thesaurus
Thesauri management
Glossary
Metadata Schema Registry
Harvesting
Terminology
Mapping
Ontology Services
Ontology editors
Ontology browser/viewer
Ontology validation
Ontology hamonisation/linking
Ontology registry
Rules editor
Reasoning/inferencing engine
Ontology-based search interfaces
Terminology
Workflows
Workflow
Mapping
Rules
Construct
Service composition
Edit
Test
Delete
Publish
Languages
Compiler
Runtime engines
Learning Flow
Sequencing
Provenance/Audit Trail
Logging
Monitoring
Transactions
Messaging
Retrieve
Present
Search/Discovery Services
Search/Querying interfaces
Keyword searching
Ontology-based searching
Hypothesis testing interfaces
Query-by-example (QBE)
Logging
Tracking
Context
Search
Federated Search
Query-by-content (QBC)
Browse/navigation
Data exploration
Matching and ranking
Data mining
Knowledge extraction
Portal services
Digital Repository Services (e.g. Fedora, DSpace, Greenstone,
ePrints)
Upload/ingest/deposit
Describe
Validate
Store
Access
Retrieve
Content Management
Information Integration
Query mediation
Hypothesis testing
Decision support services
Federated Search
Presentation Services
Presentation editor
Packaging
Dynamic presentation editor
Personalisation
Layout manager
Presentation rules
Notification/Delivery Services
Event notification
RSS feeds
Web casting
Recommender services
Alert
Personalised delivery/filtering services
Alert
Messaging
Security
Authentication/identity management
Authorisation
Access policies
Define
Attach
Edit
Reuse
Privacy
Confidentiality
Integrity
Authentication
Authorisation
Rules
Trust
Assurance
Delegation
Firewalls
Proxies
Certificates
Collaboration
AV Conferencing
Polycom, Skype
Access grid sessions
Chat
Whiteboard
eMail
Presence
Forum
Message board
Instant messaging
Phone
Application/Document sharing
Collaborative editing
Collaborative ontology
Development
Collaborative annotation tools
AV Conferencing
Chat
Whiteboard
E-Mail management
Presence
Forum
Messaging
Wiki
Collaborative modelling, simulation, steering
Remote Instrument Services
Discovery
Booking
Access
Real-time data capture and analysis
Tele-observation (remote observation)
Tele-operation (remote control)
Visualisation
Select data, parameters and ranges
Choose presentation modes
2D/3D graph plotting
Save visualisation
Simulation/Modelling
Define or select mathematical model
Store model
Choose model
Set parameters
Run model
Steer model collaboratively
Virtual Reality or Immersive Environment
Services
Computational Services
Grid computational services
Data analysis/processing
Statistical analysis
Quantitative analysis
Image segmentation
Annotation
Rating/Annotation
Peer review
Rating/assessment
Textual
Spoken
Hyperlinking
Semantic annotation
Registry Services
Create registry
Add to/deposit in registry
Remove from registry
Edit registry entry
Search registries
Assessment, Marking, Grading
Service registry
Metadata schema registry
Ontology registry
Publication Services
Finding optimal conferences/journals
Data publication
Formatting services
Version control
Bibliography Services
Manage citations (EndNote)
Preservation
Data curation
Archival
Obsolescence detection and notification
Migration
Emulation
Normalisation
Documentation
Help services
FAQs
Resource list
Archival
Best practice guidelines
Help generation
Project Management
Locating collaborators/expertise
Locating funding
Proposal writing
Project/time tracking
Report generation
Spreadsheets
Budgeting
Personal Organisation Services
Calendar
eNotebook
Calculator
Spellcheck
Help
Language translation
Currency translation
Bookmarks
Personal Development
ePortfolio
Calendaring
Resource List
Personal Development
ePortfolio
Research Portfolio
Homepage management
Course Management
Course validation
Activity Management
Activity author
Curriculum Development
Assessment
Competency
Course validation
Grading
Marking
Quality assurance
Financial/Account Management
Pricing
Usage logging
Auditing
Charging
Billing/invoicing
6. e-Learning Services
[Table of Contents]
The E-Learning Framework (ELF) is an initiative by the U.K's Joint Information Services Committee (JISC) and Australia's Department
of Education, Science and Training (DEST) to build a common approach to Service Oriented Architectures for e-learning.
6.1 e-Learning Services: Common Services
[Table of Contents]
AV Conferencing
Authorization
Context
Filing
Harvesting
Member
Alert
Calendaring
DRM
Format Conversion
Identifier
Messaging
Archiving
Chat
E-mail management
Forum
Logging
Metadata management
Packaging
Resolver
Search
Whiteboard
Person
Role
Service Registry
Workflow
Presence
Rules
Terminology
6.2 e-Learning Services: Learning Domain Services
Authentication
Content Management
Federated Search
Group
Mapping
Metadata Schema
Registry
Rating/Annotation
Scheduling
User Preferences
[Table of
Contents]
Activity Author
Course management
Learning Flow
Reporting
ePortfolio
Activity Management
Course Validation
Marking
Resource List
Assessment
Curriculum
Personal development
Sequencing
Competency
Grading
Quality Assurance
Tracking
[Table of
Contents]
7. Matrix Relating Services to Domains
The matrix below lists the key clusters of services in column 1. Their relevance to the Learning, Research, Library, IT services and
Administration sectors is indicated in each column. Services that are common across the majority of sectors are indicated using the
Common column.
Identifier
Management
Group/VO
Management
User Management
Job Management
Network
Management
Resource
Management
Software/Systems
Management
Learning/ Research/ Library IT
Admin Common
Education Grid
Services
X
X
X
X
X
X
X
X
X
X
X
Service Management
Data Management
Information
Management
Digital Rights
Management
Metadata services
Ontology Services
Workflow Services
Provenance/Audit
trail Services
Search/Discovery
Services
Digital Repository
Services (Fedora,
DSpace, Greenstone,
ePrints)
Information
Integration Services
Presentation Services
Notification/Delivery
Services
Security Services
Collaboration
Services
Remote Instrument
Services
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Visualization
Services
Simulation/Modelling
Services
Virtual/Immersive
X
X
X
Environments
Computational
services
Annotation Services
Registry Services
Publication Services
Bibliography
Services
Preservation Services
Project Management
Personal
Organisational
Services
Personal
Development
Documentation
Services
Course Management
Activity Management
Curriculum
Development
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Services
Assessment Services
Financial/Accounting
Services
X
X
8. Recommendations
[Table of Contents]
The next steps should be to:



Seek, discuss, assess and incorporate feedback to the current document;
Develop a consensus within JISC and DEST on: the list of services, their definitions, examples, relevant technologies and
the organizational structure - that should be included in the e-Framework - based on the draft proposal presented in this document
Generate a WSMO representation of the services specified in the e-Framework
9. References

"The e-Framework for Education and Research: an Overview", Bill Olivier, Tish Roberts, Kerry Blinco, July 2005
http://www.e-framework.org/resources/eframeworkrV1.pdf

"Service Classes for the e-FER", Rob Allan CCLRC e-Science Centre (for JCSR)
http://www.grids.ac.uk/Papers/Classes/classes.html

The e-Learning Framework - Common Services
http://www.elframework.org/common_services
[Table of
Contents]

The e-Learning Framework - Learning Domain Services
http://www.elframework.org/learning_domain_services

DEST, JISC-CETIS and Industry Canada "Service-oriented Frameworks: Modelling the Infrastructure for the next generation of
eLearning Systems"
http://www.jisc.ac.uk/uploaded_documents/AltilabServiceOrientedFrameworks.pdf
Download