OERInterop-PrinciplesSummary

Content

 * 1) Transcoder in the sky
 * 2) * User who visits an OER respository, but the repository as format X and they need format Y. The repository provides a link to transcode the material (audio, video) into the format the user needs/wants. Tool could be housed locally, or remotely; transcoded copies could be saved locally, etc.
 * 3) Machine-to-machine interoperability (of content and metadata)
 * 4) * XML-dumps of content from OER
 * 5) * Base on existing spec
 * 6) Machine-to-person interoperability
 * 7) * Versioning
 * 8) * URL addressable
 * 9) Fair use?

Match content of interest to what the person wants

 * Role of metadata (more than bibliographic/administrative metadata)
 * Making as easy as possible to capture/generate metadata (make it invisible)
 * Discussion:
 * Who? Publishers?
 * What are the goals for a user? What are the impacts of those goals?
 * Common strategies? -> Metadata
 * Branding?
 * Community generated metadata, metadata is enhanced, how does original provider get talkback of the additional context
 * Getting linked to other OER sites once you find one site
 * Barriers:
 * Metadata must be present, and able to be presented, auto-generate if needed, providing vs. maintaining metadata
 * Basic Principles
 * Accessibility of URLs (URLs should be findable, not login/deep-web)
 * Identify things at more granular level (page in a course, not just the course)
 * Value of OER as a "stamp"/trademark

Social Graph

 * Not tackling issue of linking people-to-people
 * Linking people-to-content-to-people
 * Leverage existing social networks (e.g., Facebook)
 * Want to be able to exist in multiple/newer social networking platforms
 * Recommendations: Sites should add social bookmarking tools

Content Contribution and Distribution
Recommendations:
 * Offline authoring tools, what's out there?
 * Scenarios:
 * Delivery to Learning Management Systems (IMS Content Packaging, IMS Common Cartridge)
 * Mobile:
 * Use of SMS to ask for resource, and text-to-speech return (MobilEd)
 * Phone as a data capture device
 * Video to phones (also leads to flexible display of content)
 * Common principles:
 * Don't trap info in the formats
 * Common mappable vocabulary
 * Media repository (source at high resolution)
 * Easy to mashup interfaces and simple APIs
 * Common mappable vocabulary
 * Media repository (source at high resolution)
 * Easy to mashup interfaces and simple APIs
 * Support IMS CC, CP, clean XHTML
 * IMS Learning Tool Interoperability