2009-03/Leap2A specification

An output of the Portfolio interoperability projects (PIOP), supported by CETIS and funded by JISC

'NOTE This is an old version of Leap2A. The newly agreed version is from July 2010, and can be found through http://www.leapspecs.org/2A/ '

=The Leap2A specification for portability and interoperability of e-portfolio information=

About this specification
This specification is intended to cover the representation of several kinds of information, centred around individuals, who collect, create, reflect on and use their own information for learning, development, self-presentation, or related purposes.

While much of this plays a part in the individuals' learning and development, rather than being materials authored by others, the information is typically authored, or collected, by the individuals themselves, and may cover: what they have done, made, achieved, written, or are proud of; what or who helps or has helped them; what they aspire to; what they are good at; evidence for and reflections on any of these; and perhaps input from other people.

It is not the purpose of this specification to cover information gathered by others about an individual, over which that individual has no easy access or control.

Version
This is the 2009-03 version of the Leap2A specification. Other work is linked through the Leap2A specification page.

The contributors to this version were principally the participants in the PIOP 2 projects. A separate page is being maintained for Leap2A contributors.

Examples
The Examples page holds elementary examples. More are on individual project pages.

Basic concepts of Leap2A and Atom

 * Basic information structures and their correspondence with Atom: an outline introduction to how Atom is used in Leap2A.
 * Atom and other elements used: a listing, with notes and links to further information.

Items
See Leap2A types

Information in Leap2A is grouped into items, each represented as an Atom entry. Each item has a Leap2A type or class, and the type affects which literal attributes, relationships or categories that may be associated with the item.

Around and beyond items
See Leap2A predicates

Leap2A items are joined with other items, and with literal values, as properties, predicates, or "metadata".
 * Literal metadata specify how to represent information tied directly to items, rather than being separate related items in their own right.
 * Personal data are often found in CVs etc. As they are not related to core portfolio processes, they are given separately.
 * Organizational data parallel personal data; similarly they are not related to core portfolio processes.
 * Structured content relates to content that refers to, or represents, other portfolio items.
 * Relationships exist between items or entries.

Categories
Leap2A categories apply to some types of item, but have no major effect on the syntax, or what relationships are expected.

There is a separate page for each of the category schemes defined, which can be found through the categories page itself.

Practicalities
The page on Leap2A and you gives guidance on mapping to, exporting and packaging in, and importing from Leap2A.

Not specific to this version

 * Leap2A practice scenarios
 * Leap2A interoperation scenarios
 * Leap2A spec changes
 * LEAP references