Reusable Competency Definitions Team Update

1
Re-usable Competency Definitions Team Update

• Robby Robson
• 6 December 2000

2
Presentation Overview

• History and Process
• Scope
• Data Model
• Binding and Best Practices
• Examples

3
RCD History Process

• IEEE P1484.20
• Need for CDs in Profiles
• WG Approved at August TB as self-actuated WG with
  short time line and minimal IMS staff support
• Created Information Model Looked at Examples
  Refined Information Model.

4
RCD SCOPE

• Limited to definitions
• Competency includes outcomes, skills, knowledge,
  etc.
• For interchange and semantic interoperability
• Does not address use, certification, etc.

5
RCD Data Model

• Mandatory parts
• GUID (machine readable)
• Title (human intelligible)
• Textual definition (human intelligible)
• Optional parts
• More precise definition according to some model
  of how competencies are defined
• Additional meta-data

6
RCD Data Model Notes

• Languages
• Human interpretable text are Langstrings
• Multiplicity is one per language
• Model element consists of
• Set of Statements
• Statement ID
• Statement Name
• Statement Text
• Statement Name is an element in the particular
  Model, e.g. proficiency, criteria, and
  indicators.

7
RCD Data Model Tabular Representation
8
RCD Binding Best Practices Guide

• Pseudo-XML bindings given in proposed base
  document
• From Examples
• Includes SCORM Compliance as an example
• Binding to be done with IMS staff assistance
• Best Practices
• Will consist of introduction plus examples
• Open for input on other recommended portions of
  the Best Practices Guide

9
IMS Schedule

• Approve Timeline (consistent with August TB
  resolution).
• Nov 2000 RCD Base Document Approved
• Feb 2001 RCD Content Management Specifications
  public draft phase
• May 2001 RCD Specifications Final
• June 2001 - IEEE Base Document

10
Example

• ltRCDgt
• ltGUIDgt(To conform with IMS practice)lt/GUIDgt
• ltTitlegtltlangstring lang"en_US"gt
• Team Playerlt/langstringgtlt/Titlegt
• ltDescriptiongt ltlangstring lang"en_US"gt
• Able to effectively execute work as a team
  member. lt/langstringgtlt/Descriptiongt
• lt/RCDgt

11
Example

• ltRCDgt
• ltGUIDgt(To conform with IMS practice)lt/GUIDgt
• ltTitlegtltlangstring lang"en_US"gtSCORM 1.1 LMS
  Runtime Conformancelt/langstringgtlt/Titlegt
• ltDescriptiongtltlangstring lang"en_US"gtA
  learning management system which conform to the
  SCORM 1.1 specification for runtime environment
  conformance.  The LMS must (1) conform with
  section 6 of the SCORM version 1.1, (2) launch
  SCORM version 1.1 Conformant Assignable Unit, (3)
  implement all of the API calls correctly, (4)
  fully support mandatory CMI data model elements
  and at a minimum can store (LMSSetValue and
  LMSGetValue) optional CMI data model elements
  across a single session of the lt/langstringgtlt/Desc
  riptiongt
• ltDefinitiongt
• ltModelgtltvocabgtltvsourcegthttp//www.adlnet.org/scorm
  /conformacevocab/lt/vsourcegtltvvaluegtSCORM
  Conformance Matrixlt/vvaluegtlt/vocabgtlt/Modelgt
• ltStatementgt
• ltStatementnamegtltvocabgtltvsourcegthttp//www.adlnet
  .org/scorm/conformacevocab/lt/vsourcegtltvvaluegtConfo
  rmancelt/vvaluegtlt/vocabgt lt/Statementnamegt
• ltStatementtextgtltlangstring
  lang"en_USgtConformant with section 6 of the
  SCORM version 1.0lt/langstringgtlt/Statementtextgt
• lt/Statementgt
• ltStatementgt lt/Statementgt
• lt/RCDgt