Ability
One of the Leap2A item types
<rdf:type rdf:resource="leap2:ability" /> or <rdf:type rdf:resource="http://terms.leapspecs.org/ability" />
| Definition: | EITHER: a general and impersonal definition of some area of knowledge, skill, competence or similar personal attribute, able to be used by anyone as a reference for a claim to possess the ability, or for a goal to achieve the ability, or as an intermediary for exploring pathways in education, employment or life OR: information about a self-defined and self-claimed ability |
| Examples: | |
| Literals used: | |
| Relationships used: |
|
| Categories: | |
| Can degrade to: / inherits from: |
entry |
| Notes: |
The main challenge with abilities is that they can be described in different levels of detail. Exactly the same applies to what are normally called "intended learning outcomes" and "competencies", which are essentially similar. The detail and definition of a description of ability can range all the way from the most vague, e.g.
through something more detailed, like
to something defined by its method of assessment
Ideally, abilities are handled as follows, which is the first case:
However, this first case does not make sense for abilities that are defined, claimed and evidenced by the holder. So we distinguish a second, self-defined case, where the ability entry contains the name (or very short definition) of the ability as the title, and the description of the ability, along with any claim or description of evidence, in the content. In this second case, the ability must be authored by the holder, which it will be by default if no author element is present. |
See also
- Leap2A/selection of type Abilities — there is potential for ambiguity here.
- early ideas on ability


