Standards, Reusability, and the Mating Habits of Learning Content Robby Robson Eduworks Corporation rrobson@eduworks. com Code 4 Lib 2006 AICC Meeting February 2, 2006 15 - 02 - 2006
What’s the User’s Problem? ¢ Learning content tends to be l l ¢ ¢ ¢ Written in large pieces Re-used in small chunks Highly interactive Evolving in sophistication Lots of legacy content must be converted to run (and report results) to learning management systems Reuse requires mixing apples and oranges Interoperability requires SCORM (Sharable Content Object Reference Model) 2 Code 4 Lib 2006 15 - 02 - 2006
What’s the Technical Problem? ¢ ¢ ¢ Learning content is (or should be) highly interactive l Quizzes (at least) l Videos, simulations, games, “smart graphics” Learning content comes l In different formats (e. g. Authorware vs. HTML) l With different navigation schemes l With different scripts stored in different places We need: l “SCOs” (Sharable Content Objects) l A common content model for SCOs 3 Code 4 Lib 2006 15 - 02 - 2006
What we did last year … SCORE (SCOrm Reuse) 1 2 3 SCORE Conversion Utility Source Content SCORE Exchange Format SCORE Tool SCORE Exchange Format XML imported into a SCORE Tool where converted content can be edited into a styled. Output is a SCORE Content (SCO) SCORM Package SCORE Content (SCO) SCORM Aggregation Tool 4 Source Content is converted into an XMLbased Interchange Format by a Conversion Utility SCO SCO An Aggregation Tool is used to aggregate and sequence SCOs into a conformant SCORM Package Code 4 Lib 2006 15 - 02 - 2006
Screen shots & tiny fonts … (Maybe the demo will work) Code 4 Lib 2006 AICC Meeting February 2, 2006 15 - 02 - 2006
SCORE Content Conversion 6 Code 4 Lib 2006 15 - 02 - 2006
SCORE SCO Editing 7 Code 4 Lib 2006 15 - 02 - 2006
SCORM Utilities 8 Code 4 Lib 2006 15 - 02 - 2006
Fidelity of Converted Content Authorware Example Unstructured HTML Example (From typical learning content authoring tool)9 Code 4 Lib 2006 15 - 02 - 2006
SCORE Prototype Demonstration 10 Code 4 Lib 2006 15 - 02 - 2006
Project Result Central Importance of a Data Model SCORE Exchange Format SCORE Conversion Utility Source Content feature identification map source to XML schema definition SCORE Tool consistent content elements SCORE Data Model 11 Code 4 Lib 2006 15 - 02 - 2006
Project Result The Success of the Data Model depends on the Card Deck Metaphor Card Deck shared state information across cards Card (location) navigation 12 Code 4 Lib 2006 15 - 02 - 2006
Project Result The Role of Generic and Learning-specific Content Elements Identification/Heading generic content elements Content Region Location Navigation learning specific content elements UI Model 13 Code 4 Lib 2006 15 - 02 - 2006
Project Result Content Element need to Share State Data across Locations Shared State Variables Location 1 Location 2 Content Element X 14 Content Element Y Code 4 Lib 2006 15 - 02 - 2006
• Project Partners • Eduworks • Advanced Distributed Learning Initiative (Joint ADL Co-Lab, Orlando) • LSI (Logistics Services International) • Mississippi State University (Center for Advanced Vehicular Systems) • NAVSEA Keyport 15 Code 4 Lib 2006 15 - 02 - 2006
XML Interchange Format based on OASIS Open. Document Format (ODF) Open specification ¢ Incorporates W 3 C specifications ¢ On ISO/IEC standards path ¢ Significant platform adoption demonstrates viability (Open Office, IBM Workplace) ¢ ODF profile (with extensions) can meet project requirements ¢ Open source library (AODL) available ¢ 16 Code 4 Lib 2006 15 - 02 - 2006
High Level Content Model Each SCO “Black Box” 1 or more Locations SCO contains 1 or more Content Components Location contains Component Location Component 17 Code 4 Lib 2006 ODF “primitive” Extended (e. g. “learning”) 15 - 02 - 2006
All Components Have ODF Content Component Common Properties • Height, Width • XY coordinate • Type Common Events • DOM event • Java. Script Handlers • Use optional Delivery Format Generator • XML to delivery format • Default dhtml Editor • means to visualize ODF component • means to edit an ODF component The component approach also supports a modular approach to implementing content converters 18 Code 4 Lib 2006 15 - 02 - 2006
ODF Content Components Location may contain: ODF Primitive Extended Text Box Interaction (QTI) Image HTML Blob Object Smart Graphic Plugin ¢ ¢ ¢ S 1000 D 19 ¢ ¢ Code 4 Lib 2006 Locations contain content components Components are cleanly encapsulated (can be inserted, cut and pasted as wholes) Primitive components are directly taken from ODF. Extended content components may be largely based on ODF Extended content components may use an ODF wrapper and be largely based on other schemas (e. g. QTI for interactions) 15 - 02 - 2006
Why am I telling you all this? ¢ Cool Open Source Projects AODL (now) www. opendocument 4 all. com l XML SCORM Studio (October) ksaunders@eduworks. com l ¢ 20 Raise issues concerning Content 4 Lib Code 4 Lib 2006 15 - 02 - 2006
Скачать презентацию Standards Reusability and the Mating Habits of Learning
8486b98a6ade976a5dce474779b5b26e.ppt