1. Sakai Perspective on Integration and Interoperability Charles Severance June 22, 2006 www.dr-chuck.com This material is Copyright Creative Commons Attribution 2.5

2. Sakai Foundation Names Executive Director

3. Sakai Map Sakai Activity - June 2006

4. Sakai Partners in Production (24%)

5. Sakai Partners in Pilot (32%)

6. Partners that do not run Sakai (46%)

7. Members that don’t run Sakai… Currently run –WebCT, Blackboard, Angel or home-grown –In no hurry to change vendors Are often paying Sakai to make the market a better place What do they want in the short term? –Interoperability.

8. Background in Standards Open Software Foundation (OSF) (1989-90) UNIX International (1990) IEEE POSIX –IEEE P1003.0 / ISO BS ISO/IEC TR 14252 (1990-1997) - Guide to an Open System Environment Reference Model –Vice Chair POSIX (1992-1996) –IEEE Standards Advisory Board IEEE Computer Magazine - Column Editor 1994-1994 IEEE LTSC - (2001 - 2002) IMS –Technical Board coChair 2005-2006 –IMS Tool Interoperability WG - 2005 –IMS Common Cartridge WG - 2006

11. Sakai and Standards Sakai needs to use its position and resources to influence ever richer standards so as to insure an ecology of many different collaboration and learning systems which are highly interoperable. – JSR-168 Portlet / WSRP 1.0 – JSR-286 Portlet 2.0 / WSRP 2.0 – IMS Tool Interoperability – IMS Common Cartridge

12. Something to think about.. Standards are cool! –LMS systems will import Common Cartridges –LMS systems will use TI based tools Which LMS systems will export Common Cartridge and make their internal tools available via Tool Interoperability?

13. Data Interoperability Needs Going forward, Sakai needs to increasingly function as a component of a larger enterprise architecture along with many other applications. Each enterprise will evolve their mix of applications independently over time.

14. Sakai Data Interoperability Roadmap... interoperability and data portability are key elements... EnterpriseDirectory StudentInformation AuthoringEnvironment PersonalLearningEnvironment PortalEnvironment CollaboarationEnvironment ContentManagement LMS Systems DataRepository

15. HTML REST WebDav SOAP iCal SPARQL RSS CalDav WebDav SOAP Current Sakai Future Sakai Sakai Interoperability: “Swiss Army Knife”

16. Sakai Integration Efforts Repositories – Read/Search - DR OSID / Sakaibrary – Writable repositories / DR OSID / JSR 170 – Export / long-term archival - Fedora / DSpace Learning Design - LAMS / CopperCore Collaborative Learning Environments (IMS TI) – Moodle / ATutor – Blackboard / WebCT / Angel Portals - JSR-168 portals / PHP based portals Desktop - PLEX / VUE / Apple RDF - Haystack / Piggybank / Welkin

17. Crazy Idea: Interoperability at the User Interface Service Oriented User Interface (SOUI) iTunesU is the model to follow until we find something better This collaboration, portfolio, learning, achievement, talent, etc - is about *ME* But not just about “ME” - I am a different me in different “context” So my “essence” is a combination of “who I am and “where I am pluged in”

18. Interoperability at the UI RSS, ATOM, RDF, SOAP, REST, HTML The SOAUI

19. Conclusion A critical element of Sakai’s value proposition to its members is standards and interoperability Demo / engineering oriented groups bring a “bit of IETF” to IMS Shorten the cycle time from specification to interoperability to production in multiple systems June 29 Cambridge, UK - http://www.heacademy.ac.uk/