The rise of the shareable document

Get the newsletter

Higher education is increasingly embracing different concepts of openness, from open access to open education resources (OER). But where does that other open concept—open source—fit into this model? Open source represents the best way to ensure these materials can be easily modified, without risk of material suddenly becoming unchangeable or inaccessible.

First, some quick definitions:

Open access is a mechanism for making scholarship publicly available to anyone, not just to users with subscriptions to scholarly journals and databases. This is achieved by publishing in open access journals, or by authors making copies of scholarship published in subscription journals available via institutional or disciplinary repositories.

Open education resources (OERs) are publicly accessible teaching and learning tools—anything from textbooks to slides to syllabi—that can be shared and even modified.

John L. Hilton III, Aaron Johnson, Jared Stein, and David Wiley have a model of openness that considers openness as a continuum. Using their model, openness minimally means access, or the ability to view something without needing some sort of credential. At the most permissive end of the openness spectrum, anyone has the ability to edit and remix content, changing it for their own purposes. Open access and OERs address the issues of access, but often fall short of addressing the issues of revising and remixing. For instance, many OER materials are shared as Word files and PDFs, which each present challenges in terms of modification of the work.

The default file format for Microsoft Word is .docx, which is a not entirely open format. Right now LibreOffice, an open source word processor, can open those kinds of files, but what if Microsoft does something to change that? The "open" content will only be available to users who have paid for some sort of Word license. Can that content really be considered be open?

This is where open source software becomes important in sharing content. Because the code is viewable, the files created by open source programs are always accessible. That means .odt files, the default LibreOffice word processing file format, are always open and modifiable. Even via other programs (including Word).

A PDF is viewable to anyone, but once you copy-and-paste text out of it, all formatting is lost. This isn't a big deal for a small chunk of text but can be a huge issue if you're trying to rework something large, like a textbook. That content can be considered open, but is it as open as it could be? What good is open content that's almost impossible to revise? Or in the case of open access scholarship, work that is difficult to quote in your own work?

Text files are open and modifiable, since just about every device has some sort of text editor. It represents a much more open, but also less popular, format for academic content.

This awareness of format is the next, necessary step in the shift toward opening scholarship and pedagogical tools. Academics have a strong handle on sharing, in a broad sense, but we need to move beyond file formats that aren't open or are difficult to modify. Open source software addresses this need. Part of the reason I wrote my book, Learn Linux in a Month of Lunches, was to teach academics how to thrive in an open source operating system, which would then make sharing and modifying work a much easier task. I spend a chapter on text editors and files because it's the most open and shareable of all file formats. In fact, it's the format that allows syllabi to be shared using GitHub.

Academics have come far in terms of sharing scholarship and teaching resources. But if we learn to share in ways that make content easier to work with, using open source software and open document formats, there could be an interesting domino effect, where more and more work is modified and shared. Access is a great thing, but let's not forget the importance of being able to easily modify work (as well as the platforms where the work resides), too.

Topics

About the author

Steven Ovadia - Steven Ovadia writes LinuxRig.com, which features The Linux Setup, interviews with desktop Linux users. He is an academic librarian who writes about how users interact with information in an online context for assorted Library Science journals. He is the author of Learn Linux in a Month of Lunches.

4 Comments

A bit offtopic. I read the first chapter of your book, that it's available for free. There you write about Linux, and his main developer Linus. Linux it's the kernel.

In the same chapter I coulnd't find anything about the person who developed the operative system, and wrote licenses to develop free software, yes I'm talking about Richard Stallman.
Maybe you could wrote that the name of whole system it's GNU with Linux, in short called Linux (I prefer GNU/Linux) but nothing about that...
If you are writing about the beginnin, I think that it's fair to talk about GNU project and free licenses used by Linux like GPL written by the FSF.

Unfortunately, I didn't have the space to explore the history of Linux and its licensing. However, if you're interested in that sort of thing, I recommend Decoding Liberation (http://www.sci.brooklyn.cuny.edu/~bcfoss/DL/), a fantastic book about the politics and economics of free and open source software. It's an incredible book.

For many years I have been "that guy using OpenOffice / LibreOffice" in a group of other people who use the main commercial suite. From this experience I can tell you that this has NEVER worked well. Partly it's because there are endless slightly incompatible versions of the main commercial suite, and because of that, it's probably impossible for OO or LO to work 100% successfully with any one of those. Share documents across two different languages and things get even worse (I get W*rd documents with Spanish style elements in them, next to their English language equivalents - that's just one example).

Couple this with the move from Arial, Tahoma, Times New Roman and other if-not-open-at-least-distributable fonts to Calibri & co that require a license of said office suite and things get even worse.

I wish I could convince my colleagues that we would all be better off working with OO/LO and then doing the .docx conversion at the last minute, for the client.

I could go on about this for a very long time but I'm going to stop now.

Footer

The opinions expressed on this website are those of each author, not of the author's employer or of Red Hat.

Opensource.com aspires to publish all content under a Creative Commons license but may not be able to do so in all cases. You are responsible for ensuring that you have the necessary permission to reuse any work on this site. Red Hat and the Shadowman logo are trademarks of Red Hat, Inc., registered in the United States and other countries.