Background
We have received the MTF Question contribution in the C4GT 2023 program for the editor and the code is merged only in one of the feature branch.
Player side implementation is not done yet, before starting the player implementation we need to re-look into the MTF data model if it’s as per the QuML spec and if any improvement can be done in it to make it easy to understand.
Data Model of MTF Question
body
<div class='question-body' tabindex='-1'> <div class='mtf-title' tabindex='0'> <p>Match the colour with the fruits.</p> </div> <div data-match-interaction='response1' class='mtf-horizontal'></div> </div>
Question is body is per the QuML spec
responseDeclaration
{ "response1": { "cardinality": "multiple", "type": "map", "correctResponse": { "value": [ { "0": 0 }, { "1": 1 }, { "2": 2 }, { "3": 3 } ] }, "mapping": [ { "value": { "0": 0 }, "score": 0.25 }, { "value": { "1": 1 }, "score": 0.25 }, { "value": { "2": 2 }, "score": 0.25 }, { "value": { "3": 3 }, "score": 0.25 } ] } }
responseDeclaration is as per the QuML spec
But above format of responseDeclaration it not self explanatory
Here are few new proposed Format for responseDeclaration
Cardinality for MTF Question should be "cardinality": "ordered"
Format1
Format2
Since the value in lhs/rhs or leftIndex/rightIndex are index of the options, Format2 seems to make more sense.
Final Format of responseDeclaration: ?
outcomeDeclaration
{ "maxScore": { "cardinality": "ordered", "type": "integer", "defaultValue": 1 } }
For more info on outcomeDeclarartion - refer , reference2
interactions
{ "response1": { "type": "match", "options": { "left": [ { "label": "<p>Red</p>", "value": 0 }, { "label": "<p>Yellow</p>", "value": 1 }, { "label": "<p>Green</p>", "value": 2 }, { "label": "<p>Orange</p>", "value": 3 } ], "right": [ { "label": "<p>Apple</p>", "value": 0 }, { "label": "<p>Banana</p>", "value": 1 }, { "label": "<p>Grapes</p>", "value": 2 }, { "label": "<p>Orange</p>", "value": 3 } ] }, "validation": { "required": "Yes" } } }
Question interactions is of type object so it is as per the QuML spec
editorState
editorState Stores editor specific data.
templateId
"templateId": "mtf-horizontal" / "mtf-vertical"
primaryCategory
"primaryCategory": "Match The Following Question"
qType
"qType": "MTF"
interactionTypes
"interactionTypes": ["match"]
Add Comment