QTI implementation restrictions and assumptions
Restrictions
//item/resprocessing/outcomes/decvar
- Only the variable named "SCORE" is allowed. Reason: we can thus
omit all the complicated map_input, map_output, ... in Element section.
Restrictions by being bound to 'SCORE' can be solved by putting items
in
questions and do a outcomes_processing on the assessment.
//item/resprocessing/respcondition
- Only one displayfeedback is evaluated
//section
- Only "sumofscores" and "number_correct" scoring models are
supported.
- Only first outcomes_processing evaluated.
- Sections within sections are ignored.
//section/outcomes_processing
- Only outcomes_feedback_test is evaluated, other elements are
ignored.
//section/outcomes_processing/outcomes_feedback_test
- Only 1 displayfeedback evaluated.
//presentation
- On /material tags: Only /matimage, /matvideo, /mattext and
/matemtext are
processed. It is possible to put HTML tags within those tags.
- /matimage@uri is relative to the root of the IMS Content Package
from which the IMS XML comes from.
Assumptions
//item/itemfeedback
- The solution, hint children are used for rendering only. (*1) the
type of feedback is determined by
item/resprocessing/respcondition/displayfeedback
- - *1: since <displayfeedback feedbacktype = "Solution" does
not make sense if you also want to have hints, we added a button,
which,
when clicked by the user, presents the solution
- Only one hintlevel is saved per item, that is, it is assumed that
only one resprocessing/respcondition triggers hints
- @feedbackstyle makes only sense for element <hint>.
- hint@feedbackstyle: Only "Incremental" is supported.
//section
- At least one item in a section.