View source for Open service interface definition

{{no footnotes|date=July 2023}}
An '''open service interface definition''' ('''OSID''') is a programmatic interface specification describing a service. These interfaces are specified by the [[Open Knowledge Initiative]] (OKI) to implement a [[service-oriented architecture]] (SOA) to achieve [[interoperability]] among applications across a varied base of underlying and changing technologies.
== Rationale ==
To preserve the investment in software engineering, program logic is separated from underlying technologies through the use of software interfaces each of which defines a contract between a service consumer and a service provider. This separation is the basis of any valid SOA. While some methods define the service interface boundary at a protocol or server level, OSIDs place the boundary at the application level to effectively insulate the consumer from [[Protocol (computing)|protocols]], server identities, and utility libraries that are in the domain to a service provider resulting in software which is easier to develop, longer-lasting, and usable across a wider array of computing environments.
OSIDs assist in [[software design]] and development by breaking up the problem space across service interface boundaries. Because network communication issues are addressed within a service provider and ''below'' the interface, there isn't an assumption that every service provider implement a remote communications protocol (though many do). OSIDs are also used for communication and coordination among the various components of complex software which provide a means of organizing design and development activities for simplified [[project management]].
OSID providers (implementations) are often reused across a varied set of applications. Once software is made to understand the interface contract for a service, other compliant implementations may be used in its place. This achieves [[reusability]] at a high level (a service level) and also serves to easily scale software written for smaller more dedicated purposes.
An OSID provider implementation may be composed of an arbitrary number of other OSID providers. This layering technique is an obvious means of [[abstraction]]. When all the OSID providers implement the same service, this is called an ''adapter'' pattern. Adapter patterns are powerful techniques to federate, multiplex, or bridge different services contracting from the same interface without the modification to the application.
== List ==
* Agent
* Assessment
* Authentication
* Authorization
* CourseManagement
* Dictionary
* Filing
* Grading
* Hierarchy
* Logging
* Messaging
* Repository
* Scheduling
* Workflow
== References ==
* [http://simba.cs.uct.ac.za/~honsproj/cgi-bin/view/2003/baving_green.zip/baving_green/coursetool/downloads/paper.pdf Baving, T., Cook, D., Green, T.  ''Integrating the Educational Enterprise''. 2003.]
* [http://www.okiproject.org/documents/OKIandIMS-WiresAndSocketsRevisited.pdf Kraan, W.  ''O.K.I. and IMS, wires and sockets revisited''.]
* [http://www.okiproject.org/library/doc_41.html Kahn, J.  ''Screen Shots: Repository OSID Interoperability''. 2005.]
* [http://www.okiproject.org/filemgmt/visit.php?lid=44 Kumar, V., Merriman, J., Thorne, S. ''Open Knowledge Initiative Final Report''. 2004.]
* [http://okiproject.org/filemgmt-data/files/RepositoryDevelopersGuide-v1.0.pdf Kahn, J.  ''Repository Developer's Guide''. 2006.]
* [http://www.okiproject.org/documents/OKIManagingComplexity_rel_1_0.pdf Kahn, J. ''Managing Complexity and Surviving Technology Change''. 2005.]
== External links ==
* {{Official website|http://osid.org}}
* [https://okapia.atlassian.net/wiki/spaces/OSID/overview OSID wiki]
* [https://web.archive.org/web/20081226161331/http://www.phpoki.org/ PHP OSIDs]
{{internet-stub}}
[[Category:Software architecture]]
[[Category:Service-oriented (business computing)]]