CMI WG Status

1
CMI WG Status

• Tyde Richards
• Chair CMI WG
• tyde_richards_at_us.ibm.com

2
Overview

• Background on CMI Standardization
• WG Status
• WG process and members
• Status P1484.11.2 API draft standard
• Status P1484.11.1 Data Model draft standard
• Future Directions
• Getting involved
• QA

3
CMI Background

• AICC CMI specification submitted 1998
• Original Project all inclusive too large
• Decision to adopt multiple small Projects
• 7 proposed
• API and Runtime Data Model accepted
• Moving forward proposal to
• Retain original CMI conceptual scope
• Standardize SCORM components where appropriate

4
CMI Conceptual Scope
Reusable Content Objects
Assuming

• Communication Model
• runtime data model
• transport bindings

• Aggregation Model
• learning activities
• related resources
• simple pedagogy
• sequencing

LOM
Competency Definitions
In Scope
Not in Scope
5
Working Group Process

• Editing and ballot resolution
• Weekly 2 hour meetings
• Active use of email reflector
• Small size and informal
• Editor funded by ADL (Scott Lewis)
• 11 active members
• Usually 6-8 in weekly calls
• Issue tracking spreadsheets
• new draft every 1-2 weeks

6
Working Group Members

• Frank Farance - Farance, Inc., (SC36 Chair)
• Lenny Greenberg - Pathlore
• Jack Hyde AICC CMI WG chair
• Tom King - Macromedia
• Scott Lewis ADL (technical writer)
• Rolf Lindner - Darmstadt University
• Kiyoshi Nakabayashi - NTT-X, (ALIC)
• Claude Ostyn - Click2Learn
• Dan Rehak - Carnegie Mellon University
• Tyde Richards IBM, (CMI WG Chair)
• Robby Robson - Eduworks, (IEEE LTSC Chair)
• Schawn Thropp - ADL (SCORM engineer)

7
Status P1484.11.2
ECMAScript API for Content to Runtime Services
Communication

• API draft standard submitted to IEEE SA
• New Features
• Addition of state model
• Addition of error codes
• First round balloting complete
• 22 affirmative, 5 negative 77 affirmative
• About 350 comments
• Comment resolution underway

8
Status P1484.11.1Data Model for Content Object
Communication

• Data Model draft undergoing final edits
• New Features
• Data model represented in ISO 11404
• Principled changes to balance past, future
• SCORM relevant changes to status, score
• Balloting group invitation soon

9
Future Directions

• Completing current work
• API standard hopefully Q4 2002
• Data Model standard hopefully Q1 2003
• Planning new projects
• IMS Content Packaging (pending IMS submission)
• API Data Model binding document(consider SCORM
  excerpt as base document)

10
Getting Involved

• Two methods you can do both !
• Participating in the WG
• Need to be a member of the IEEE LTSC
• Need to contribute time and expertise
• Participating in CMI balloting groups
• Need to be a member of IEEE or IEEE CS
• Need to be a member of IEEE SA

11
Q A
For additional information or to get
involved Please contact tyde_richards_at_us.ibm.com