A slightly modified version of our paper for the ProLearn/iClass thematic workshop on Learning Objects in Context, "VWE: a framework for modularized Virtual Learning Environments - Applying the Learning Object Concept to the VLE", will be published in a special issue of the IJEL- International Journal on E-Learning.
The paper describes the Learning Object taxonomy that constitutes the basis for the Virtual Workspace Environment (yes, we deeply regret the badly chosen name, but the project started back in 1997, and well…;). The VWE Learning Object texonomy is based on Wileys’s idea of the Atomic Learning Object [.doc]. We have addes a new type of object: the Resource Object.
The Resource Object has one task and that is to support digital content objects (such as Simple (Fundamental) Learning Objects or Simple (Fundamental) Data Objects) to be rendered, used or interacted with. Hence, Resource Objects provides the application logics needed in Grouped Learning Objects. By separating application logics (one layer) from presentation (another layer) and data (a third layer) we can say goodbye to the type of Learning Objects that makes a mishmash of presentation, logics and data.
Resource Objects can be of two types: the Helper Resource Objects, which works as described above - much like a "plug-in" or "reader" for content - and the Creator Resource Objects, which adds functionality (application logics) which doesn’t need to be directly related to any content. Hence, it can add arbritrary functionality to the VLE!
This approach makes it possible to assemble a VLE from general modules, in the same fashion as we assemble content from "traditional" Learning Objects. Hence, we get a modularized VLE that is as flexible as our modularized content!
To support this component/object model for a VLE, we developed (it later turned out:) a Service Oriented Architecture (SOA). Exposing common functionality as services proved to be the best way to support this kind of modularity. However, back in 1997, when we started to develop VWE, Web Services where more or less unheard of. Instead we used CORBA and RMI to accomplish our mission: to build the first (at least to my knowledge) Service Oriented Architecture for Learning. Later, in 2001 we released a second prototype-framework based on Web Service technology (e.g. SOAP. WDSL etc.)
Assembling a VLE with the VWE-framework is quite similar to working with the LAMS system (We are currently looking in to IMS Learning Design for VWE). A teacher (or a student) chooses which components (content and functionality) they want to use in order to construct their new Learning Space (or as it is also refered to: Workspace). Parts of the Learning Space become personal and, other parts are shared with other users for collaboration and interaction. The process is handled with wizard-like Learning Space editors.
We basically wanted to put teachers and learners in control of the VLE by making the VLE adapt to different learning contexts as well as to different user preferences, methods for learning and pedagogical theories!
The figure below outlines the VWE Learning Object Taxonomy
I am currently working on two more VWE papers so expect more to come… in the meantime: read the ProLearn/iClass paper
