LEAP2A Portfolio Implementation
Rationale
In the current Portfolio API implementation (as at time of writing, May 2009), we're missing support for any of the available Portfolio standards. In the light of Mahara's new support for LEAP2A, as well as other Portfolio vendors, it makes sense for Moodle to be able to export LEAP2A in order to be really useful. This doesn't mean that Moodle will never support any other Portfolio standard, it just means that it's a logical first choice.
Background to LEAP2A
LEAP2A is a simple ATOM Based standard that is well positioned as a low-barrier standard to combat some of the heavier standards out there. The basic premis is that every item is an entry, with some additional LEAP specific metadata. Content is not just defined by metadata, but also largely gains meaning based on its relation to other items.
LEAP2A is being championed by JISC in the UK and adopted by a number of Portfolio vendors.
What needs to happen in Moodle
- Agreement on a generic way to write XML, and an implementation
- LEAP2A writing library
- ... more
See also
http://wiki.cetis.ac.uk/LEAP_2.0 http://moodle.org/mod/forum/discuss.php?d=119894 http://wiki.mahara.org/Developer_Area/Import%2f%2fExport
