Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Portfolio interoperability progress in the UK

612 vues

Publié le

Publié dans : Technologie, Formation
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

Portfolio interoperability progress in the UK

  1. 1. Portfolio interoperability progress in the UK <ul><ul><li>Shane Sutherland, Pebble Learning </li></ul></ul><ul><ul><li>Simon Grant </li></ul></ul><ul><ul><li>JISC CETIS & independent </li></ul></ul><ul><ul><li>ePortfolio & Digital Identity </li></ul></ul><ul><ul><li>Maastricht 2008-10-23 </li></ul></ul>
  2. 2. Progress on two fronts <ul><li>A portfolio interoperability prototyping project focused around portfolio systems used in practice, and geared towards the needs of the developers of those systems </li></ul><ul><li>Coming out of this project, a developing specification for transfer of portfolio information between systems based on the Atom Syndication Format and more broadly, Semantic Web concepts </li></ul>
  3. 3. What's carried on? <ul><li>Many ideas established in IMS LIP or even earlier </li></ul><ul><ul><li>others from UKLeaP and IMS ePortfolio </li></ul></ul><ul><li>The aim to support information transfer </li></ul><ul><ul><li>between systems when transferring </li></ul></ul><ul><ul><li>(but also intended to support transfer of small pieces) </li></ul></ul><ul><li>The subject of the Information, which supports </li></ul><ul><ul><li>CV building </li></ul></ul><ul><ul><li>other presentations </li></ul></ul><ul><ul><li>PDP, CPD </li></ul></ul><ul><ul><li>several employer interests </li></ul></ul><ul><ul><li>but not admin processes, unless in interests of the learner </li></ul></ul>
  4. 4. What's new for interoperability? <ul><li>Emphasis on developer-friendliness from the start </li></ul><ul><li>Based on Semantic Web & Dublin Core </li></ul><ul><ul><li>to give the simplest possible structures </li></ul></ul><ul><ul><li>to reuse established practice </li></ul></ul><ul><ul><li>to link to many current and future developments </li></ul></ul><ul><ul><li>but not imposed on developers </li></ul></ul><ul><li>Uses familiar formats </li></ul><ul><ul><li>LEAP2A based on Atom (as other specs have done) </li></ul></ul><ul><ul><li>but LEAP not necessarily fixed to any one XML schema </li></ul></ul><ul><li>Readily merges with other information </li></ul>
  5. 5. The LEAP 2.0 vision <ul><li>From CETIS Portfolio SIG meeting, December 2006 </li></ul><ul><li>The demand was for something </li></ul><ul><ul><li>relatively simple in concept </li></ul></ul><ul><ul><li>easy to implement </li></ul></ul><ul><ul><li>modular and extensible </li></ul></ul><ul><li>Name reflects UK LeaP and Web 2.0 </li></ul><ul><li>It now &quot;... aims to provide a sound basis for practical interoperability between portfolio tools, and other tools dealing with the same kinds of information.&quot; </li></ul><ul><li>http://wiki.cetis.ac.uk/LEAP_2.0 </li></ul>
  6. 6. A LEAP in simplicity <ul><li>LEAP 2.0 uses a representation of portfolio information that is actually very simple </li></ul><ul><li>Semantic Web RDF blobs and arrows (“triples”) </li></ul><ul><li>A very few examples: </li></ul><ul><ul><li>achievement – has evidence – resource (dissertation) </li></ul></ul><ul><ul><li>activity (course) – supports – achievement (good grade) </li></ul></ul><ul><ul><li>achievement – is evidence of – assertion (my statement) </li></ul></ul><ul><ul><li>assertion – claims – ability (learning outcome of course) </li></ul></ul><ul><ul><li>meeting – attended by – person </li></ul></ul><ul><li>Does not build them into fixed complex structures </li></ul><ul><ul><li>because the patterns are changeable </li></ul></ul>
  7. 7. A small corner of blobs and arrows course (activity) outcome (ability) achievement (good grade) assertion is evidence of has outcome supports claims personally defined resource (essay) has evidence
  8. 8. PIOP – from December 2007 <ul><li>“Portfolio InterOperability Prototyping” </li></ul><ul><li>Wanted something that was definitely developer-friendly </li></ul><ul><ul><li>uptake means everything for a standard </li></ul></ul><ul><ul><li>developers are vital for implementation </li></ul></ul><ul><ul><li>involve developers centrally from the outset </li></ul></ul><ul><li>http://wiki.cetis.ac.uk/Portfolio_interoperability_prototyping </li></ul><ul><li>Chose to work with the Atom Syndication Format </li></ul><ul><ul><li>an XML format a bit like RSS </li></ul></ul><ul><ul><li>how you would expect to represent a blog feed </li></ul></ul><ul><ul><li>in Atom, everything is an entry </li></ul></ul><ul><ul><li>idea had and shared by several other people </li></ul></ul><ul><li>Agreed LEAP2A – LEAP 2 using Atom </li></ul>
  9. 9. <ul><li>These are the Blobs </li></ul><ul><li>Based on established usage within partner portfolio systems </li></ul><ul><li>More have been sketched out in LEAP 2.0 for future consideration </li></ul><ul><li>Entry is used as itself for any general pieces of writing </li></ul><ul><li>Graceful degradation </li></ul><ul><li>“ plan” includes goal </li></ul>LEAP2A types of information <ul><li>entry </li></ul><ul><ul><li>ability </li></ul></ul><ul><ul><li>achievement </li></ul></ul><ul><ul><li>activity </li></ul></ul><ul><ul><ul><li>meeting </li></ul></ul></ul><ul><ul><li>person </li></ul></ul><ul><ul><li>resource </li></ul></ul><ul><ul><li>selection </li></ul></ul><ul><ul><ul><li>plan </li></ul></ul></ul>
  10. 10. LEAP2A relationships & inverses <ul><li>relation </li></ul><ul><ul><li>reflects on </li></ul></ul><ul><ul><li>has part </li></ul></ul><ul><ul><li>has ordered part </li></ul></ul><ul><ul><li>supports </li></ul></ul><ul><ul><li>has evidence </li></ul></ul><ul><ul><li>has agenda </li></ul></ul><ul><ul><li>has outcome </li></ul></ul><ul><ul><li>attended by </li></ul></ul><ul><ul><li>has reply </li></ul></ul><ul><ul><li>author (no inverse) </li></ul></ul><ul><li>(inverse ones) </li></ul><ul><ul><li>reflected on by </li></ul></ul><ul><ul><li>is part of </li></ul></ul><ul><ul><li>is ordered part of </li></ul></ul><ul><ul><li>supported by </li></ul></ul><ul><ul><li>is evidence of </li></ul></ul><ul><ul><li>is agenda of </li></ul></ul><ul><ul><li>is outcome of </li></ul></ul><ul><ul><li>attends </li></ul></ul><ul><ul><li>in reply to </li></ul></ul><ul><li>more in LEAP 2.0 for future consideration </li></ul>
  11. 11. Information about entries <ul><li>Entries have authors </li></ul><ul><ul><li>Atom allows plain text name, e-mail, URI </li></ul></ul><ul><ul><li>in LEAP2A, URI can relate to separate person entry </li></ul></ul><ul><ul><li>but we haven't yet decided how to cover personal details </li></ul></ul><ul><li>Records created, modified at certain times </li></ul><ul><li>Achievements each have one date of achievement </li></ul><ul><li>Plans each have one target date of completion </li></ul><ul><li>Activities, meetings have start and end dates </li></ul><ul><li>Things happen in locations </li></ul><ul><li>These things are recorded “literally” </li></ul><ul><ul><li>rather than by a relationship to another item “blob” </li></ul></ul>
  12. 12. Abilities are of great interest <ul><li>(skill, competence, learning outcome, etc.) </li></ul><ul><ul><li>People aim to acquire them through learning </li></ul></ul><ul><ul><li>They are assessed </li></ul></ul><ul><ul><li>People claim to have them </li></ul></ul><ul><ul><li>Qualifications relate to them </li></ul></ul><ul><li>An ability itself is an impersonal definition </li></ul><ul><ul><li>can be subject of goals </li></ul></ul><ul><ul><li>can be subject of claims or assertions </li></ul></ul><ul><ul><li>can be built up into skills frameworks </li></ul></ul><ul><li>Ability can be represented in LEAP </li></ul><ul><ul><li>ideally as an external definition, with just a link to it </li></ul></ul><ul><ul><li>also possible to define within the portfolio information itself </li></ul></ul>
  13. 13. PIOP project achievements <ul><li>3 initial partners </li></ul><ul><ul><li>Newcastle University </li></ul></ul><ul><ul><li>Pebble Learning (ex Wolverhampton) </li></ul></ul><ul><ul><li>University of Nottingham </li></ul></ul><ul><li>First version of LEAP2A </li></ul><ul><ul><li>see http://wiki.cetis.ac.uk/LEAP2A_specification </li></ul></ul><ul><li>JISC funded project now being extended to others </li></ul><ul><ul><li>test and extend the specification </li></ul></ul><ul><ul><li>carefully add in whatever else is necessary for them </li></ul></ul><ul><ul><li>maintaining agreement of all who have been involved </li></ul></ul><ul><li>New collaborators include Mahara and Synergetics </li></ul><ul><ul><li>this round to be completed by end of March 2009 </li></ul></ul>
  14. 14. PIOP and LEAP future <ul><li>Specification to be tested and working by March 2009 </li></ul><ul><li>All portfolio and related systems are welcome to collaborate to ensure coverage of their information </li></ul><ul><li>Develop transform from LEAP2A to LEAP RDF </li></ul><ul><ul><li>RDF and RDFa will be the higher level of interoperability </li></ul></ul><ul><li>Invite other specifications to develop transforms </li></ul><ul><ul><li>these to become alternatives to LEAP2A </li></ul></ul><ul><ul><li>all still included in the LEAP 2.0 vision </li></ul></ul><ul><li>Find way of working with IMS eP and HR-XML </li></ul><ul><ul><li>new, not current versions </li></ul></ul><ul><li>Increasingly international </li></ul>
  15. 15. Credits <ul><li>Shane Sutherland co-authored the paper, and was instrumental in getting the PIOP work started </li></ul><ul><li>LEAP2A is (and will be) the product of collaboration and agreement between the PIOP working partners </li></ul><ul><li>Colleagues in JISC CETIS and its Portfolio SIG and LIPSIG community have originated or developed ideas </li></ul><ul><li>The BSI UKLeaP work developed many ideas – the “LeaP” name was from Mike Collett of Schemeta </li></ul><ul><li>Many ideas were originated or brought together by the IMS LIP and ePortfolio teams </li></ul>
  16. 16. Summary <ul><li>LEAP 2.0 is a simple, powerful interoperability framework for learner-controlled portfolio information, based on Semantic Web concepts </li></ul><ul><li>PIOP project ensures developer interests covered </li></ul><ul><li>LEAP2A is the first implementation, based on Atom </li></ul><ul><li>Thanks for your attention </li></ul><ul><li>If there is time, questions and discussion? </li></ul>