Practical Interop For OPDF Developers - Nov 2009
•Download as PPT, PDF•
1 like•934 views
short presentation for OPDF fund recipients that tries to explain why simply developing within an LMS and exporting is NOT sufficient to provide shareable resources, and some suggestions on better approaches
![Overview ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (17)
Similar to Practical Interop For OPDF Developers - Nov 2009
Similar to Practical Interop For OPDF Developers - Nov 2009 (20)
Recently uploaded
Recently uploaded (20)
Practical Interop For OPDF Developers - Nov 2009
- 1. Practical Interoperability for OPDF Recipients Scott Leslie, BCcampus November 12, 2009
- 8. The Ideal Shared OPDF-Funded Content Instructor / Instructional Developer Trying to Reuse Content
- 10. Scenario 1 – Moodle
- 11. Scenario 1 – WebCT/BB
- 12. Scenario 1 – D2L
- 13. Scenario 2 - Education-specific standards IMS Content Package HARD TO DO
- 14. Scenario 3 - Web-specific standards HTML / Flash / PDF EASIER TO DO
- 15. Scenario 4 – Develop out in the Open HTML / Flash / PDF
- 17. Suggested File Formats Note on PDFs and Word Docs: PDFs aren’t a particularly web-friendly, data-friendly or re-use friendly format. Unless there is no other choice, efforts should be made to avoid PDF (and other proprietary document formats like Word .doc) in favour of native web pages and document transfer formats like RTF Asset Type Suggestion Images Ideally PNG (though GIF/JPEG still fine) Text and Web Pages HTML 4.01 (but ALL presentation in CSS) Video MPEG4 Rich Media Applications Flash Quizzes and Tests Ideally IMS QTI format, but separate text doc with questions/answer keys also helpful
Editor's Notes
- Images The preferred format for images is the PNG format (cf. http://en.wikipedia.org/wiki/Portable_Network_Graphics ) though because of their ubiquity in support throughout browsers and other devices, use of Gifs or JPEGs is not unreasonable. Text and Web Pages Where possible, text and other content shuld be provided in the form of web pages written to confirm to the XHTML 1.1 standard ( http://www.w3.org/TR/xhtml11/ ). Efforts should be made to place styling information in separate linked style sheets. A Note on PDFs PDFs aren’t a particularly web-friendly, data-friendly or re-use friendly format. Unless there is no other choice, efforts should be made to avoid PDF (and other proprietary document formats like Word .doc) in favour of native web pages and document transfer formats like RTF. Videos Videos ideally would be MPEG-4 encoded. While Flash video is widely supported on browsers and provides compact file sizes, it does not work on all mobile devices, so use your judgment accordingly. Rich Media Applications Typically Flash is the format of choice here, and while it is not supported on all mobile devices, it is widely supported on most desktop browsers. When sharing the resulting Flash resources, ideally the .fla file and individual media assets that went into the resource would be bundled with the .swf asset in a zip file, though this is seen as an ideal, not necessarily optimal, solution. Quizzes and Tests Ideally, Quiz and Test data will be shared both in IMS QTI format ( http://www.imsglobal.org/question/ ) and as a simple RTF file. Quiz and test data for formal final assessment (e.g. not self-administered quizzes) should ideally be shared as Objects separate from other material, which will enable us to restrict access to these specifically in the event we need to.
- show example of IMS Content Package and standalone website. bulk uploads