Page Comparison

...

"answer": "<p>This is test data</p>"

Multiple Choice Question:

Multi-select MCQ:

Proposed Solution

Here is the solution for diff types of the question.

Solution 1

Datatype: String

In this solution, All answers will be wrapped together under some HTML element and stamped to answer property.

answer: {
  en: "<div><p>Delhi</p></div>",
  hi: "<div><p>दिल्ली</p></div>"
}

answer: {
  en: "<div><p>Delhi</p></div>",
  hi: "<div><p>दिल्ली</p></div>"
}

answer: "<div>
          <p>Delhi</p>
          <p>Bangalore</p>
        </div>"

answer: {
  en: "<div><p>Delhi</p><p>Bangalore</p></div>",
  hi: "<div><p>दिल्ली</p><p>बैंगलोर</p></div>"
}

Pros:

• No QuML spec changes are needed.

Cons:

• Difficult to differentiate each answer for the player as it’s wrapped together under some HTML element.

• Some extra effort is required to support this format for both editor and the player.

• Data transformation is required for older questions.

Solution 2 (Recommended)

In this solution, Each answer will be stored separately as an element in an array.

Datatype: Array (An array of strings)

answer: {
  en: ["<p>Delhi</p>"]
  hi: ["<p>दिल्ली</p>"]
}

answer: {
  en: ["<p>Delhi</p>"]
  hi: ["<p>दिल्ली</p>"]
}

answer: [
  "<p>Delhi</p>, 
  "<p>Bangalore</p>"
]

answer: {
  en: ["<p>Delhi</p>","<p>Bangalore</p>"]
  hi: ["<p>दिल्ली</p>", "<p>बैंगलोर</p>"]
}

Pros:

• Easy to differentiate each answer for the player as it’s not wrapped together under some HTML element.

• Easy to manipulate UI by the player.

• Minimal changes are required by the editor and player.

Cons:

• QuML spec changes are required to support this format.

• Data transformation is required for older questions as it’s an array of strings.

interactions

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

...