1. Open Knowledge Initiative Architectural Overview 12/15/01

2. OKI Philosophy Infrastructure for Educational Application Development and Support Pedagogically Driven Open (low threshold for access/adoption) Collaborative Enabling Sharing of Diverse Application Development Efforts API Based/Implementation Independent

3. Deliverables 1.x Version of OKI Framework Spec. Implementations of Framework APIs Collection of Exemplar Tools/Applications (Including “LMS” Solution) Developer Community Strategy Sustainability Strategy

4. OKI Architecture API Based Framework Specification AuthNAuthZDBMSFileGUIDRulesEtc... Course MgmtContent MgmtAssessmentEtc... Component APIs Common Service APIs

5. OKI Architecture OKI Framework Specification Framework Implementations AuthNAuthZDBMSFileGUIDRulesEtc... Course MgmtContent MgmtAssessmentEtc... Component APIs Common Service APIs Infrastructure

6. OKI Architecture OKI Framework Specification Framework Implementations –Local –Modular. AuthNAuthZDBMSFileGUIDRulesEtc... Course MgmtContent MgmtAssessmentEtc... Component APIs Common Service APIs Infrastructure

7. OKI Architecture. AuthNAuthZDBMSFileGUIDRulesEtc... Course MgmtContent MgmtAssessmentEtc... Component APIs Common Service APIs Pedagogical Tools Application Suite Infrastructure

8. Client Objects Client Apps Client Objects Client Apps Client Objects Web Apps Browser Client Objects Web Apps Browser Client Objects Client Appss OKI ServicesOKI Clients Campus Infrastructure OKI Service Model

9. Multiple OKI Servers Serving Different Content, But Sharing Some Enterprise Services SIS Data Authentication/ Authorization Digital Repository SIS Data Digital Repository

10. Multiple OKI Servers Sharing Common Infrastructure Services SIS Data Authentication/ Authorization Digital Repository Messaging

11. OKI Processes Common Services OKI/LMS Services Pedagogical Tools User Experience Infrastructure EALP Architecture Sustainability Common Services LMS Services OKI Tools User Experience Infrastructure

12. EALP Educational Activities and Learning Practices –LMS Summit – April 2001 –Needs assessment/scenarios –Tool Definition Workshop – Oct 15, 16 –Current Directions User Experience Content Management

13. Architecture Group Primary team is at MIT –Approximately 3FTE –Provide bulk of day to day effort Core partner designers –Have met 4 times since May –Critical input and contribution –Backgrounds range from system design, instructional application design, library systems

14. Institutional Partners (Design) MIT Stanford University North Carolina State University University of Michigan University of Wisconsin University of Pennsylvania Dartmouth College

15. Stay Tuned http://web.mit.edu/oki