100 likes | 124 Views
Explore OKI's collaborative platform for higher education partners, featuring open architectural specifications and common service APIs for seamless implementation. Enhance educational components and service layers for better campus infrastructure. Ideal for MIT implementations and development community engagement.
E N D
OKI – Common Services ITAG Lunch Scott Thorne & Chuck Shubert March 13, 2002
What is OKI? • Infrastructure for Educational Software • Mellon Funded • Collaborative • Higher Education Partners • Standards Groups • Open Architectural Specification
Institutional Partners • Cambridge University • Dartmouth College • MIT • North Carolina State University • Stanford University • University of Michigan • University of Pennsylvania • University of Wisconsin
“LMS” Educational Software Educational Component APIs Course Mgmt Content Mgmt Assessment Etc… Etc… Etc… Educational Service Implementations Common Service APIs AuthN AuthZ DBMS File GUID Rules Logging User Messaging Etc… Common Service Implementations Common Objects Institutional Infrastructure OKI Service Layers
Why use API’s • Integration • Independence • Code Reuse • Development Discipline • Protocol vs API?
OKI Service Model CampusInfrastructure OKI Clients OKI Services Client Objects ClientApps Browser Client Objects WebApps Browser Client Objects ClientApps Browser Client Objects ClientApps Client Objects Browser WebApps
Applications Sharing Some Enterprise Services Digital Repository Authentication/ Authorization Digital Repository
Common Services • Authentication • Authorization • Logging • DBC • File • User Messaging • Local Identifier • Calendar & Scheduling • Workflow • Rules
API Design • Balancing Act • Generic & Flexible • Specific & Precise • Stable & Simple • Full Function
What Next • Evolving API’s • MIT Implementations • Development Community