These are just my raw notes from Day one as I entered them into my local wiki. brent.

Notes Day One


Compliance Program


10 years of IMS meetings.

Improve global sector interoperability; company interacts with IMS Compliance program to recieve IMS "conformance" marks. Vendor would make conformance statements public along with evidence. May require, when appropriate, testing against IMS-approved test application data.

Performance marks for tools and pubished work (published works might be Content series, Meta-data, etc.).

Vendor Obligations

  • do self testing
  • submit request for conformance mark
  • conformance declaration
  • evidence of conformance

Program will be launched within 90 days.

Outreach Program

Outreach Materials:

  • basic information - brochure, case study
  • workshops, journal articles, white papers, etc.

Targeted projects

Content Packaging: Past, Present & Future Development

Colin Smyth

Time to start reviewing package specification.

Content Packaging is utilized by a variety of systems to move many things. Is a "generic container".

Types of Packages:

  • learning mateials
  • composite objects, eg. ePortfolio, QTI, etc
  • Collections of composite objects
  • table of contents and resource-less

Functional Issues:

  • multiple organizations
  • sub-manifestations (lots of issues, sequencing, nesting)
  • 'isvisible' attribute usage clarification (being used in inconsistent ways)
  • usage of XInclude/XLink/XPointer
  • Identifiers (for accessability?)

1.2 work needs to know what the community wants, how they are doing things in best practice.

model v.1.2

  • new functionality
  • functional clarifications
  • total documentation rewrite and expansion

Work to start on 1st April 2005.

Content Packaging 1.1.4 changes and common issues in CP interoperability

Wilbert Kraan

[technical discussion]

Using CP to move around lists of resources. Use <organisations> but leave out <organisations>

Conflicts on schemalocations; look at examples provided by IMS.

If you use a local XSD you need to put it in the package; should be identical to the official on-line XSD.

Have at least one <item> in each <orgnization>

declare everything in the manifest. including spacer.gifs, js files.

Common Content Packaging Problems

  • incorrect schemalocations / namespaces
  • missing or wrong file references
  • missing resources
  • manifest.xml not at the root of the package
  • invalid characters
  • non-unique identifiers
  • file failed to import
  • zip file format incompatability (look at zip file format?)

SCORM 2004 Sequencing Tutorial

Nina Pasini Deibler and Bill Blackman

SCORM 2004 has added the ability to add sequencing rules outside of the SCOs. Rules are written at the aggregation (not SCO) level

  • all of the children must follow all the rules of the parent
  • Content structure diagrams show the intended path the learner should take through the instruction.

Presentation Rules

  • present the content in a linear order, with forward and backward buttons. FLOW = TRUE.
  • allow the learner to choose the order. from the table of contents, may be used with FLOW, CHOICE=TRUE (default value)
  • present the content only in the prescribed order; with forward and backward buttons, CHOICE=FALSE
  • the learner can't go back once started; useful with tests and branching, FORWARD ONLY, with choice, if learner selects a late event, learner wont' see the previous events
  • Allow the learner to exit the parent

Conditional Sequencing Rules

  • Global Variables (Objectives); read by LMS/VLE to sequence SCOs.

Roll Up

  • used by parent to determine progress; scores?

Sequencing Templates and Models

  • scenario teaching (game style)
  • user specific (one route for CEO, one for new employer, etc...)
Last modified 10 years ago Last modified on 2009-05-22T06:10:39+09:00