...
Summary
Introduction
The Open Service Interface Definitions (OSIDs) define a service-based architecture to promote software interoperability. The OSIDs are a set of interface specifications that describe how various software components interact using a variety of service interoperability patterns among its many service domains. It's a pile of paper.
The value of the OSIDs is only realized through working code.
This wiki contains documentation and examples on the use of OSIDs and the Okapia tools and runtime environment.
Download
Try An Example
The OSIDs (available from osid.org) are the service interface definitions. This wiki has information about the OSIDs and the Okapia open-source implementation.
| Table of Contents | ||
|---|---|---|
|
Try An Example
Clone a sample application and OSID Provider:
| Code Block |
|---|
% git clone https://bitbucket.org/okapia/9-planets-sample.git
% cd 9-planets-sample
% make run |
If you count nine planets, your OSID environment is working. Anything less would be a serious problem.
What It Does
OSID Consumer
net.okapia.osid.sample.Test illustrates the basics of consuming an OSID.
- Starting up the OSID Runtime environment.
- Loading a Resource OSID Provider
- Getting some stuff from it.
OSID Provider
The OSID Resource Provider is net.okapia.osid.sample.providers.resource.solarsystem. It demonstrates the basics of an OSID Provider using the Okapia OSID implementation framework.
- An OsidManager.
- Setting up the identity of the service provider.
- Implementing a simple OsidSession.
- Implementing an OsidRecord attached to an OsidObject.
Configuration
An example configuration for this OSID Resource Provider is net.okapia.osid.sample.providers.resource.solarsystem.ResourceManager.xml.