• Save
Content providers\' roles in the ASPECT project
Upcoming SlideShare
Loading in...5
×
 

Content providers\' roles in the ASPECT project

on

  • 1,520 views

A presentation I gave during the ASPECT WP5 meeting in Munich to describe the roles of content providers in ASPECT.

A presentation I gave during the ASPECT WP5 meeting in Munich to describe the roles of content providers in ASPECT.

Statistics

Views

Total Views
1,520
Views on SlideShare
1,353
Embed Views
167

Actions

Likes
0
Downloads
0
Comments
0

6 Embeds 167

http://www.aspect-project.org 90
http://aspect-project.org 62
http://aspect.eun.org 9
http://aspect-project.com 3
http://www.aspect-project.net 2
http://translate.googleusercontent.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • … is mainly focusing on WP2-related issues!
  • … Will be more WP3-related

Content providers\' roles in the ASPECT project Content providers\' roles in the ASPECT project Presentation Transcript

  • The Role of ASPECT Content Providers David Massart, EUN Munich, Germany – May 14, 2009
  • Outline • ASPECT goals and structure • WP5 objectives, tasks, and deliverables • Content-related Activities • Three content provider scenarios • Overview of this workshop
  • ASPECT Objectives (Context = School Community in Europe) 1. Analyse how a range of content-related standards and specifications compare 2. See how the implementation of standards and specifications will enhance pan- European interoperability 3. Establish best practices for combining existing specifications into complete solutions
  • • Metadata: IEEE LOM, Dublin Core • Vocabulary: XVD, VDEX, ZTHES, SKOS • Protocol: SQI, SPI, SRU/SRW, OAI-PMH • Query Language: CQL, PLQL, LRE-QL Content discovery •Registry: CORDRA, ADL Registry
  • Content discovery Content use •Format: IMS Content Packaging, SCORM, IMS Common Cartridge, IMS QTI • Identifier: Handle System, DOI •Access Control:Creative Commons, IMS Common Cartridge, LRE DRM
  • Content discovery Implementation Best practices of best practice Content use
  • Content discovery Implementation School Best practices of best practice pilots Content use
  • WP4 Dissemination WP2 Content discovery WP5 WP6 Implementation School Best practices WP3 of best practice pilots Content use WP7 Validation & Quality Insurance
  • WP5 Objectives 1. Apply a range of standards and specifications for content discovery and establish interoperable connections between them 2. Select a small set of recommended standards and specifications for content use and to apply them to tools and content where appropriate
  • WP5 Tasks 1. Connection of ASPECT partners’ repositories 2. Selection of content to match profiles of schools 3. Adding metadata to existing resources to increase discovery and reuse 4. System integration 5. Selection of a set of standards and specifications for content use 6. Report on implementation of standards in ASPECT
  • WP5 Deliverables 1. A critical mass of metadata that can be searched for and discovered seamlessly (M18 – Feb. 2010) 2. A critical mass of content (>200 MST SCORM) to which the common cartridge specs has been applied (M18 – Feb. 2010) 3. Integrated system v1.0 (M15 – Nov. 2009) 4. Integrated system v2.0 (M24 – Aug. 2010) 5. Report (M28 – Dec. 2010)
  • Content-Related Activities • Discovering and exchanging interoperable content requires: – Packaging content (and validating packages) – Describing content (and validating metadata) to enableitsdiscovery, assessment, and exchange – Exposing metadata (and validating protocols) – Searching metadata for content – Exchanging content (including access control) – Rendering content
  • Three Exchange Scenarios 1. Simple content – Available online – Open – Can be rendered in a web browser (plug-in) 2. Packaged content – SCORM – IMS Common Cartridge 3. Non-open content
  • Simple Content Scenario • Packaging content (and validating packages) • Describing content (and validating metadata) to enableitsdiscovery, assessment, and exchange • Exposing metadata (and validating protocols) • Searching metadata for content • Exchanging content (including access control) • Rendering content
  • Packaged Content Scenario • Packaging content (and validating packages) • Describing content (and validating metadata) to enableitsdiscovery, assessment,andexchange • Exposing metadata (and validating protocols) • Searching metadata for content • Exchanging content (including access control) • Rendering content
  • Non-Open Content Scenario • Packaging content (and validating packages) • Describing content (and validating metadata) to enableitsdiscovery, assessment, andexchange • Exposing metadata (and validating protocols) • Searching metadata for content • Exchanging content (including access control) • Rendering content
  • So, Today … WP2 WP5 WP6 Content Implementation School discovery of best practice pilots
  • And Tomorrow… WP3 WP5 WP6 Content Implementation School Use of best practice pilots
  • Questions ?