Content management with repository open service interface definition
- OSID's - Open service interface definitions
- Usage and functions of OSID's
- Package org - OSD repository description class summary
Now days the term content management is the key issue with website's design, what to include what not to include is very crucial problem. Here, in this paper we have shown the way of managing content called assets, which may contain metadata, course materials, assessment items, images, videos etc. The repository open service definition is an oki specification which defines the storing and retrieving of digital content referred to as assets. Here we have shown architecture of repository open service interface definition as well as its usefulness in managing contents. The Repository Open Service Interface Definition (OSID) is an O.K.I. specification which defines the storing and retrieving of digital content, referred to as Assets. OSIDs are programmatic interfaces which comprise a Service Oriented Architecture for designing and building reusable and interoperable software. Key-words: Open Service Interface Definition(OSID), Open Knowledge Initiative(OKI), Service Oriented Architecture(SOA).
[...] Some useful methods of this interface are copyAssets(), getAssets() etc. 7.2 org.osid.repository.Asset An Asset's definition includes several methods for managing Records in addition to the common ones for display name, description, and id. The management methods are a little more complex than the ones found in the Repository. To start, we have the getDisplayName(), updateDisplayName(), getDescription(), updateDescription(), and getId(). These methods are similar to those found in many OSIDs . A PartStructure has the common methods, getDisplayName(), getDescription(), and getId(). [...]
[...] The Authentication OSID permits an application to abstract the authentication process without having to manage the details of the underlying authentication service AUTHORIZATION The Authorization OSID allows an application to establish and query a user's privileges to view, create, or modify application data, or use application functionality COURSE MANAGEMENT The CourseManagement Open Service Interface Definition (OSID) primarily supports creating and managing a CourseCatalog. The catalog is organized into: CanonicalCourses, which are general and exist across terms; CourseOfferings for CanonicalCourses, which occur in a specific term, have a CourseGradeType1, a Status, etc; and CourseSections for CourseOfferings, which have a meeting location, schedule, student roster, etc. [...]
[...] 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 protocols, server identities, and utility libraries that are in the domain to a service provider resulting in software which is easier to 4.SUMMARY OF THE OSIDS The following briefly describes the OSIDs (Open Service Interface Definitions). 4.1 OSID ROOT The Root package, with a mechanism for loading OSID managers 4.2 AGENT OSID use Agents to represent individuals or processes that invoke specific Services. [...]