1. Standards, Reusability, and the Mating Habits of Learning Content Robby Robson Eduworks Corporation rrobson@eduworks.com

2. 15 - 02 - 2006Code4Lib 2006 2 What’s the User’s Problem? Learning content tends to be 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)

3. 15 - 02 - 2006Code4Lib 2006 3 What’s the Technical Problem? Learning content is (or should be) highly interactive Quizzes (at least) Videos, simulations, games, “smart graphics” Learning content comes In different formats (e.g. Authorware vs. HTML) With different navigation schemes With different scripts stored in different places We need: “SCOs” (Sharable Content Objects) A common content model for SCOs

4. 15 - 02 - 2006Code4Lib 2006 4 What we did last year … SCORE SCORE Exchange Format SCORE Conversion Utility Source Content SCORE Content (SCO) SCORE Tool SCORE Exchange Format SCORM Aggregation Tool SCORE Content (SCO) SCORE Content (SCO) SCORE Content (SCO) SCORM Package SCO Source Content is converted into an XML- based Interchange Format by a Conversion Utility XML imported into a SCORE Tool where converted content can be edited into a styled. Output is a SCO An Aggregation Tool is used to aggregate and sequence SCOs into a conformant SCORM Package 1 2 3 (SCOrm Reuse)

5. Screen shots & tiny fonts … (Maybe the demo will work)

6. 15 - 02 - 2006Code4Lib 2006 6 SCORE Content Conversion

7. 15 - 02 - 2006Code4Lib 2006 7 SCORE SCO Editing

8. 15 - 02 - 2006Code4Lib 2006 8 SCORM Utilities

9. 15 - 02 - 2006Code4Lib 2006 9 Fidelity of Converted Content Authorware Example Unstructured HTML Example (From typical learning content authoring tool)

10. 15 - 02 - 2006Code4Lib 2006 10 SCORE Prototype Demonstration

11. 15 - 02 - 2006Code4Lib 2006 11 Project Result Central Importance of a Data Model Source Content SCORE Exchange Format SCORE Tool SCORE Conversion Utility feature identification map source to XML schema definition consistent content elements SCORE Data Model

12. 15 - 02 - 2006Code4Lib 2006 12 Project Result The Success of the Data Model depends on the Card Deck Metaphor Card (location) shared state information across cards navigation Card Deck

13. 15 - 02 - 2006Code4Lib 2006 13 Project Result The Role of Generic and Learning-specific Content Elements Navigation Identification/Heading Content Region learning specific content elements generic content elements UI Model Location

14. 15 - 02 - 2006Code4Lib 2006 14 Project Result Content Element need to Share State Data across Locations Content Element Y Content Element X Location 1Location 2 Shared State Variables

15. 15 - 02 - 2006Code4Lib 2006 15 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

16. 15 - 02 - 2006Code4Lib 2006 16 XML Interchange Format based on OASIS OpenDocument Format (ODF) Open specification Incorporates W3C 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

17. 15 - 02 - 2006Code4Lib 2006 17 High Level Content Model Location Component Location Component Each SCO “Black Box” 1 or more Locations contains SCO contains 1 or more Content Components ODF “primitive” Extended (e.g. “learning”)

18. 15 - 02 - 2006Code4Lib 2006 18 All Components Have ODF Content Component Common Properties Height, Width XY coordinate Type Common Events DOM event JavaScript Handlers Use optional Editor means to visualize ODF component means to edit an ODF component Delivery Format Generator XML to delivery format Default dhtml The component approach also supports a modular approach to implementing content converters

19. 15 - 02 - 2006Code4Lib 2006 19 ODF Content Components 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) Text Box Interaction (QTI) Smart Graphic S1000D HTML Blob Image Object Plugin ODF PrimitiveExtended Location may contain:

20. 15 - 02 - 2006Code4Lib 2006 20 Why am I telling you all this? Cool Open Source Projects AODL (now) www.opendocument4all.com www.opendocument4all.com XML SCORM Studio (October) ksaunders@eduworks.com ksaunders@eduworks.com Raise issues concerning Content4Lib