David Davies' Weblog
GMail me at 'daviesda(at)gmail.com' obviously replacing the (at) with @ first - I don't want to fill up my new account with spam just yet ;)
There is much to discuss about what weblogging means, in all its forms, which is entirely reasonable because thoughtful people are continuously discussing all forms of media. My daughter has just enrolled on a media studies course and her first assignment was to discuss a particular genre of movies and how they affect people. But we understand movies, right, 'cos they've been around a long time? Wrong. There are always new interpretations and ways of using all forms of media, and when new media arise, and there's an interesting debate to be had on whether weblogs represent a new form of media, the debate moves on in exciting new directions. So it's important to debate what weblogs and moblogs are, but don't expect a consensus because they're different for different people. Always will be. But isn't that the fun bit?
I have a claim to stake in the history of moblogging. I had a moblog before any of you. My SMS blog was the first moblog and it continues to this day. It was so new there wasn't even a generic name for what the weblog was trying to do. Dave grokked what I was trying to do way back. I posted pictures and video to my moblog before most of you even had mobile phones. And I'll state right now that I was only able to what I did by using the software that Dave and the Userland team created. I've always tried to be fair to that.
But just for the record, and to show it is pointless claiming to be the first at anything, I wasn't actually the first person to have a moblog. Not by a long way. You see that's the problem with definitions. Anyone remember this guy? Steve Mann was wearing mobile computers back in 1980 and was later posting images taken from his devices back to the Internet (see wearcam.org). And I don't even think that Steve was the first to go on the road with a wearable computer. I recall seeing pictures of a guy on a bike with an even more ungainly mobile computer from the '70's but I can't find a link anywhere. Neither of these guys called what they did moblogging. Would you? Discuss.
The problem with definitions - or how I learned to get over learning objects and start making good e-learning instead
Perhaps LOs are only meaningful to educational technologists or the people who write the software to manipulate these data. The end user, the teacher let's say, doesn't really care what you call the parts, they just want to achieve a specific end point, creating a PowerPoint file or creating some e-learning for example. Learning the names of all the parts often just gets in the way. That's why users don't read software manuals, because good software should be unambiguous and as intuitive as possible. Who cares if you guys can't agree what a learning object is, I just want to create something I can use to teach my students. I've heard words to that effect many times when talking to colleagues. It's a bit like, well at a stretch any way, whether or not to use HTML tables or CSS to structure your web pages. How many people care about that? Sure, they care about the output, how well a web page works in different web browsers, but probably for most people they just trust that the folk who make the web page editing software will sort that out and just give the user the best solution. Same with LOs in my opinion.
So now when I'm in a meeting with my fellow academics and learning objects crop up in the discussion, I just say they're bits of reusable e-learning material and everyone gets it and we quickly move on to talking about the really interesting stuff. Like how to create really effective e-learning materials.
Enough about learning objects for the time being. So now, who's going to add metadata to my learning objects... ;)
Here's how I tend to think about learning objects. Learning objects are the data contained within content packages. Pretty specific but it works for me and here's why. When I talk about e-learning materials I think of three classes of data (see figure).
Raw assets often though not always exist outside of a specific learning context, that is to say whatever context they do have is usually inherent in the asset. For example in an x-ray of the chest the context is the data contained within the x-ray itself, the pixels of the x-ray. It is the act of adding context by creating metadata (context for how the asset relates other data including a learning outcome for instance), and assembling raw assets into larger aggregations (e.g. adding a text narrative to an x-ray) that creates a meaningful piece of learning material. Ironically in this scheme it's raw assets that are the building blocks of learning materials rather than in previous analogies where learning objects have been likened to, for example, Lego bricks. Raw assets are given a learning context and assembled, or aggregated to use the common parlance into learning objects, the stuff learners use to learn from. Learning objects get moved around between learning environments as content packages.
At one extreme, most people are fairly comfortable with what constitutes a raw asset (itself an assembly of data, pixels in an image for example but that's taking too reductionist an approach) and at the other extreme content packages are well understood, not least because there are specifications that describe what they are and how they're structured. Between these two lie the learning objects. Sometimes it's difficult to conceptualize learning objects if you've never worked with tools that make it completely unambiguous what they are. There are tools available that understand this simple metaphor and function well to create one class of data from the other (for recommendations of what I think are the best tools get in touch). Perhaps my particular way of looking at this problem will be more familiar to people who are used to learning content management systems and are therefore comfortable with the progression of complexity from raw asset to content package. Others may find this approach too simplistic and instead prefer to think of the increase in contextualization from raw asset to context package. Either way it amounts to just about the same thing. But perhaps there's one of the underlying problems with the way people think about learning objects. There is sometimes an uneasy overlap in ways in which educationalists looks at e-learning materials and the way education technologists do. What works as an analogy for some doesn't always work for others.
But of this there can be no doubt, the materials or 'objects' that sit midway within the opposing continua of organisation and reusability are the learning objects. If we don't like the name then let's find another, but the space remains.