Proposed QuML Spec Changes

Background:
We have identified some gaps between QuML Spec (v1) and inquiry implementation (api, service & player). In order to make inquiry QuML compliant we need to modify the schema at the inquiry api, editor, player and add/update few items in the spec as well.

Spec Changes for Question:

Attribute Name: answer

answer is needed for non interactive question.

Current QuML spec (v1): Not Available

Proposed QuML spec (v1.1):

answer also should support multi-lingual data similar to body.

"answer": {
    "description": "answer contains the text, graphics, media objects that describe the question’s content.",
    "oneOf": [
      {
        "type": "string",
        "description": "Answer as HTML string when the answer is used in only one language."
      },
      {
        "$ref": "#/definitions/i18nData"
      }
    ]
  }

Sample Data for QuML (V1.1):


"answer": "<p><span style=\"background-color:#ffffff;color:#202124;\">The challenges faced by India after independence were Partition led to arrival of 8 million people to India from Pakistan for whom homes and jobs had to be found. 500 princely states, each of which was ruled by a maharaja or a nawab, had to be convinced to join the new nation. Also, in the long run, the new nation had to adopt a political system which would best serve the hopes and expectations of its population.</span></p>"

OR

"answer":{
  "en": "<p><span style=\"background-color:#ffffff;color:#202124;\">The challenges faced by India after independence were Partition led to arrival of 8 million people to India from Pakistan for whom homes and jobs had to be found. 500 princely states, each of which was ruled by a maharaja or a nawab, had to be convinced to join the new nation. Also, in the long run, the new nation had to adopt a political system which would best serve the hopes and expectations of its population.</span></p>"
}

Attribute Name: interactionTypes

need to be added for interactive questions.
Ref: Question Definition

Current QuML spec (v1): Not Available

Proposed QuML spec (v1.1):

"interactionTypes": {
    "description": "interactionTypes contains the kind of interaction a interactive question can have",
    "type": "array",
    "items": {
      "type": "string",
      "enum": [
        "choice",
        "text",
        "select",
        "date",
        "file-upload",
        "canvas"
      ]
    }
  }

Sample Data:

Attribute Name: media

spec need to be updated based on discussion (ref: [Design] - Making Question Set Editor and QuML Player QuML Compliant )

Current QuML spec (v1):

Proposed QuML spec (v1.1):

Sample Data for QuML(V 1.1):

Attribute Name: responseDeclaration.mapping

the mapping spec need to be updated.

Current QuML spec (v1):

Proposed QuML spec (v1.1):

Sample Data for QuML (v1.1):

Attribute Name: interactions

In Case of multiple interaction types (e.g: choice & text), the implementation can have multiple variables for each interaction types (e.g: response1 for choice and response2 for text)

Current QuML spec (v1):

Proposed QuML spec (v1.1):

Open Questions:
1. Do we always have options array for all different types of interactions like date, select, canvas, file-upload?

Attribute Name: solutions

Current Solutions Spec is not covering internal data structure.

Current QuML spec (v1):

Sample Data for Quml Spec (1.0):

Proposed QuML spec (v1.1):

Sample Data for QuML Spec (v1.1):

Attribute Name: bloomsLevel

Data type mismatch found between spec json and wiki page.
QuML/v1/question-schema.json at master · sunbird-specs/QuML
Question Definition

Current QuML spec (v1):

Proposed QuML spec (v1.1):

Attribute Name: feedback
Current QuML spec (v1):

Sample Data for QuML (v1.0):

Proposed QuML spec (v1.1):

Sample Data for QuML (v1.1):

Attribute Name: hints
Current QuML spec (v1):

Sample Data for QuML (v1.0):

Proposed QuML spec (v1.1):

Sample Data for QuML (v1.1):

Spec Changes for QuestionSet:

There are some special characters in line number 27 & 51. So need to re-write these lines.
coordinateDef is not available but coordinate definition is available which is being referred from line number 215. So need correction at line number 215.
media definition is missing which is being referred from anyTypeDef (line number: 224). So need to add media definition.