- My eBooks Loading ...
Track details: - -
Buy this album
About Stephen Downes
About Stephen's Web
Subscribe to Newsletters
Privacy and Security Policy
Web - Today's OLDaily
Web - This Week's OLWeekly
Email - Subscribe
RSS - Individual Posts
RSS - Combined version
JSON - OLDaily
Stephen's Web and OLDaily
Half an Hour Blog
Google Plus Page
Huffington Post Blog
National Research Council Canada
Research Topics, Research Wiki, Code
All My Articles
What is a Learning Context?
I would question this statement: "But, what is a learning context? We define a context (for learning objects) as “the ability for a learning object to interconnect various, similar events or statements.” This would be as Ackoff might have defined it. "
I do not believe, for various reasons, that a 'context' is a property of an object, and 'the ability to connect...' is a property of an object. If pressed to define 'context' (and IMHO definitions by their very nature are imprecise) I would say something like 'the set of objects, including their functions and relations, that could be detected or accessed by an object'. Please note the counterfactual nature of this definition: if an object is blind and dumb, it does not follow that it does not exist within a context, only that the context is inaccessible to the object.
Contexts are typically defined (reasonably, but still IMHO) from the perspective of the user, or in our case, the learner. I sometimes talk of the context as being the learner's environment, and online, the digital environment. If we want to be complete, we can talk about three major environments: the learner's external environment (classroom, working space, in-person coaches, etc.), internal environment (previous beliefs, thoughts, hopes, etc) and digital environment.
But this is all a bit throw-away, just a taxonomy. What is correct in the initial statement is the focus on the capacity to interact, whether that interaction occurs directly (object to object) or indirectly (object to learner to object). This context has the properties of an environment, a space, a room, and may be treated as an object in its own right. Objects in a context are 'placed' in a context, that is, by one means or another, they stand in the relation of being 'contained in' the space ('contained in' is a virtual relation - the objects themselves may be physically remote, not visible, nor not in any real sense 'contained' by the context; their being 'contained' is made so by their being declared to be so, and requries only that they be (potentially) accessible from within the space.
'Object oriented', in this context, means that the horse and the palm tree have properties in common, derived from ('inherited') by virtue of their being certain types of objects, such that interaction with both the palm tree and the horse can be accomplished in the same way ('look at', for example, or 'speak to'). Such interaction will (typically) reveal the properties of the object ('you see: a horse') or invoke functions in the objects. This capacity, importantly, is enjoyed by objects among each other; the horse (potentially) can 'see' the tree, or 'speak to' the tree, and hence, the objects interact with their context.
"We need a new metaphor, which we suggest as “organic, ecological ‘legos,’ capable of inter-communication amongst themselves [c.f. 10], capable of receiving (validated) inputs from the producers of knowledge and understanding, and which any instructor, educator, learner, or any other informer can employ to convey a message that enhances the learner’s ability to achieve outcomes and immerse him/her self into a culture or cultures." Exactly. But delete the word 'legos' - think more of the horse and the palm.
"More importantly, we insist that the formal language related to object engineering, and, an extension of this language be always, somewhere part of the record."
Well - yes - but how? We don't even have a common means of creating what you would call 'elemental objects', much less embodying common properties. I think that a common XML definition of 'learning resources' is an important first step - not the metadata, but the resources themselves. From this common framework we can begin to embed logical contructs that allow objects to inherit functionality from base models (I don't like the word 'class' - inheritance and inherited functionality has to be technology neutral, expressed in XML and not (say) Java).