A response to `Of OER and Platforms: Five Years Later`

Original post: https://opencontent.org/blog/archives/4892

I didn’t want this to get lost in the comments section but I found this post by David Wiley spot on, especially in his dissection of the LMS in the comments. As long as the LMS is still a dumping ground of stuff as opposed to a link farm out to innovation, it will never be innovation.

My response down in the comments, cleaned up to be a stand alone post:

Hollowing out the LMS is the only road they have towards innovation; if one of those common launch points was an OER provider that could be at least slightly more useful but I agree that when faculty treat their course as more of a website (via Paul Hibbitts GravCMS approach — http://www.hibbittsdesign.org/blog/) it’s the way forward.

Dr. Chuck is working on Tsugi to app-ify the LMS and unbundle it as well, which could make OER proliferation more possible at the system level. In this model, Sakai and other systems are effectively hollowed out *by design* via LTI launches, content item launches, and the items pulled in (innovations) are small decoupled stand alone applications —  https://www.tsugi.org/

I also have my own methodology in the game that sees the LMS fragmented (architecturally) so that policy can be crafted in a way that allows open aspects of course (content) to be open while closed experiences (private student – teacher engagements) can happen securely along side. We are building a self-federated ecosystem meaning any new part of the system can talk to any other new part of the system once it shows up. So we’re always able to account for the NextBigThing (n+1 thinking) in education or build new things the market hasn’t conceived. https://www.elmsln.org/

All three of these approaches are signs of the Next Generation Digital Learning Environment (NGDLE) which is NOT a product but a mindset and a way of implementing education online, which I think will directly result in greater adoption (or at least production as Open first) of OER. When systems are unbundle, ownership and privacy can be unbundled as well, leading to more robust, reusable solutions.

Speaking of unbundling, make sure to checkout OERSchema which ELMSLN seeks to use as a way of allowing Markdown Files (pure, portable, open by default) from Github to be able to populate and flush out content, interactions and more in ELMSLN (or any system).

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s