LEAP 2.0 and a way forward

1
LEAP 2.0 and a way forward

• Simon Grant
• JISC CETIS Portfolio SIG
• London, 2007-10-22

2
Maastricht

• Importance of employers
• Employability portfolios
• HR-XML
• Link to IMS ePortfolio
• Can we relate the two based on models
• ontology?

3
What is a portfolio?
items and relationships
4
Portfolio basics

• Needed for
• whole transfer (secure feelings)
• parts for presentation, query, matching
• Information is web, not hierarchy
• What kinds of things make up the web?
• Class or type hierarchy can be useful

5
LEAP 2.0 starting points

• Portfolio items
• anything that can be related
• Relationships
• relating any items
• Relationships are light
• content-free
• no need for separate identifiers

6
Types of LEAP item

• Entry
• things standing for themselves, primarily
  represented in the portfolio
• Proxy
• standing for things with an independent
  existence can be simply title reference
• Tag

7
LEAP item
entry
tag
proxy
activity
personality
organization
achievement
interest
person
goal
reflexion
thing
value
planned meeting
assertion
competency
file
achieved qualification
claim
things that are below in this hierarchy inherit
all the required attributes / predicates defined
for above classes
8
Implementation

• Any binding allowed which can be mapped to a
  canonical form
• Canonical RDF / Semantic Web
• XML needs GRDDL transforms
• RDF and RDFa map directly
• What do microformats need?

9
Still to do

• Further clarify and agree item type definitions,
  attributes, predicates
• ontology can add more class relations
• Place HR-XML entities
• Relate to UN/CEFACT CCTS
• Agree structure for item hierarchy
• Do relationship hierarchy similarly
• Construct worked examples