Versions Compared

Old Version 11

changes.mady.by.user Vaibhav Bhuva

Saved on

compared with

New Version 12

changes.mady.by.user Vaibhav Bhuva

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

(Note: Existing behavior of the player will be continuing as it is for the warning indicator)

Editor Changes:

  • Warning The warning timer will be removed from the editor form and editor will not save the warning time value in timeLimits.

  • min time will be stored inside timeLimits as timeLimits.questionset.min

  • There will not be any field for taking user input for min time, editor will store the min time as 0 by default.

...

Currently, maxScore property is getting stamped in two places at the question metadata level.

As per QuML spec, maxScore should be stored under the outcomeDeclaration property.

Current Format

New format as per QuML Spec

Code Block
languagejson
// Question metadata

{
  maxScore: 1,
  "responseDeclaration": {
    "response1": {
        "maxScore": 1,
        "cardinality": "multiple",
        "type": "integer",
        "correctResponse": {
            "value": [1,0],
            "outcomes": {
                "SCORE": 1
            }
        },
        .....
    }     
  } 
}
Code Block
{
  "outcomeDeclaration": {
    "maxScore": {
      "cardinality": "single",
      "type": "integer",
      "defaultValue": 1
    }
  }
}

...

In the current implementation, We are not storing the answer property for MCQ and MMCQ. but as per QuML spec, An answer is mandatory for all types of questions.

  • SA – HTML

  • MCQ/MMCQ – reference value for data OR actual value ?
    For example: “1,2” OR empty string “India, US”
    (Need to be checked with Sajesh Kayyath and Gauraw Kumar

...

Current Format

New format as per QuML Spec

Not Applicable

Code Block
languagejson
"answer": "1" // Value assign for data
OR
"answer": "indiaIndia" // actual value.

Multi-select MCQ:

Current Format

New format as per QuML Spec

Not Applicable

Code Block
languagejson
"answer": "1India,2 US" // Value assign for data
OR
"answer": "India, US" // actual value.

...

actual value.

interactions

As part of the new implementation, We will be moving only the validation field under the response1 property. No other change.

...

Current Format

New format as per QuML Spec

Code Block
languagejson
"solutions": [
    {
        "id": "70c82bf5-9459-4c43-8897-0e58b7e1da62",
        "type": "video",
        "value": "do_2137930190247526401388"
    }
]
Code Block
languagejson
"solutions": {
    "70c82bf5-9459-4c43-8897-0e58b7e1da62": "<video  width="400" #solutionVideoPlayer controls poster="https://dev.inquiry.sunbird.org"><source type="video/mp4" src="https://dev.inquiry.sunbird.org/assets/public/content/assets/do_2137930190247526401388/earth.mp4"><source type="video/webm" src="https://dev.inquiry.sunbird.org/assets/public/content/assets/do_2137930190247526401388/earth.mp4"></video>",
}



// Key = UUID

  • Solutions is a JSON object in key-value format. The keys in the JSON are the identifiers of different solutions for the question and values are HTML snippets for solutions.

  • Solutions HTML must contain only structural and media HTML elements. There should be interactions in a solution and hence no input HTML elements. QuML players should allow the users to view the solutions if the context in which the question is being used allows the users to view the solution.


feedback

Feedback is a JSON object in key-value format. The keys in the JSON are the identifiers of different feedbacks for the question and values are HTML snippet to be shown to the student. After the response processing, the QuML player renders the feedback HTML mapped to the value that is set to the FEEDBACK outcome variable.

...

Current Format

New format as per QuML Spec

Code Block
languagejson
// Not applicable
Code Block
languagejson
“feedback”: {
  “70c82bf5-9459-4c43-8897-0e58b7e1da62”: “<h1>Well done!!!</h1>”,
  “70c82bf5-9459-4c43-8897-0e58b7e1da63”: “<h1>Better luck next time!!!</h1>”
  “70c82bf5-9459-4c43-8897-0e58b7e1da64”: “<h1>You need to work harder!!!</h1>”
}

// key = UUID

For more information, please refer to this document: https://quml.sunbird.org/v1/question#feedback

hints (This has to be modified by an adopter)

...

Current Format

New format as per QuML Spec

Code Block
languagejson
// Question Metadata
{ 
  hints: { 
    en : "string"
  }
}
Code Block
languagejson
“hints”: {
  “70c82bf5-9459-4c43-8897-0e58b7e1da62”: “<HTML>...</HTML>”,
  “70c82bf5-9459-4c43-8897-0e58b7e1da63”: “<HTML>...</HTML>”
  “70c82bf5-9459-4c43-8897-0e58b7e1da64”: “<HTML>...</HTML>”
}

// key = UUID

Hints is a JSON object in key-value format. The keys in the JSON are the identifiers of different hints for the question and values are HTML snippet for hints.

For more information, please refer to this documentation: https://quml.sunbird.org/v1/question#hints

...

Currently, instructions are being stored in the following format:

For QuestionSet:

Current Format

New format as per QuML Spec

Code Block
languagejson
{ 
  instructions: { 
    default : "<html>...</html>"
  }
}
Code Block
languagejson
instructions:  : "<html>"

For Question:

Current Format

New format as per QuML Spec

Code Block
languagejson
{ 
  instructions: { 
    en : "<html>...</html>"
  }
}

//Only Shikshalokam is using the above format.
// Not used by inQuiry
Code Block
languagejson
instructions:  : "<html>"

...