Talk:Workgroup:Technology policy

From WikiEducator
Jump to: navigation, search


Thread titleRepliesLast modified
Technology-related discussions012:37, 23 December 2009
Multimedia021:31, 13 November 2009
OER content interoperability between Connexions and the Mediawiki101:16, 1 August 2009

Technology-related discussions

Edited by another user.
Last edit: 12:37, 23 December 2009

Every now and then technology-relevant discussions come up on the general WE mailing list. Might be useful to keep a record of when this happens for future reference, and indicate what policy issues are raised. E.g.

Ktucker (talk)11:29, 23 December 2009


Currently, libre knowledge (and free software) purists have trouble viewing video resources on WikiEducator. For this policy it would be good to consolidate previous discussion and decide how best to proceed.

For future reference for discussions on this topic, some links (please add):


  1. What alternatives are there to embedding YouTube videos in pages? (preferably serving free file format videos)
  2. ...
KTucker (talk)21:31, 13 November 2009

OER content interoperability between Connexions and the Mediawiki

What approaches could be considered (for due diligence and basis for rationale)?

First note that WE (CC BY SA) can include and derive cnx resources (CC BY) but not the other way round.

  1. Migrate WE to the cnx platform (Rhaptos).
    • Pros
      • enable WE with a host of features already available in Connexions such as
        • custom workflows (e.g. in sub-trees of resources, ...)
        • semantic tagging and search
        • please add
    • Cons
      • Labour intensive, so will need careful community process design
      • Migrating MediaWiki templates may be tricky ??
  2. Work with the underlying XML representation in Connexions and transform for WE (XSLT, etc.)
  3. Focus on IMS content export/import (and/or SCORM)
    • Pros
      • This approach services other platforms which support IMS ...
  4. Please add.
KTucker (talk)11:25, 28 July 2009

Hi Kim good thinking as always :-)

  • Very aware of the licensing issues ;-)--- WE support's both CC-BY and CC-BY-SA licensing (as we subscribe to the free cultural works definition.) That said -- I think that once we have the technology sorted, we can resolve the licensing -- even if it means a separate "Connexions" install for CC-BY-SA content.
  • Another advantage of a connexions export for MW is the ability to host a static instance of WE course content.
  • Yip -- the export of MW templates can be tricky -- in the case of WE we will focus on the most widely used pedagogical templates. Using the collections extension we can whitelist, for example navigation templates or infact consider Connexions specific behaviours for MW templates.
  • At this stage our thinking is to remain with the CNXML framework rather that trying to invent a new XML representation. Further transformations and manipulations down the track are not excluded. Candidly -- its easier to get Connexions content into MW than the other way around.
  • We have already developed a proof of concept web-service for exporting IMS content packages / cartridges from WE. So if we get additional funding we can do this. Having worked with IMS/SCORM exports / imports in LMS, I'm not too impressed with their implementations. Basically -- in most LMSs the IMS/SCORM imports look less elegant and functional than content authored within their own systems. I wonder why????

Cheers Wayne

Mackiwg (talk)01:16, 1 August 2009