introduction to scorm part iictchen/pdf/scorm-partii.pdf · scorm scope scorm book 2: the scorm...
TRANSCRIPT
References
www.scorm.tamucc.eduThe SCORM Run-Time Environment (V1.2), Advanced Distributed Learning (ADL) Initiative, October 2001SCORM Version 1.2 Sample Run-Time Environment Version 1.2.1, Advanced Distributed Learning (ADL) Initiativewww.adlnet.org
Outline
Example imsmanifest.xml that contains single SCOMicrosoft LRN Editor
Part I ReviewSCORM Meta-dataConclusionQ&A
Example- Microsoft LRN Editor
SCORM scope
SCORM
BOOK 2: The SCORMContent Aggregation Model
BOOK 3: The SCORM Run Time Environment
Launch, Communication API (from AICC)
Data Model (from AICC)
BOOK 1: The SCORMOverview
Meta-data Dictionary (from IEEE)
(Meta-data XML Binding and Best Practice (from IMS)
Content Structure (derived from AICC)
Content Packaging (from IMS)
SCORM Content Packaging
Content Packaging Conceptual Diagram
(.zip, jar, etc…)
(imsmanifest.xml)
Imsmanifest.xml Structure
Content Packaging Exampleimsmanifest.xml
1
2
3
4
The <organizations> Section -Hierarchical
TOC1
TOC2
TOC2a
TOC2b
Course navigation
menu
LMS Differences - Alternate Sequencing
The <resources> Section -Dependency Files
SCO & Assert Meta-data
SCORM Run-time Environment
Run-time Environment Overview
Learning Management System (LMS)
Server Side
Client Side
Data ModelActual data sent
back and forth
between SCO and LMS
API (Communications
Link between SCO
and LMS)
Launch
JavaScriptJavaScript
Browser
SCO
API Adapter
API Adapter
LMSServerLMS
Server
Asset
1
2
3
SCO To LMS Communications API Adapter State Transition
SCORM Run-time Commands
Run-time Meta-data Categories
cmi.core (12 mandatory items and 3 optional items) cmi.objectives (8 optional items) cmi.student_preference (5 optional items) cmi.student_data (4 optional items) cmi.interactions (13 optional items) Misc. communications (2 mandatory items and 2 optional items).
SCORM Mandatory Run-Time Items (1/2)
SCORM Mandatory Run-Time Items (2/2)
Optional Meta-data Items
CMI.CORE Optional Elements
CMI.OBJECTIVES
CMI.STUDENT_PREFERENCE
CMI.STUDENT_DATA
CMI.INTERACTIONS (1/2)
CMI.INTERACTIONS (2/2)
Miscellaneous Communications
Golden rules for SCORM
Golden Rule for SCOs: One SCO can not link directly to another SCOOnly one SCO is active at any time
Golden Rule for Run-time Meta-data:One SCO can not directly access data from another SCO
SCORM Meta-data
SCORMMeta-data
CourseMeta-data
Run-timeMeta-data
LMSimsmanifest.xml
SCOMeta-data
AssetMeta-data
Context Independent
(10)
(5)
(8)
(10)
(11)
(3)
(5)
(3)
(6)
Content AggregationMeta-data
Context Specific
Meta-data Model Overview
SCORM has two major meta-data categories:Course Meta-data - described in the imsmanifest.xml fileRun-time Meta-data - data maintained and supported by the SCORM specifications and SCORM-compliant learning management systems
SCORM classifies course meta-data into three categories:
Content Aggregation Meta-data, Sharable Content Object Meta-dataAsset (Sharable Resource) Meta-data
Context Independent vs. Context Specific Meta-Data
The three categories of course meta-data can be further classified by their positions within the course manifest file, and according to whether they provide context specific or context independent descriptions.
Context specific meta-data
Context specific meta-data are data specific to a particular course packaged by a SCORM manifest file:
course title, description of the packaged course, author of the packaged course, which might be different from the author of individual SCOs, keywords to help in locating the course within a SCORM repository, copyright of the packaged course, intended audience for the course, catalog information, required or expected prerequisites for the course, etc.
Context independent meta-data
Context independent meta-data are data describing individual SCOs or Assets that are independent of any particular course that uses these objects:
SCO or Asset title, general description of the SCO or Asset, the original author of the SCO or asset, keywords associated with the SCO or asset, copyright of the SCO or asset, etc.
The IMS Learning Resource Meta-Data Model
SCORM Content Aggregation Meta-Data (1/2)
Content aggregation meta-data consist of:data that can be searched externally such as course title, description, date created and version, data about the overall content aggregation (course) describing the course purpose, intended audience, author, copyright, etc.
Content aggregation meta-data should be context specific data, and they can appear in both the <metadata> and <organizations> sections of the manifest file.
SCORM Content Aggregation Meta-Data (2/2)
SCORM SCO Meta-Data (1/3)
Sharable Content Object meta-data are data describing course SCOs, independent of the a particular context. Like Aggregation Meta-data, the purpose of SCO meta-data is to make it easy to find and reuse SCOs archived in SCORM repositories. However, whereas Aggregation Meta-data are used to locate and reuse entire courses, SCO meta-data are used to find and reuse the building blocks of courses.
SCORM SCO Meta-Data (2/3)SCO meta-data can be classified into three categories:
that can be searched externally such as the SCO title, description, date of creation and version, data describing a Sharable Content Object, and data not related to a specific content aggregation structure, i.e., context independent data.
SCO meta-data, if it is included, must be context independent. These meta-data are placed in the <resource> subsections of the <resources> section of the course manifest file
SCORM SCO Meta-Data (3/3)
SCORM Asset Meta-Data (1/2)Asset meta-data is data describing course and SCO assets, such as graphics files, individual web pages, media streams, xml and javascript files Asset meta-data can be classified into three categories
data that can be searched externally such as asset title, description, date of creation and version, context independent data for the Asset, and data that can be used to create repositories of sharable Assets
Like SCO meta-data, Asset meta-data must also be context independent, allowing Assets to be shared among different courses. Asset meta-data are placed in the <file> subsection of a <resource> subsection in the manifest file
SCORM Asset Meta-Data (2/2)
Content Aggregation, SCO & Assert meta-data
Conclusion
There is a need for content repository and Learn Content Management System (LCMS)LMS and SCO has its own responsibilities
Q&A