1 / 24

Portfolio SIG, Manchester, 21 June 2007 Portfolio Interoperability

Portfolio SIG, Manchester, 21 June 2007 Portfolio Interoperability. Scott Wilson CETIS. This work is licensed under a Attribution-NonCommercial-ShareAlike 2.0 licence. There is no right or wrong answer!. The Scenarios. Institutional system <-> institutional system (e.g FE -> HE)

morty
Download Presentation

Portfolio SIG, Manchester, 21 June 2007 Portfolio Interoperability

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Portfolio SIG, Manchester, 21 June 2007Portfolio Interoperability Scott Wilson CETIS This work is licensed under a Attribution-NonCommercial-ShareAlike 2.0 licence

  2. There is no right or wrong answer!

  3. The Scenarios • Institutional system <-> institutional system (e.g FE -> HE) • Institutional system <-> employer system • Institutional system <-> personal system • Institutional system <-> govt. agency system • Personal system <-> personal system • Personal system <-> employer system • Interaction with admissions process, recruitment process, assessment process, accreditation process • Etc.

  4. Many kinds of (data) interoperability • identities • profiles & preferences • permissions • content • structures & relationships • official competencies, credits etc

  5. The transfer scenario - layers

  6. Personal -> Institution Scenario

  7. And back the other way

  8. Identities • Provisioning • SPML • IMS Enterprise • DirXML/DSML • Distributed identity • OpenID • CardSpace • Shibboleth

  9. Profiles and preferences • FOAF • vCard • OpenID SRP • HR-XML (CV)

  10. Permissions • No easy way to do this today • XACML? • Proprietary permissions negotiation? • Inference via FOAF groups? • A new language?

  11. Content: The Big Five • (X)HTML • Atom/RSS • UBL • ODF • DocBook + also things like AAC, MP3, MPEG, QT, WMV, SVG, PDF, LaTEX, MS Word, TEI (the list goes on…)

  12. Structure • Atom/RSS/etc for simple structures • RDF+OWL for complex structuring • isPartOf • isVersionOf • Inheritance • Specialised (e.g. Leap2.0 relations) • XML Topic Maps • Regular links • IMS Content Packaging/RAMLET/MPEG-21

  13. Official competencies and credits • HR-XML • MIAP Learner Achievement Record

  14. Roll Your Own XML Spec • “neither easy nor fun” • “pass/fail ratio” • “software pain” • “restating Metcalfe” • “opportunity cost”

  15. Interoperability: scope

  16. Open APIs • Flickr API • YouTube API • Facebook API

  17. Public ‘middleware’ services as sharing intermediaries • Portfolio -> Slideshare/Flickr/Facebook/EduSpaces -> employer

  18. What’s supported today? • Elgg: Atom, RSS, FOAF, various content formats • Moodle: Atom, RSS, various content formats • Employer HR systems: MS Word, HR-XML(?) • PebblePad: IMS CP, HR-XML Europass, Shibboleth, RSS, UKLEAP, IMS EP

  19. Never, ever, ever implement IMS EP Look, just don’t.

  20. Security • User choice is important - user control of access

  21. Adopters dilemma • Its not much fun being the only one who supports a standard

  22. scott.bradley.wilson@gmail.com • http://www.cetis.ac.uk/members/scott

More Related