St t ithi th SCOStructure within the SCO -...

St t ithi th SCOStructure within the SCOA Strategy for Effective Content Reuse

T de RichardsTyde RichardsEduworks Corporationtrichards@eduworks [email protected]

ADL International PlugfestJanuary 18, 2006

OverviewOverviewProblem Area

Requirements for representing content below the SCO levelImplications for effective content reuse

BackgroundTwo prototype projects sponsored by the Joint ADL Co-Lab

2004-5 SCORE Prototype (LSI, Eduworks, NUWC)Legacy content conversion into SCOs P d i l d i f iPedagogical and user interface consistency

2005-6 XML SCORM Studio (Eduworks, MSState, LSI, NUWC, JADL)Improve SCORE technical approachEvaluate benefits of ADL OPELEvaluate benefits of ADL OPELBase content format on open specificationsImprove usability


BIG PICTUREBIG PICTURE

Reuse is a major goal ofSCORM Program“L i Obj ”“Learning Objects”

Reuse entailsStarting with instructional contextStarting with instructional contextFinding appropriate contentCutting & PastingCutting & PastingRe-stylingPackaging for SCORM Delivery


g g y

ProblemProblem

Tools do not support this type of reuse today

Formats are proprietaryContent is locally heldSCORM tools operate on content not learning experiences


2004 5 SCORE Project Goal2004-5 SCORE Project Goal

Develop tools, techniques, and procedures to Effectively disaggregate existing coursewareSeparate presentation from content Mix and match content from different sourcesMake SCOs this wayProduce instructionally sound learning y gexperience


Motivated byMotivated by…

Quantity of non-SCORM legacy contentSCORM treats the SCO as a “black box”

N t f d i l i tNo support for pedagogical consistency across SCOs from different sourcesNo support for user interface consistency across pp ySCOs from different sources

Solving the content conversion problem entailsO i th bl k bOpening the black boxDefining a common content model for SCO-level content


How we assumed it would workHow we assumed it would work

SCORE Source Content isSCOREExchange

Format

SCOREConversio

nUtility

SourceContent

Source Content is converted into an XML-based Exchange Formatby a Conversion Utility

1

SCOREContent

SCORETool

SCOREExchange

Format

The Exchange Format is imported into the SCORE Tool where converted 2

(SCO)

SCORM

content can be edited into a styled, conformant SCO

An Aggregation Tool suchSCORM

AggregationTool

SCOREContent(SCO)

SCOREContent(SCO)

SCOREContent(SCO)

SCORMPackage

SCOSCO

SCO

An Aggregation Tool such as Reload is used to aggregate and sequence SCOs into a conformant SCORM Package

3


SCOREContentContent

Conversion


SCORESCOSCO

Editing


SCORM Utilities


Fidelity of Converted ContentFidelity of Converted Content

AuthorwareSource Content

UnstructuredHTML “Blob”

Source Content


SCORE Prototype DemonstrationSCORE Prototype Demonstration


SCORE Project ResultsSCORE Project Results

Created pedagogically and graphically consistentCreated pedagogically and graphically consistent SCOs using rich media content

From different sourcesFrom different sourcesIn different content formats

Learned that structure, not just format, are important for j pconverting coursewareDeveloped repeatable content conversion methodologyFormed opinions about representing SCO content


Project ResultThe basic SCORE Process

SourceContentSource

ContentSourceContent

SCOREExchange

Format SCORE

ToolSCORMPackage

SCOREConversion

UtilitySCORE

ConversionUtility

SCOREConversion

Utilityy


Project ResultA Content Conversion Methodology

intended users technical constraintsnecessary

support materials ?

intended

technical constraints on delivery format

pp

Planning SCORE C t t

intendedpedagogic use ? pedagogy-to-SCORM

mappingContent

Conversion

user interfacestyle conventions

source content in convertible format


Project ResultThe Central Importance of a Data Model

SourceSCORE

Exchange SCORESCORE

ConversionContent Format ToolUtility

featuremap

source XMLschema

consistentcontentidentification to

XML

schemadefinition

contentelements

SCORE Data Model


Project ResultThe Success of the Data ModelThe Success of the Data Model

depends on the Card Deck Metaphor

Card Deck

Card(location)

sharedstate information

across cards(location)

navigation


Project ResultjThe Role of Generic and

Learning-specific Content Elementsg p

Identification/HeadingIdentification/Heading

Content Region

genericcontent

elements

i Content Region

learningspecificcontent

elements

Location

Navigation elements

UI Model


Project ResultContent Element need to Share StateContent Element need to Share State

Data across Locations

Shared State Variables

Location 1 Location 2

ContentElement

Y

ContentElement

X


Project ResultA Requirement for Linear and RelationalA Requirement for Linear and Relational

Navigation within the SCO

Linear Navigationnext, previous, first, last

Linear

R l i l N i i

• location 1• location 2• location 3• location 4

Relational Navigationhelp, browse, related content

RelationalRelational

relation

relation

L1 L3

L4L2


Project ResultI li ti f St t d N i ti ?Implications of State and Navigation?

LMS – SSN and maybe State Persistence

Current SCORM Black BoxSCO

Black BoxSCO

Black BoxSCO

navigation and stateservices at location level

special requirements atSCO-boundary locationsservices at location level SCO-boundary locations

W ’ i thiWe’re seeing this


SCO SCO SCO


2005-6 XML SCORM Studio Project Goals

Prototype an end-to-end user-centric solution for the SCORM content lifecycleT h i ll i d b SCORE t tTechnically improve and base SCORE prototype capabilities on an open XML specification Use the technical and design expertise of the MSUUse the technical and design expertise of the MSU InSite Studio Team to improve usability and support for assessmentsEvaluate the Joint ADL Co-Lab's Open Platform for e-Learning (OPEL) and use in prototype if feasible


