Sample Ad Advertise your business on myplick. Only $2.00 a month.
Comments:
Notes:
Slide 1: IMS Specification Adoption in Canada
Slide 2: Participation in Specification/Standardization Activities
• EduSpecs: Provide an opportunity for Canada to influence the creation of common specifications and standards, and thereby enable sales of Canadian online learning materials around the world. • Standards Council of Canada
Slide 3: Participation in Specification/Standardization Activities
• Participating membership in:
– IMS: Accessibility, Learning Design, etc. – ISO/IEC JTC1 SC36: Information Technology for Learning Education and Training
• Sponsored membership in:
– IEEE Learning Technology Standards Committee
Slide 4: Featured Implementers
• Learn Alberta.ca • eduSource • CanCore • A sample of the community in Canada using IMS specifications
Slide 5: LearnAlberta.ca portal
"allow efficient repurposing of learning objects to support curriculum development and management.“ -Alberta Learning
Slide 6: LearnAlberta.ca portal/repository
• audience-specific: students, teachers, parents, administrators, content providers, curriculum developers and other education stakeholders • The learning objects will support Alberta Programs of Study, i.e. curriculum outcomes. • Designed to support lifelong learning in Alberta
Slide 7: Content Packaging
• "defines a standardized set of structures that can be used to exchange content" • Proof of concept implementation • Makes use of the "organizations" section of the manifest: "describing zero, one, or multiple organizations of the content within a manifest"
Slide 8: Content Packaging
Slide 9: Done in conjunction with license agreement with National Geographic Soc.
Currently under development; available Fall 2003
Slide 10: Done in conjunction with license agreement with National Geographic Society
Slide 11: Done in conjunction with license agreement with National Geographic Society
Slide 12: Done in conjunction with license agreement with National Geographic Society
Slide 13: Done in conjunction with license agreement with National Geographic Society
Slide 14: Done in conjunction with license agreement with National Geographic Society
Slide 16: careo.org
Magee & Norman, Dublin Core 2002, "Building Digital Books…"
Slide 18: CA*Net 4 Connected Primary Partners
Athabasca Univ.
Netera NewMIC SFU Surrey Univ. of Waterloo Technologies Cogigraph Téléuniversité du Québec Tele Education NB
Slide 19: Goals:
• Create a testbed of linked and interoperable learning object repositories across Canada • Provide a forum for the ongoing development of the associated tools, systems, protocols and practices that will support such an infrastructure
Slide 20: Goals:
• Develop and promote national and international standards • Be fully bilingual • Develop a community of practice • Be accessible to all Canadians
Slide 21: Work Package Teams
• Repository Content Development Package Managers: NBDEN and NewMIC Foundation - Key Participating Partners: University of Waterloo; Cogigraph (Teleuniversite) Digital Rights Management - Package Managers: NBDEN with NRC Testing and Evaluation - Package Managers: Netera and Cogigraph (Teleuniversite) Metadata Development - Package Managers: Athabasca University and NBDEN Key Participating Partners: Cogigraph (Teleuniversite)
• • •
Slide 22: Work Package Teams
• Software Development - Package Manager: Cogigraph (Tele-universite ) Key Participating Partners: Athabasca University; NBDEN; NewMIC Foundation; Learning Commons, University of Calgary (in association with Netera) Hardware Integration - Package Managers: Netera and NewMIC Foundation Business and Management Models - Package Manager: Netera Key Participating Partners: NBDEN; Cogigraph (Tele-universite; University of Waterloo Community Building - Package Manager: University of Waterloo Key Participating Partner: Netera Project Management, Co-ordination and Communications Package Manager: Netera
• •
• •
Slide 23: Specifications:
Digital Repositories Interoperability:
– OAI Metadata harvesting (Athabasca University as lead) – Gateways to other recommended protocols, including Z39.50
Learning Design for resource description and structure Content packaging
Slide 24: IMS DRI: harvesting
Metadata Repository
1..* 0..*
ECL:
Edusource
Communication Language
Metadata Repository Services «uses»
2..*
uses 1..4
«system» SPLASH «system» CAREO «system» ALOHA
0..*
DRM services
«uses»
2..* «call» 1..* 1..* 2..* ask service 1..4 1..* eduSource Service Registry
2..* 1..*
eLearning Middleware Services
1..4 * 1..4
1..*
«system» EXPLORA
Digitized Resource Repository
1..* 0..*
Resource Management Services
«uses» *
«system» AD LIB
Content Packaging
Learning Design
for identification of services
design by Gilbert Paquette, Technologies Cogigraph (Tele-universite)
Slide 25: ECL: eduSource Communication Protocol
• "a meta-protocol to prevent code duplication for protocol access and to simplify maintenance when protocols evolve" "built inside a SOAP XML envelop on top of HTTP to provide communication between protocols such as OAI and Z39.50"
•
Slide 26: Goals:
eduSource Communication Protocol
design by Mike Mattson, Learning Commons, University of Calgary
Slide 27: Gateway Architecture
OAI Harvesting
ECL ECL ECL
JXTA P2P
Z39.50
ECL
Univ. of
IMS DRI SOAP & XQUERY
ECL
Slide 28: CanCore Learning Object Metadata Application Profile
Norm Friesen normf@athabascau.ca www.cancore.org
Slide 29: CanCore
Application profile: "customization of a standard to meet the needs particular communities of implementers with common applications requirements." Subset of LOM elements: 77 down to 56; 39 are active: ALL COVERED Guidelines document: best practice recommendations, 175 pp.
Slide 30: CanCore
E-learning specifications & standards communities are largely concerned with syntax and technical interoperation Effective metadata requires semantic specification and consensus Incorporate best practice from library and heritage communities Incorporate common practice from implemenations No other body is doing this across e-learning projects
Slide 31: CanCore
Complexity decreases
LOM Information Model: appx. 80 elements, little interpretation
Implementation CanCore
Specificity and Interoperability increases
Slide 32: CanCore: what LOM metadata is NOT
Is not information to be directly exposed to end-users Is not for version or rights management Is not a content model
Slide 33: CanCore Guidelines
Clarification
Slide 34: CanCore Guidelines
Clarification Best Practice Recommendations
Slide 35: CanCore Guidelines
Survey of use Clarification Best Practice Recommendations
Slide 36: CanCore Guidelines
Survey of use Clarification Best Practice Recommendations
Vocabulary Definitions
Slide 37: CanCore Guidelines
Survey of use Clarification Best Practice Recommendations echnical Implementation Notes Vocabulary Definitions
Slide 38: Guidelines revisions
• EduSource: primary partners
– AU, Netera Alliance, Téléuniversité du Québec, University of Waterloo, New Media Innovation Centre, TeleEducation New Brunswick.
• Alberta Learning • Centre recherche LICEF • Larger repository community:
– – – – Eisenhower National Clearinghouse CETIS; SESDL ARIADNE National Library
• Your input is welcome!
Slide 39: Element Subsets
• Different elements are important in different contexts • Need to see what consensus arises around element implementation • Many element values set through system development or system customization
Slide 40: Patterns of use in application profiles
• Adapted from CETIS • Some consistency, some divergence Legend
Required/Recommended Optional/Conditional Excluded/Not Supported
Slide 42: Sponsors
• • • • CANARIE Industry Canada Netera Alberta Learning
Slide 43: www.learnalberta.ca www.edusource.ca www.cancore.ca www.careo.org
normf@athabascau.ca