1 / 11

IMS Content Packaging

IMS Content Packaging. Overview Dec 5, 2005. IMS Content Packaging scope. Source: IMS Info Model document Fig. 2.1. Manifest elements. Source: IMS Info Model document Fig 4.1. Currently. The only defined organization type is acyclic graph (tree) But other types are possible

reagan-luna
Download Presentation

IMS Content Packaging

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IMS Content Packaging Overview Dec 5, 2005

  2. IMS Content Packaging scope • Source: IMS Info Model document Fig. 2.1

  3. Manifest elements • Source: IMS Info Model document Fig 4.1

  4. Currently • The only defined organization type is acyclic graph (tree) • But other types are possible • The only defined resource type is “web content” • But other types are possible • The only defined binding is XML • Extensibility placeholders in all elements

  5. <manifest> <organizations> <organization> <item> <item identifierref=“resource1”/> <item identifierref=”SubManifest1“ > </item> <item identifierref=”resource1"/> </organization> </organizations> <resources> <resource identifier=”resource1"> … </resource> </resources> <manifest identifier=”SubManifest1"> <organizations> <organization> <item> <item identifierref=”resource2"/> <item identifierref=”resource3"/> </item> </organization> </organizations> <resources> <resource identifier=”resource2"> … </resource> <resource identifier=”resource3"> … </resource> </resources> </manifest> </manifest> Dereferencing & Mapping An organization element is a structured map of resources. The resources element an unstructured collection of resource descriptors. An item in an organization may reference either a resource descriptor, or a sub-manifest. In the IMS Simple Sequencing and SCORM profiles of IMS CP, only leaf items may reference a resource or sub-manifest. Source: IEEE LTSC WG 11 (Schawn Thropp, Claude Ostyn)

  6. Resource • Actually a “digital descriptor for a resource” • In current version, resource is always “web content” • Has an identifier (scope = manifest) • May have its own metadata • Resource element contains an inventory of files and/or “dependency” references to other resources • “Launchable” resources have an attribute whose value is a URL • URL is typically relative to package “root” • URL may be fully qualified == external resource • URL may have parameters • “Not launchable” resources are typically used for shared assets

  7. … <resources> <resource identifier="SCO1" type="webcontent“ adlcp:scormtype="sco" href="simplest_sco.html"> <metadata> … </metadata>   <file href="simplest_sco.html"> <metadata> … </metadata> </file>   </resource> <resource identifier="SCO2" type="webcontent“ adlcp:scormtype="sco“ href="simplest_sco_reusing_script.html">   <file href="simplest_sco_reusing_script.html" />   <file href="SCORMGeneric.js" />   </resource> </resources>

  8. Erratum • Source: IMS Info Model document Fig 4.1 The summary diagram in the IMS CP Information Model document is incomplete. An item may in fact also have meta-data

  9. Profiles of IMS CP: Simple Sequencing & SCORM Source: IEEE LTSC WG 11 (Claude Ostyn) Simple Sequencing adds rules to Organization and items. Each item represents an activity. SCORM 1.2 adds some presentation data options and specifies mandatory elements when metadata is present. SCORM 2004 builds on SCORM 1.2 and adds Simple Sequencing”

  10. Abstract view Source: IEEE LTSC WG 11 (Schawn Thropp)

More Related