Implementation ApproachImplementation Approach

Second Problem SCO AggregationAnd

SequencingImportExport

Multiple SCOsDelivery Format(SCORM PIF)

Sequencing

First Problem SCO Conversionand Editing

Export

1 SCODelivery Format

(SCORM PIF)g

(SCORE Prototype)ImportExport

1 SCOXML Exchange

Format


Format

MSU InSite Studio TeamMSU InSite Studio TeamMSU InSite Studio TeamMSU InSite Studio Team

• Brings expertise from InSite Studio• User-centric authoring tool• Validated by teacher authorsy• Support for SCORM content• Support for IMS QTI assessments

• Will provide• User interface design expertise• Interactions based on IMS QTI


A Few Words about OPEL(Open Platform for E-Learning)

StoreContent

RunContent

CreateContent

ValidateContent

StoreContentStore

ContentRun

ContentRun

ContentCreateContentCreateContent

ValidateContentValidateContent

• Under development byJoint ADL Co Lab

PackageContent

Content ContentRegisterContent

Content ContentSequenceContent

PackageContentPackageContent

ContentContent ContentContentRegisterContentRegisterContent

ContentContent ContentContentSequenceContent

SequenceContent

Joint ADL Co-Lab• Technical lead is

Chris Bray Persistent Objects

Snap-In Loader & Messaging

SCORM Object ModelPersistent ObjectsPersistent Objects

Snap-In Loader & MessagingSnap-In Loader & Messaging

SCORM Object Model

• Intended to providecore functionality forADL prototype projects

OPEL Common Runtime Environment

Object-Relational Bridge Database

OPEL Common Runtime EnvironmentOPEL Common Runtime Environment

Object-Relational BridgeObject-Relational Bridge DatabaseDatabase

ADL prototype projectsso that the projects donot need to re-invent it Windows Linux Mac … Solaris

Microsoft .NET Framework / Novell Mono

Windows Linux Mac … SolarisWindows Linux Mac … Solaris

Microsoft .NET Framework / Novell MonoMicrosoft .NET Framework / Novell Mono


One Possible OPEL UseOne Possible OPEL Use

OPEL is being evaluatedas a framework to provideuser interface support


The Role of an Open SpecificationThe Role of an Open Specification

GoalSCO t t d l b d la SCO content model based on a general purpose open

specificationWhy ?

Jump start critical mass adoptionJump start critical mass adoptionLeverage platform adoption broader than learningProvide a non-proprietary basis for SCORM content

Requirements include the “card deck” metaphor linear and relational navigationUI styling

t t i d tievent triggered actions state variablesgeneric content elements learning specific content elements


learning-specific content elements

Open Specification CandidatesOpen Specification Candidates

OASIS DITAReadable help documentationType/specialization & relational browsing

OASIS Open Document Format (ODF)p ( )ISO standards track “office document” formatIncludes several W3C content formats

Rich Internet Application/UI languagespp g gMozilla XUL, Macromedia MXML, Microsoft XAMLAssociated with particular platforms

W3C Compound Document WGpIssues of integrating XML content specifications

Resource Aggregation Specifications MPEG 21.1


IMS Content Packaging

Decision to use OASIS ODFDecision to use OASIS ODF

Open specificationIncorporates W3C specificationsOn ISO/IEC standards pathSignificant platform adoption demonstrates viability (Open Office, IBM Workplace)ODF profile (with extensions) can meet

j t i tproject requirementsOpen source library (AODL) available


High Level Content ModelHigh Level Content Model

E h SCO “Bl k B ”

L ti

Each SCO “Black Box”1 or moreLocations

containsSCO1 or moreContent

Location

Location Component

co a sSCOcontains

Components

ODF “primitive”

Component

Location

Location

Component

Extended Component (e.g. “learning”)


All Components HaveAll Components HaveODF

Delivery Format Generator• XML to delivery format

ODF Content

ComponentCommon Properties

H i ht Width • Default dhtml• Height, Width• XY coordinate• Type

Common EventsDOM

Editor• means to visualize ODF component

• DOM event• JavaScript Handlers• Use optional

• means to edit an ODF component

The component approach also supports a modular approach to implementing content converters


Proposed Strategy for ODF Content Components

L ti t iA location contains content componentsAll content components share common capabilities and are cleanly

ODF Primitive Extended

Location may contain:

co o capab es a d a e c ea yencapsulated (can be inserted, cut and pasted as wholes)Primitive content components are directly taken from ODF.

TextBox

Interaction(QTI)

HTMLImage Extended content components may be largely based on ODF (e.g. a component for S1000D elements)Extended content components may use an ODF wrapper and be largely

SmartGraphic

BlobImage

Objectuse an ODF wrapper and be largely based on other schemas (e.g. others listed)S1000DPlugin


ConclusionConclusion

Problem AreaRequirements for representing content below the SCO levelImplications for effective content reuse

2004 5 SCORE P t t d t t d2004-5 SCORE Prototype demonstrated …Content conversion from multiple sources and formats into SCOs The benefits of an XML-based approach to achieve pedagogical and user interface consistency across SCOsuser interface consistency across SCOsA repeatable methodology for content conversion

2005-6 XML-based SCORM Studio (in progress) will add …Expanded support for the SCORM content lifecycleExpanded support for the SCORM content lifecycleImproved usabilityImproved implementation (leverage open source libraries)XML content representation for the SCO based on OASIS ODF


Date post:	09-Jun-2018
Category:	Documents
Upload:	lamtuong
View:	214 times
Download:	0 times

St t ithi th SCOStructure within the SCO -...

Documents