18 march 2004 colin milligan funded by. © reload 2003, funded by workshop structure session i...

35
18 March 2004 Colin Milligan funded by

Upload: isabel-brooks

Post on 26-Mar-2015

217 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

18 March 2004

Colin Milligan

funded by

Page 2: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Workshop Structure

Session IIntroduction: Interoperability and Reload

Session IIContent Packages

Session IIIMetadata

Session IVSCORM

Page 3: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Interoperability

orig. src: Charles Duncan, Intrallect

Page 4: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Why we need standards

Standards Promote:• Persistence

– Remember laser disc based materials,

• Discovery– Beyond your local community

• Sharing between different systems– For efficiency.

• Flexibility– Internationalization and Accessibility.

Page 5: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Who makes standards.

IMS Working Groups

specification implementation standard

User Needs

New Technology

Research

review and feedback

IEEE

CEN/ISSS

ISO

ADL SCORM

(conformance)(certification)

Page 6: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

What do they cover?

• Metadata

• Content Packaging

• Simple Sequencing

• Learning Design

• Question and Test Interoperability

• Digital Repositories

• Enterprise

• Accessibility

• Learner Information Profile

• Competency (and Portfolios)

• (Interactive Content)

Page 7: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Specification Documents

• Each Spec. has 3 components:– Information Binding

• XML Binding – how to describe.

– Information Model• What to describe: definitions, rules and

constraints

– Best Practice Guide• Guidelines for using and implementing.

• Available from IMS web site for free

Page 8: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Example: Content Package

imsmanifest.xml

Metadata

Resources

Page 9: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

<manifest xmlns="http://www.imsglobal.org/xsd/imscp_v1p1“ xmlns:imsmd="http://www.imsglobal.org/xsd/imsmd_v1p2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" identifier="MANIFEST-65A1BA8F-3A73-479E-0F63-163FFDA5B0E1" xsi:schemaLocation="http://www.imsglobal.org/xsd/imscp_v1p1 imscp_v1p1.xsd http://www.imsglobal.org/xsd/imsmd_v1p2 imsmd_v1p2p2.xsd">

<metadata /><organizations default="ORG-9CD8FA62-FF8C-B998-55CA-C1599862AEA6"> <organization identifier="ORG-9CD8FA62-FF8C-B998-55CA-C1599862AEA6" structure="hierarchical"> <title>Organization</title> <item identifier="ITEM-CD55CF07-609F-A592-E0B9-8EC68A32942F" isvisible="true" identifierref="RES-5669B8B0-

85B5-01D8-0A33-3284AE5A6218"> <title>sundialjelsim</title> </item> </organization></organizations><resources> <resource identifier="RES-5669B8B0-85B5-01D8-0A33-3284AE5A6218" type="webcontent" href="sundialjelsim.html"> <file href="images/jspowered.gif" /> <file href="images/solarGeom/sun.gif" /> <file href="jscore.jar" /> <file href="progress.jar" /> <file href="SolarGeom.jar" /> <file href="sundialjelsim.jsm" /> <file href="sundialjelsim.html" /> </resource> </resources></manifest>

imsmanifest.xml(how to interpret this package)

(how the content is organised)

(what resources are needed)

Page 10: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Why do we need tools?

• Avoid working directly with XML(files get much more complicated than

the one in our example),

• speed up xml creation.• reduce errors,• aid conformance (and uptake),

Page 11: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Where Does RELOAD fit?

Page 12: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

In Practice …

CREATECONTENT

PACKAGE &

ALTER[RELOAD

]

STORE[REPOSITORY]

DELIVER[MLE]

Page 13: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

RELOAD Tools

• Reference Implementation– Test, benchmark

• Visually assemble and manipulate Content Packages– Better than XML

• View Content Packages– For testing and preview.

Page 14: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

(screenshot)

details

Visual equivalent of imsmanifest.xml

files

Page 16: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Future

• RELOAD 1.1.1+ stable and feature complete

• Open Source – others are encouraged to extend, and are doing so

• Designed to adapt easily if specifications are revised.

Page 17: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Creating CPs with RELOAD

• 10 minute demo• Hands On• Further Tasks• Round-up

Page 18: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Hands On: A First CP

• Core Tasks (p7: Collect Resources Together -p16)– Collect Content– Create Working Directory– Prepare Placeholders– Import Content– Make Organizations– Preview– Rearrange– Add Metadata– Package and Zip

Page 19: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Advanced tasks

• Advanced Tasks (p23-25)– Manifests– Dependencies

Page 20: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Roundup

• RELOAD allows us to move from Abstract to Physical– Tests (proves) the specification– Links Content Creation and Content

Sharing

Page 21: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

3. Metadata

• Describes resources:– General (title and keywords)– Lifecycle (versioning)– Metametadata (who wrote the record)– Technical (assisting implementation)– Educational (level)– Rights (copyright and other restrictions)– Relation (to other content)– Annotation (usage metadata)– Classification (in a system)

Page 22: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Why metadata is important

• Discovering Resources– Description, educational MD

• Using Resources– Version control, technical

• Enforcing Rights• Attributing Ownership/Authorship

Page 23: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Application Profiles

• Metadata must be interoperable– ~80 elements in LOM– Decide on important elements at a

local (organisational) level– Use shared vocabulary/taxonomy

• Kinetics, motion, physics …

– Implement Rules and restrictions

Page 24: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Good Metadata

• Added by Information Professionals• Consistent across a repository• Assists Reuse

– Usage metadata – recommendation systems like Amazon:

Page 25: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Hands On Session

• Take your own content and create content packages.

• Add Metadata– http://www.cetis.ac.uk/profiles/

uklomcore

• If you don’t have any content of your own, get some here. – http://reload.ac.uk/ex/

• Aggregate Packages.

Page 26: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Roundup

• You should have been able to :– Make your content reusable– Describe your content– Aggregate your content with others.

Page 27: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Where next?

• A repository– JORUM – Merlot , SMETE

• Federated Search:

– Maricopa Learning Exchange – CAREO

• An LMS– WebCT, BlackBoard, Saba, Teknical

Page 28: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

4 SCORM

• SCORM: The Shareable Content Object Reference Model

• SCORM is real, – Certification (soon),– Now (almost).

Page 29: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

SCORM History

• US Dept. of Defense, Boeing (AICC)• Training• Single User Model

• Drives (pulls) specs forward.

Page 30: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

SCORM Future

• Close harmonisation with equivalent IMS specs – avoiding divergence.

• Incorporating Simple Sequencing (1.3 –2004)

• Question and Test Interoperability (1.4)

• Simulations and adaptive learning (v2)

Page 31: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Hands On Session

• In addition to CP and MD, SCORM includes support for management of learning (p20 SCORM Elements -22):– Pre-requisites– Max time allowed– Time Limit Action– Data from LMS– Mastery Score

Page 32: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

SCORM Player

• Allows SCORM functionality preview without using an LMS.– Simple to set up– See what the learner sees– Test functionality.

– SingleCourseEx.zip

Page 33: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

The Future

• RELOAD Editor is stable• Others are developing functionality

– SCORM 1.3 editor (ADL)– ALOHA Metadata Editor (CanCore)– VDEX Editor (ICBL)

• Learning Design

Page 34: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Roundup

• RELOAD is about enabling– Engage with the standards– Test the standards– Improve the tools.

Page 35: 18 March 2004 Colin Milligan funded by. © RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content

© RELOAD 2003, funded by

Contact

Colin [email protected]

http://www.reload.ac.uk/