![]() |
|
![]() |
![]() |
![]() |
Mirror, Mirror: Refining the Element in the IMS e-Portfolio SpecificationCreated by Catherine Howell (La Trobe University) on May 24, 2006
The e-portfolio community would agree that reflection is a key part of learning, and by association, a key activity for owners of e-portfolios. The IMS e-portfolio specification includes a special <reflexion> element, designed to highlight this and separate it from other e-portfolio elements. But the distinction between reflexion and other e-portfolio elements in the IMS spec (notably, <assertion>) remains unclear, and this has the potential to affect the way that we understand and interpret identity, ownership, and activity in relation to e-portfolios. Pondering this, Scott Wilson asks: At what level of description is the distinction between reflexion (aka self-asserted statements) and assertion (aka reputation or other-asserted statements) useful? Good question. The relevant bit of the IMS ePortfolio Best Practice Guide seems to be 3.1.7: Using Core Data Structures: Assertion / Reflexion. To the authors' credit, they've had a stab at defining reflection, but I find their definition insufficient because it raises questions similar to Scott's. The wording in 3.1.7 seems to me to mirror some slightly fuzzy thinking about the nature and role of reflection in e-portfolios. And the actual example of reflexion (XML format) given is alarmingly simplistic: <lip:description> <lip:short>My Thoughts on the essay</lip:short> - <lip:long> Could be improved with discussion of relationship with Norse Culture </lip:long> </lip:description> Am I the only one who finds this funny -- kind of? Back to the IMS <reflexion> element. It seems clear that reflection is both an "activity" and an "item" (or "product"). <Assertion> is linked to <reflexion> because, as part of a reflective activity, a learner may make a connection between items (between ideas, objects, or persons) -- asserting that a relationship exists between them. So, where does reflection come in? Reflection, I would suggest, is the argument that backs up the assertion -- it is semantic, as well as syntactic. A reflective "argument" can take the form of evidence supplied by the learner, or it can take the form of an interpretation, an attribution of meaning. The phenomenon of hyperlinking has meant that the distinction between semantics and syntax, reflexion and assertion, has blurred. The act of creating a hyperlink (on the Web, or in an e-portfolio) is widely intended and interpreted as a functional argument: it encompasses both the assertion of a relationship and, at the same time, the supplying of evidence. Sometimes, as Scott suggests, assertion operates in the same space as reputation (how I perceive others, and how others perceive me). <Assertion> therefore has a social element. But not always: <assertion> may also operate as part of a private reflection -- which the learner may choose to expose to others, thereby shifting something private / personal into the arena of the public / social. Reflective activity in e-portfolios has to mean more than filling in a form-field titled "Reflection" (this is a problem with the current iteration of OSP). Reflective activity is complex and involves several levels of thought and activity on the part of the learner. We can point to educational theoretical models like Kolb's learning cycle act as the underpinning rationale and research basis for believing the reflection is relevant and important to learning. However, Kolb et. al. -- and, significantly, the now-familiar language of "folio thinking" and the e-portfolio community in general -- seem to emphasise "right-brain" thinking (holistic, visuospatial, emotive) over "left-brain" (verbal, linear, analytic). This seems to me, at least potentially, to create a top-level pedagogical problem and, taking different learning styles into account, to neglect a major group of learners and, by extension, owners of e-portfolios. The planned integration of VUE into Sakai seems, to my mind, to be a product of the current "left-brain bias" of folio thinking. I say this without wishing to disparage the use of visual tools or concept maps, which are particularly suitable for dyslexic students; and I am also very happy that visual tools are being gradually introduced into Sakai's very hierarchical, folder-centric information structure. My overall point is that our understandings and definitions of reflection have to address the reality of adaptability, switching, and unpredictability in learner preferences and learner behaviour. And they have to provide for future developments and refinements in neuropsychological / sociological understanding of learning, and consequent educational models.
|
![]() |
|
| Unless otherwise noted, EDUCAUSE holds the copyright on all materials published by the association, whether in print or electronic form. In certain cases the work remains the intellectual property of the individual author(s) (see Special Circumstances). Content from conference speeches, presentations, blogs, wikis and feeds reflect the opinions of the author, and not necessarily those of EDUCAUSE or its members. | |||
I agree that the distinction between assertion and reflexion is ambiguous and arguably unnecessary. It is an artifact of attempting to align the IMS spec with the yet-to-be-released BSI 8788/UKLeaP. Note, though, that the reflexion element name is spelled with an "x" in part of distinguish it from the obviously more extensive process of reflection. I would have preferred not naming leaving the word "reflection" out of the normative spec altogether to avoid the confusion you're in. I think you'd be hard pressed to find anyone who disagrees that reflection is a more complex than the means we have to capture it. As it's likely there will be a revision of the specification in the next 12-18 months, I encourage you to log this as an issue on the IMS site and propose ideas for a richer representation of reflection. Your last paragraph strikes me as more interesting. I'm not sure I understand your association of concept mapping with "left-brain" thinking. Aren't such maps much more "holitic" and "visuospatial" than any of the alternative ways of organizing portfolios? My experience working with students building portfolios using tools like CMap certainly point towards concept mapping as a powerful means for engaging non-linear, visual, integrative thinking. What would be a better direction for OSP/Sakai?