|Content Asset||Raw media: images, text snippets, audio clips, applets, etc.||Indecomposable†||Content assets are reused as is, possibly with modifications in presentation and style.||The key issue for content assets is separating presentation from content. Contextual dependence should be avoided.||Basic metadata and information about rights will allow assets to be cataloged and reused. Technical information may also be important. In practice, content assets are often labeled only with a title and identifier.||Text and pure HTML are standardized formats for content assets, although HTML produced by most authoring tools is not standards conformant. XHTML is an improvement.
Interoperability is improved by associating appropriate metadata to a content asset.
|Content assets are usually edited and displayed using common authoring suites, plug-ins and browsers. For widest use, it is best when no plug-in is needed, or when a plug-in is freely available, automatically downloaded and widely in use, e.g. Flash™ or Acrobat Reader™. Products, Plug-ins and formats can be community-specific, as in those needed to produce and display MathML.|
|Information Object||A text passage, Web page(s), applet, etc. that focuses on a single piece of information. It might explain a concept, illustrate a principle or describe a process. (Single) exercises are often considered information objects.||Decomposable into content assets.||Information objects are normally reused as self-contained units. In authoring situations, sometimes, content assets are extracted and reused as well.||For information objects, separation of content from presentation is important, and it is also important to avoid cross references that entangle the content with the structure, pedagogy and context.||Basic metadata is important for information objects, but it may also be important to say something about the educational level and style of an information object. It may also be important to facilitate proper attribution by including the identification of the author(s) within metadata.||Information objects are similar to content assets. For applets, Java™ is considered a standardized format by some, although it has many platform and versioning issues. There are specification and standards that specifically address test questions.||Information objects are similar to content assets in that they generally require a single application to edit and a single plug-in or application to display. The products involved are usually not specific to learning, although it is possible to use learning-specific authoring tools to produce information objects. Look for products whose output can be edited by more commonly available tools.|
|Learning Component||A learning component is a generic term for things like lessons and courses that typically have multiple learning objectives and are composed of multiple learning objects.||Decomposable into learning objects||Learning components can be reused in their entirety, but it is suspected that most reuse of learning components uses only parts of them, usually learning objects.||As the aggregation level increases, reuse shifts to component reuse. Therefore issues of separating pedagogy, structure and content become more crucial for reuse. Pedagogical approach and contextual dependence become the limiting factors for reusing or repurposing learning components in their entirety.||Many learning resource catalogs list courses and modules and only provide basic metadata. More detailed contextual information is helpful, as is information that guides the user. It should be noted that most metadata associated with a learning component applies to the component as a whole and not to learning objects, information objects or content assets contained within it.||Learning components are similar to learning objects.||Learning components are similar to learning objects although they may rely more on course management technology. If a learning component (e.g. a course) can only run on a particular course management system, it is not very interoperable.|
|Learning Environment||“Learning Environment” is a catch-all phase for the combination of content and technology with which a learner interacts. Thus a course written in a course management system is a learning component, but a deployment of the course in a course management system at a particular institution (with a particular enrollment policy, help center, library reserve system etc.) used by learners is a learning environment.||Decomposable into content, technology and processes that support learning||The components of learning environments can be reused, but learning environments are not reusable objects in the sense being discussed here.||Learning environments may be designed for a specific context and pedagogical approach or may be more general. The more general ones are those that are reusable. For them, it is important to avoid cross-linking of components of the environment.||Information about a learning environment is rarely encoded using a standardized metadata record. Nonetheless, it is important to provide a description, information about intended users, rights and technical information, and proper documentation.||The standards relevant to learning environments are those relevant to IT infrastructure.||Learning environments must integrate with registrar systems, library information systems, content and knowledge management systems, etc.|
- Getting Started
- Reusability Framework
- Reusable Design Guidelines
- NSDL and Reusability