The pragmatics of InLOC competence logic

Putting together a good interoperability specification is hard, and especially so for competence. I’ve tried to work into InLOC as many of the considerations in this Logic of Competence series as I could, but these are all limited by the scope of a pragmatically plausible goal. My hypothesis is that it’s not possible to have a spec that is at the same time both technically simple and flexible, and intuitively understandable to domain practitioners.

Here I’ll write now about why I believe that, and later follow on to finalise on the pragmatics of the logic of competence as represented by InLOC.

Doing a specification like InLOC gives one an opportunity to attract all kinds of criticism from people, much of it constructive. No attempts to do such a spec in the past have been great successes, and one wonders why that is. Some of the criticism I have heard has helped me to formulate the hypothesis above, and I’ll try to explain my reasoning here.

Turn the hypothesis on its head. What would make it possible to have a spec that is technically simple, and at the same time intuitively understandable to domain practitioners? Fairly obviously, there would have to be a close correspondence between the objects of the domain of expertise, and the constructs of the specification.

For each reader, there may appear to be a simple solution. Skills, competences, learning outcomes, etc., have this structure — don’t they? — and so one just has to reproduce that structure in the information model to get a workable interoperability spec that is intuitively understandable to people — well, like me. Well, “not”, as people now say as a one-word sentence.

Actually, there is great diversity in the ways people conceive of and structure learning outcomes, competences and the like. Some structures have different levels of the same competence, others do not. Some competences are defined in a binary fashion, that allows one to say “yes” or “no” to whether people have that competence; other competences are defined in a way that allows people to be ranked in order of that competence. Some competence structures are quite vague, with what look like a few labels that give an indication of the kinds of quality that someone is looking for, without defining what exactly those labels mean. Some structures — particularly level frameworks like the EQF — are deliberately defined in generic terms that can apply across a wide range of areas of knowledge and skill. And so on.

This should really be no surprise, because it is clear from many people’s work (e.g. my PhD thesis) that different people simplify complex structures in their own different ways, to suit their own purposes, and in line with their own backgrounds and assumptions. There is, simply, no way in which all these different approaches to defining and structuring competence can be represented in a way that will make intuitive sense to everyone.

What one can do is to provide a relatively simple abstract representation that can cover all kinds of existing structures. This is just what InLOC is aiming to do, but up to now we haven’t been quite clear enough about that. To get to something that is intuitive for domain practitioners, one needs to rely on tools being built that reflect, in the user interface, the language and assumptions of that particular group of practitioners. The focus for the “direct” use of the spec then clearly shifts onto developers. What, I suggest, developers need is a specification adapted to their needs — to build those interfaces for domain practitioners. The main requirements of this seem to me to be that the spec:

gives enough structure so that developers can map any competence structure into that format;

So when you look at the draft InLOC CWAs, or even better if you come to the InLOC dissemination event in Brussels on 16th April, you know what to expect, and you know the aims against which to evaluate InLOC. InLOC offers no magic wand to bring together incompatible views of diverse learning outcome and competence structures. But it does offer a relatively simple technical solution, that allows developers who have little understanding of competence domains to develop tools that really do match the intuitions of various domain practitioners.

Three InLOC drafts for CEN Workshop Agreements are currently out for public comment — links from the InLOC home page — please do comment if you possibly can, and please consider coming to our dissemination event in Brussels, April 16th.