3.4. Building Content Packages

< Previous | Contents | Next >

‌3.4. Building Content Packages‌

This section presents the requirements for building SCORM Content Packages. The section describes the XML binding for the IMS Content Packaging Specification as applied to SCORM. There are some specific rules that have guided the creation of this XML binding:

 The XML binding will adhere to the XML 1.0 specification [6] of the W3C.

 The XML binding must maintain the definitional structure of the IMS Content Packaging Information Model.

Some of the requirements are also drawn from other various specifications and standards. The majority of the requirements are inherited by the requirements defined in IMS Content Packaging Specification. Some other specifications and standards are implicitly inherited based on the nature of the XML and other Internet technologies.

This section also defines the requirements for each of the SCORM Content Package Application Profiles:

 Resource Content Package Application Profile: A content package that only contains resources (i.e., no organization). This type of content package can be used for bundling a set of learning resources with no defined organization or content structure. These learning resources may or may not have relationships between each other.

 Content Aggregation Content Package Application Profile: A content package for bundling a set of learning resources and their intended static structure and sequencing requirements (i.e., the manifest contains 1 or more organizations of the learning resources).

Refer to Section 3.5: The SCORM Content Package Application Profiles for more information on SCORM Content Package Application Profiles.

3.4.1. Manifest File 3.4.1.1. <manifest> Element XML Namespace Prefix: imscp Attributes:Elements:Example:3.4.1.2. <metadata> Element XML Namespace Prefix: imscp Attributes:Elements:Example:3.4.1.3. <schema> Element XML Namespace Prefix: imscp 3.4.1.4. <schemaversion> Element XML Namespace Prefix: imscp Example:3.4.1.5. {Metadata}3.4.1.5.1. Metadata using XML extensions Example:3.4.1.5.2. <location> Element XML Namespace Prefix: adlcp Attributes:Elements:Example:3.4.1.6. <organizations> Element XML Namespace Prefix: imscp Attributes:Elements:Example:3.4.1.7. <organization> Element XML Namespace Prefix: imscp Attributes:Elements:Example:3.4.1.8. <title> Element XML Namespace Prefix: imscp Example:3.4.1.9. <item> Element XML Namespace Prefix: imscp Attributes:Elements:Example:3.4.1.10. <title> Element XML Namespace Prefix: imscp Example:3.4.1.11. <item> Element 3.4.1.12. <metadata> Element XML Namespace Prefix: imscp Attributes:Elements:Example:3.4.1.13. <timeLimitAction> Element XML Namespace Prefix: adlcp Example:3.4.1.14. <dataFromLMS> Element XML Namespace Prefix: adlcp Example:3.4.1.15. <completionThreshold> Element XML Namespace Prefix: adlcp Attributes:Elements:Example:3.4.1.16. <sequencing> Element 3.4.1.17. <presentation> Element 3.4.1.18. <data> Element XML Namespace Prefix: adlcp Attributes:Elements:Example:3.4.1.19. <map> Element XML Namespace Prefix: adlcp Attributes:Elements:3.4.1.20. <metadata> Element XML Namespace Prefix: imscp Attributes:Elements:3.4.1.21. <sequencing> Element 3.4.1.22. <resources> Element XML Namespace Prefix: imscp Attributes:Elements:Example:3.4.1.23. <resource> Element XML Namespace Prefix: imscp Attributes:Elements:Example:3.4.1.24. <metadata> Element XML Namespace Prefix: imscp Attributes:Elements:Example:3.4.1.25. <file> Element XML Namespace Prefix: imscp Attributes:Elements:Example:3.4.1.26. <metadata> Element XML Namespace Prefix: imscp Attributes:Elements:Example:3.4.1.27. <dependency> Element XML Namespace Prefix: imscp Attributes:Elements:Example:3.4.1.28. <manifest> Element 3.4.1.29. <sequencingCollection> Element 3.4.2. Content Package Manifest Extensions 3.4.3. Content Package Manifest Href Handling 3.4.3.1. Handling the XML Base Attribute 3.4.3.2. URL Encoding and Decoding 3.4.3.3. Handling Additional Parameters as Part of URLs

< Previous | Contents | Next >