{"id":39920,"date":"2007-08-09T10:42:03","date_gmt":"2007-08-09T14:42:03","guid":{"rendered":"https:\/\/segue.middlebury.edu\/view\/html\/node\/39920"},"modified":"2012-08-06T17:57:56","modified_gmt":"2012-08-06T17:57:56","slug":"o-k-i-open-service-interface-definitions-as-a-native-framework-api","status":"publish","type":"page","link":"https:\/\/segueproject.org\/openiworld\/","title":{"rendered":"Overview"},"content":{"rendered":"

O.K.I. Open Service Interface Definitions as a Native Framework API<\/h3>\n
\n
Technology Showcase<\/a>
\n2007 Openi<\/span>World<\/span>:eLearn<\/span>
\n<\/span> New Orleans, LA
\n1:00-1:45 pm, August 9, 2007<\/span>Interoperability initiatives often follow the theme of enabling applications of disparate design and implementation to exchange data and functionality via a standards-compliant external application programming interface (API). The Harmoni application framework and the curricular applications evolving out of it turns this paradigm around and makes the Open Knowledge Initiative (O.K.I.) open service interface definitions<\/em> (OSIDs) the primary internal API of the system. This design allows an application’s data and functionality to be accessible through the OSIDs from its inception. Even more importantly, alternate OSID implementations from third parties may be swapped for those shipped in the framework enabling applications to make use of a wide range of infrastructures.<\/p>\n<\/div>\n

 <\/p>\n

Adam Franco
\nCurricular Technology DeveloperAlex Chapin<\/a>
\nPrincipal Curricular Technologist
\nMiddlebury College CodeLab<\/a><\/span><\/p>\n
<\/div>\n<\/div>\n<\/div>\n

OpeniWorld Handout<\/h3>\n
\n
\n
\"download\"
\nDownload<\/strong><\/a>
\n(74.03 kB)<\/span><\/div>\n

\n\"Download
\n<\/a><\/div>\n
<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

O.K.I. Open Service Interface Definitions as a Native Framework API Technology Showcase 2007 OpeniWorld:eLearn New Orleans, LA 1:00-1:45 pm, August 9, 2007Interoperability initiatives often follow the theme of enabling applications of disparate design and implementation to exchange data and functionality … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":29,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-39920","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/segueproject.org\/openiworld\/wp-json\/wp\/v2\/pages\/39920","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/segueproject.org\/openiworld\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/segueproject.org\/openiworld\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/segueproject.org\/openiworld\/wp-json\/wp\/v2\/users\/29"}],"replies":[{"embeddable":true,"href":"https:\/\/segueproject.org\/openiworld\/wp-json\/wp\/v2\/comments?post=39920"}],"version-history":[{"count":1,"href":"https:\/\/segueproject.org\/openiworld\/wp-json\/wp\/v2\/pages\/39920\/revisions"}],"predecessor-version":[{"id":200000040283,"href":"https:\/\/segueproject.org\/openiworld\/wp-json\/wp\/v2\/pages\/39920\/revisions\/200000040283"}],"wp:attachment":[{"href":"https:\/\/segueproject.org\/openiworld\/wp-json\/wp\/v2\/media?parent=39920"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}