Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Summary

OsidManagers are the top level service endpoint interface into an OSID Provider. 

OsidManagers

The job of an OsidManager is to:

  1. articulate what OsidSessions are supported
  2. access OsidSessions
  3. articulate what (sub) OsidManagers are supported
  4. access OsidManagers
  5. articulate what Types are supported
  6. articulate what Locales are supported
  7. identify the OSID Provider
  8. provide the ability to access versions of an OSID Provider

For now, we'll just concern ourselves with session support and access.

OsidSession Access

Each OsidSession can be considered a service endpoint within an OSID that deals with some smaller set of functionality. Slicing a large functional domain into smaller parts eases the ability to implement an OSID Provider, and communicates clearly what is and is not supported by an OSID Provider. The OsidManager is essentially a mini-service bus.

OsidProfiles

The specification groups the identity and support methods into OsidProfiles which are extended to become OsidManagers. 

Example

This is an example subset of the Learning OSID where two of the OsidSessions manage retrieval and querying of learning objectives.

See Also

 

  • No labels