from learningObject to SCORM manifest

[john_hunt@us.ibm.com]

Dear DITA learning SC,

For our ongoing discussion about processing
priorities and mapping from the DITA learning map domain to a SCORM manifest,
see http://wiki.oasis-open.org/dita/LearningContent/map2manifest in our
wiki, with content repeated below for the email record.

Join us for discussion today at this
week's meeting.

John
___________________________________
John Hunt
DITA Architect / Lotus Information Development Center
Chair, OASIS DITA learning and training content sub-committee
IBM Software Group/Lotus Software
phone: 617.245.8053; t/l 268.9401
john_hunt@us.ibm.com


Mapping from DITA learning map domain to SCORM manifest

This describes some basic mapping from the DITA learning map domain to a simple SCORM manifest.

DITA map domain

The DITA map domain uses specialized topicref's to define map elements for a learningObject and learningGroup. As a domain, these elements are available for use in any DITA map type, including generic map, bookmap, or other specialized map types yet to be developed.

learningObject

organizes topic references to DITA learning topics as a learning object.

Contains:

( topicmeta (Optional) then lcMapLom (Optional) then learningPlanRef (Optional) then ( learningOverviewRef or learningPreAssessmentRef) (Optional) learningContentRef (Optional) then ( learningPostAssessmentRef or learningSummaryRef ) (Optional) )

learningGroup

learningGroup introduces and groups learning objects into higher-level organizations, such as course-level, module-level, or lesson-level.

A learningGroup may include a topic reference to a top-level learningOverview topic. A learningGroup can also contain other <learningGroup> elements, allowing you to organize learning content at course, module, or other higher-levels of hierarchy.

Contains:

( topicmeta (optional) then lcMapLom (Optional) then learningPlanRef (Optional) then ( learningOverviewRef or learningPreAssessmentRef ) (any number) ( learningObject or learningGroup ) (any number) then ( learningPostAssessmentRef or learningSummaryRef ) (any number) )

A sample learningObject

And this sample from our design spec:

<learningObject collection-type="sequence" href=""top_beneoverview.dita"" type="learningOverview">
  <learningOverviewRef href=""BeneStructuredOverview.dita"" type="learningOverview"/>
  <learningContentRef href=""BeneStructured.dita"" type="learningContent"/>
  <learningPostAssessmentRef href=""BeneStructuredAssess.dita"" type="learningAssessment"/>
  <learningSummaryRef href=""BeneStructuredSummary.dita"" type="learningSummary"/>
</learningObject>

A simple imsmanifest for the sample learningObject

So, a basic imsmanifest might be something like this:

<manifest xmlns:lom="http://ltsc.ieee.org/xsd/LOM"
        xmlns="http://www.imsglobal.org/xsd/imscp_v1p1"
        xmlns:adlcp="http://www.adlnet.org/xsd/adlcp_v1p3"
        xmlns:imsss="http://www.imsglobal.org/xsd/imsss"
        xmlns:adlnav="http://www.adlnet.org/xsd/adlnav_v1p3"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        identifier="MANIFEST-FDC59F51-B25F-70CF-3923-B549F45F83F0"
        xsi:schemaLocation="http://www.imsglobal.org/xsd/imscp_v1p1 imscp_v1p1.xsd http://ltsc.ieee.org/xsd/LOM lom.xsd http://www.adlnet.org/xsd/adlcp_v1p3 adlcp_v1p3.xsd http://www.imsglobal.org/xsd/imsss imsss_v1p0.xsd http://www.adlnet.org/xsd/adlnav_v1p3 adlnav_v1p3.xsd"
        version="1.3">
 <metadata>
    <schema>ADL SCORM</schema>
    <schemaversion>CAM 1.3</schemaversion>
 </metadata>
 <organizations default="Course">
    <organization identifier="Course" structure="hierarchical">
       <title>Why DITA for learning content?</title>
       <item identifier="d1e7" isvisible="true" identifierref="res_d1e7">
          <title>The benefits of structured content</title>
          <imsss:sequencing>
             <imsss:controlMode choice="true" choiceExit="true" flow="true" forwardOnly="false"
                                useCurrentAttemptObjectiveInfo="true"
                                useCurrentAttemptProgressInfo="true"/>
          </imsss:sequencing>
       </item>
    </organization>
 </organizations>
 <resources>
    <resource identifier="res_d1e7" type="webcontent"
              href=""topics/top_beneoverview.html""
              adlcp:scormType="sco">
       <file href=""topics/BeneStructuredOverview.html"/>"
       <file href=""topics/BeneStructured.html"/>"
       <file href=""topics/BeneStructuredAssess.html"/>"
       <file href=""topics/BeneStructuredSummary.html"/>"
       <file href=""commonltr.css"/>"
       <file href=""js/APIWrapper.js"/>"
       <file href=""js/courseFunctions.js"/>"
    </resource>
</resources>
</manifest>

And I would assume that the html files above could include next/prev/parent links to each other, within the same resource group.