After #OER18 and some initial research I believe the time is ripe for the #GoOpen movement to embrace basic standards and create documentation that encourages learning resources to be the plainest html possible.
Small HTML files are the most universal, the most accessible, and the least data costly. Shared standards are a #SocialJustice issue.
Also listening back to @opencontent #oer keynote comparing purists and pragmatists...The differences wouldn't matter if we had open standards. (my draft ideas: http://
Yet I also fear an "new wine old bottle" problem with emergence of #OER tools. Why are we building things only machines can read? If we continue down this route maybe some of Dave's darker questions come true. Again some simple standards around html markup and a community push can help ensure open stays open.
In doing research on the history of standards for marking up #OER html resources I am now beginning to think @oercommons is an "open silo" I can't access anything without signing, there is no documentation on how the resource builder works, and no library I can not access without sharing personal data
site says it is CC by-nc-sa but I see no link to any repo or code repository seems a resource is nothing more than an iframe
<div class="iframe-loading js-iframe-loading" title="100 People: A World Portrait"></div>
This is what I am exploring.
For academics in our spaces whose #GoOpen, #oer, #digped, #DOO, philosophies align with #indieweb principles would the tools like MicroPub and MicroSub and standards like webmentions not only make tracking the spread of our stuff, but more importantly encouraging the spread and spirit, without recreating another silo. Regardless of how open?
The OER Commons tools look promising and we would need stuff like that for most educators but I was trying to figure out what a DIY approach could look like as well.
I just joined @virtuallyconnecting at the #oer18 conference and I didn't have to get out my pajamas. Woke up to ice on this "Spring Break" day.
Here is a link to an early draft of a book on open pedagogy @wiobyrne and I will never finish: https://
Interoperability does have a legacy cost but if we put effort into our metadata and standards tools can be built like the oer commons resource builder and Google Docs importer to make easier on everyday people.
We can get there I am commenting on the #oer18 feed from my own website using #indieweb tools.
I get to own my data and decide where to share it.
Hey #oer18 is this the most current documentation on LRMI and A11y markup: https://
I also want to keep things as vanilla HTML/CSS as possible to make remixing easy