Remove Multiple Competence Assignements to single Question

1 Reasons to Abandon Feature

To discriminate properly every item should measure exactly one competence. This is hard enough, few test questions authors can do it. Professional, high stakes exam providers do it. 
However ILIAS is too flexible and thus too complex: Tests allow assigning competences to sub-question entities. This leads to A) bad measuredment and B) unwanted code complexity. 
This should go. 

2 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

3 Contact

• Author of the Request: Tödt, Alexandra [atoedt]
• Maintainer:Heyser, Björn [bheyser]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

4 Funding

Removing the feature from the ILIAS code base might need funding. If you are interest in funding this request, please add your name and institution to this list.

• ...

5 Discussion

Use the following discussion section to express your objections against this request or your consent to get rid of this feature.

Jackisch, Ingo [jackisch] since competencies add an abstraction layer to test questions I dont agree that a single question will always adress a single competency. I dont see a need that a special sub-part of a questioin needs to be matched exactly to a competency, but the question as a whole shold be able to trigger several competencies (like: If you solve this question correctly, you proved competencies for handling terms and for dealing with logarithms etc.)
If tests which have a limited number of questions are to adress several competencies, it would be even harder to achieve the quorum if every question may only adress a single competency.

6 Implementation

{The maintainer has to give a description of the final implementation and possible consequences for existing installations.}

Approval

Approved at {date} by {user}.