1.1.1 Relationship to IMS Global Standards

QTI 3 brings together QTI 2.x and Accessible Portable Item Protocol® (APIP®) [APIP-IMPL-10] accessibility and accommodation features into a single assessment specification.

QTI 3 uses an IMS Content Packaging [CP-12] specification profile to package and exchange assessment content. IMS AccessForAll™ [AFA-30] specifications are used to support accessibility functionality.

The QTI 3 project group has also produced an assessment metric profile in connection to the IMS Caliper Analytics® [CALIPER-11] specification.

The IMS Competencies and Academic Standards Exchange® (CASE®) [CASE-10] specification is used to exchange information about learning and education competencies. CASE can also transmit information about rubrics, criteria for performance tasks, which may or may not be aligned to competencies. An example of CASE being used with a QTI package is included in BPIG section 6.

In QTI, Learning Tool Interoperability® (LTI®) [LTI-13] can be used to launch a specific interactive experience for candidates. However, externally launched tools may be blocked during assessment sessions depending on the security protocols of the assessment. The recommended practice is to use LTI only when standardized QTI approaches have been exhausted.

1.1.2 Other Related Standards

Where possible, QTI 3 leverages existing web standards such as HTML5, WAI­-ARIA, CSS, MathML, SSML, PLS, and others produced by the W3C.

W3C accessibility standards, best practices and the assistive technology ecosystem are used to support candidates’ accessibility needs.

1.1.3 Interoperability in QTI 3

The QTI 3 standard is intended to foster interoperability of assessment-based content packages. The QTI 3 standard is comprised of a collection of specification documents designed to ensure that the exchangeable package of assessment content adheres to a rigorous set of file structure expectations. QTI 3 introduces new assessment, section, and item specifications as well as a new QTI 3 Content Package profile (based on the 1.2 version of the IMS Content Package specification).

This revised item specification is enforced by a newer, more rigorous conformance process. User experience interoperability will enable content authors to produce questions and tests that render and behave consistently across systems implementing QTI 3. The resulting specification eases adoption by adding unambiguous content structural markup and accessibility information to QTI 3. The use of web-based markup (HTML5) describes assessment content and semantics, and CSS can describe how the content will be displayed to candidates, in terms of layout, colors, and animations. This helps eliminate rendering inconsistencies across platforms, and enable content authors to communicate specific formatting and rendering expectations for assessment delivery interfaces.

Delivery systems are expected to use the information supplied in the QTI 3 standardized exchange formats, but can elect to use proprietary or other delivery-focused formats during content rendering and data collection.

Within the content package exchange, there may be interoperability issues surrounding specific file formats (e.g., mime types) for some supporting media files or custom interaction code. The QTI 3 standard allows for the use of any media type at this time, so interoperability between vendors may require agreement on the provision of specific file formats. Likely areas where that would occur within the content are pre-recorded media files (audio or video-only, or audio with video) as part of an item stimulus or prompt, or as alternative or supplemental support content for specific support needs. The QTI 3 standard allows for the provision of multiple file formats, which could reduce run-time file-format incompatibility issues.

QTI 3 supports bi-directional text, Ruby Markup https://www.w3.org/International/articles/ruby/  , and vertical text (via CSS) to support internationalization.

Interoperability for QTI 3 is also supported by the use of an IMS governed conformance and certification process, which employs IMS provided online automated validation tools, and requires certified systems to demonstrate validation. The validation tools assist organizations by examining exchange files for structural consistency against the QTI 3 standard. (See the QTI 3 Conformance and Certification [QTI-CERT-30] documentation.)

1.1.4 Packaging

QTI uses the IMS Content Packaging specification for organizing, describing, and exchanging assessment content. Section 6 of this document provides examples of IMS Content Packaging for metadata and variants.

1.1.5 Usage of Alternative XSDs

The physical exchange of QTI-based resources uses a zip file of the set of QTI-XML files, support asset files (e.g. images, video, etc) and a manifest file that defines and describes the relationships between the full set of files. This zip file is known as a QTI Package (this package is based upon the 1EdTech Common Cartridge 1.3 specification).

Validation of ALL of the QTI-XML resources is achieved using the primary ASI XSD ('imsqti_asiv3p0p1_v1p0.xsd'). The construction of the QTI Package requires that each QTI resource is supplied in its own XML file. Therefore, to enable validation of each type of QTI-XML resource we have supplied an XSD specific to that type. The list of XSDs and their intended validation usage is listed in the following Table.

There is NO preferred validation method. Whichever approach is used the validations results are consistent. If any problems are encountered using the 1EdTech XSDs and/or validator then please use the 1EdTech Support Portal at: https://support.imsglobal.org/support/home .

1.1.6 Future Scope

The IMS members contributing to the development of the QTI 3 specification regard this version 3 as a definitive set of features and functionality relating to Web and accessibility standards that should not require significant iterative updates or changes. Correction of errors is an expected part of any specification maintenance, but the QTI project group hopes version 3 meets market demands and will not require major additions or changes in scope.

2.1.1 QTI Metadata

This allows metadata specific to QTI 3 to be added to a QTI 3 item resource in the imsmanifest.xml file.

Full details of the QTI 3 metadata model can be found in the IMS QTI Metadata Information Model and XSD Binding Version 3.0 document, but some of the defined metadata fields cover:

• the interaction types used in the item
• whether the item is a composite item
• whether the item is time dependant or not
• whether the item is adaptive or not
• whether the item will generate feedback or not, and if the feedback is adaptive
• whether the item makes a model solution available
• whether the item is a concrete instance or a template used to create a concrete instance
• how the item will be scored, by QTI response processing, by a human or by some form of external machine scoring
• some information on the tool used to author the item

2.1.2 LOM Metadata

Metadata following the IMS QTI 3 profile of IEEE LOM can also be included, as well as the LOM metadata which can be applied to learning resources generally. This profile provides some rules on how to map QTI concepts to standard LOM fields. For example, that the test or item identifier should be present as an identifier in the LOM metadata. This profile also adds some additional QTI specific vocabularies as an extension to LOM. For example, it supports the Resource Discovery Network Resource Type Vocabulary (RDN/LTSN).

2.1.3 Curriculum Standards Metadata

This allows learning standards and IMS CASE (Competencies and Academic Standards Exchange) identifiers to be associated with a test or item. See the example in section 6.4 on support for CASE in QTI.

2.2.1 XML

The QTI Information Model [QTI-INFO-30] is defined as an eXtensible Markup Language (XML) instance and bound by a set of XML Schema Definition (XSD) files. XML is a W3C Recommendation designed to store and transport data and provides the flexibility and extensibility necessary for QTI assessment content or data to be easily organized and exchanged.

2.2.2 HTML5

Beginning in version 2.2, QTI added a select group of HTML5 elements to the standard. These elements were primarily chosen to increase the accessibility of the assessment content. QTI 3 continues to use a subset of the the complete HTML5 specification to maintain the interoperability of the content being exchanged.

In QTI 3, there is an increased emphasis on the use of HTML5 markup. While the class attribute has been available in previous versions, the use of specific QTI standardized presentation classes was developed to increase rendering interoperability. This new approach uses classes where appropriate: for specifying styling information (presentation). An enumerated, shared vocabulary of styles (prefixed by the qti- prefix) will be maintained outside of the QTI specification (schema) to improve interoperability of styling information. See Section 3 for more details.

If a certain style does not exist in the shared vocabulary while authoring assessment content, a custom one can be used; if this happens frequently for a specific style, the style is a candidate for inclusion in the shared vocabulary.

For specifying behavior (semantics) outside of the existing QTI attributes, custom data attributes ( data-) should be used. In case a certain data- attribute is used frequently, and becomes a best  practice, it is a candidate for promotion to a built-in attribute, part of the QTI schema.

The new standardized QTI presentation classes and attributes use a "qti" prefix in their naming in the hope of preventing class naming conflicts. For all standardized QTI presentation classes, the names begin with "qti-"; for example "qti-labels-decimal" (used for interaction choices). For standardized custom attributes related to presentation, the attribute names begin with "data-qti-"; for example "data-qti-max-selections-message."

The use of these QTI-specific classes and attributes is generally described in the interactions or features for which they are intended. A full list of all standardized QTI vocabulary is included in Appendix B, and the complete documentation and example CSS is found in the QTI 3 Standardized Shared Vocabulary and CSS Classes document.

Note that in XML, attributes MUST contain a value to be valid. HTML allows for some boolean attributes to leave out the values, for example <video controls> to indicate the video should include controls. The QTI 3 XML validator would flag this markup as invalid. In QTI 3, you should use a "true" value for HTML boolean attributes except in the following cases:

1. For the audio and video elements in QTI 3 markup, the "controls" attribute MUST include a value for the attribute to be valid XML. As per the HTML 5 specification, the way to exclude controls is to explicitly not include the attribute in the audio or video element. In QTI 3, valid values to include controls are "controls" (as per the HTML specification) or "true" (the more traditional boolean value for XML). So <video> would mean the controls are not provided to the candidate (as in the example below), and <video controls="controls"> would indicate the candidate should be provided with media controls.
2. For the "default" attribute, use default="default" (though "true" is also valid).

2.2.3 CSS3

QTI 3 does allow for the inclusion of Cascading Style Sheets (CSS) version 3 in content files to transfer the preferred rendering and behavior for test presentation. However, given the complexities of cascading styles, features such as @import and image references, and their possible conflict with delivery system default styles, the automatic acceptance of stylesheets is not required by certified QTI systems. Some assessment programs may, at their own discretion, create and demand support for their own stylesheets as part of the agreed upon scope of work for a particular contract or program.

Associating a stylesheet with an item, a test, a section, a rubric block, template block, feedback structure, or stimulus to control appearance involves using the QTI stylesheet element within the content structure.

There are specific sequential places within a given QTI XML file that can reference stylesheets, and some substructures within the XML files can also reference stylesheets. In each instance, multiple stylesheets can be listed, with the expectation that the styles "cascade" – where stylesheets listed after other stylesheets override previous stylesheets. However, there are instances where stylesheet references are made within nested nodes of the content, and the stylesheet within these nested nodes are meant to be scoped to that node only, and not intended to apply to any other content. For example, assessment items can contain references to stimulus, where the stimulus has a reference to a stylesheet. In this case, the stylesheet within the stimulus is intended only for that stimulus, and not applied to the item content. Similarly, if a stylesheet reference is made from within a rubric block within the qti-item-body node, the stylesheet for the rubric block is scoped only to that specific rubric block, and not for any other rubric blocks within that item, or the item content itself.

Adding a reference to a stylesheet is done by referencing the stylesheet from your file, as shown in the example below.

<qti-stylesheet href="style/custom/your-styles.css" type="text/css" />

Disclaimer: some systems will reject custom CSS as part of item content to maintain overall visual consistency. Only use custom CSS on the item-level as a last resort.

QTI 3 has adopted the "Shared Vocabulary" approach to improve the interoperability for the presentation of assessment content. Use the QTI 3 Standardized CSS Shared Vocabulary and CSS Classes document to reference the shared vocabulary for visual consistency. The use of these QTI-specific classes and data attributes is generally described in the interactions or features for which they are intended.

QTI 3 does not support the use of CSS 3 Speech.

For CSS introduced by item authors or QTI authoring systems via the stylesheet element, a qti-portable-custom-interaction would be able to dynamically insert CSS at run time into the HTML markup associated with the interaction. It is recommended that any such CSS generated be scoped to the interaction.

2.2.4 MathML

QTI 3 permits the use of MathML version 3 directly within the portions of the XML files that use HTML5 markup.

The simple example below illustrates the inclusion of a mathematical expression marked up with MathML into an item.

<!-- This example adapted from the PET Handbook,
  copyright University of Cambridge ESOL Examinations -->
<?xml version="1.0" encoding="UTF-8"?>
<qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 
https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="math"
title="Relativity" adaptive="false" time-dependent="false" xml:lang="en">
  <qti-response-declaration identifier="RESPONSE" cardinality="single" base-type="identifier">
    <qti-correct-response>
      <qti-value>E</qti-value>
    </qti-correct-response>
  </qti-response-declaration>
  <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float"/>
  <qti-item-body>
    <qti-choice-interaction response-identifier="RESPONSE" max-choices="1">
    <qti-prompt>Which famous scientist is popularly associated with the equation
        <div role="math" aria-label="E equals m c squared">
          <math xmlns="http://www.w3.org/1998/Math/MathML" >
            <mrow>
              <mi>E</mi>
              <mo>=</mo>
              <mi>m</mi>
              <msup>
                <mi>c</mi>
                <mn>2</mn>
              </msup>
            </mrow>
          </math>?
        </div>
      </qti-prompt>
      <qti-simple-choice identifier="E">Einstein</qti-simple-choice>
      <qti-simple-choice identifier="G">Galileo</qti-simple-choice>
      <qti-simple-choice identifier="H">Hawking</qti-simple-choice>
      <qti-simple-choice identifier="N">Newton</qti-simple-choice>
    </qti-choice-interaction>
  </qti-item-body>
  <qti-response-processing
   template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/match_correct"/>
</qti-assessment-item>

1EdTech hosts schemas from external namespaces for efficient validation. Note that within this Guide, schema locations and namespaces may not be included in the examples here for ease of reading.

2.2.5 Other Specialized Markup Languages

Specialized markup languages such as Chemical Markup Language (CML) exist for many domains that have a need for computer aided assessment. For that reason, integrating such markup languages with QTI is desirable. Other markup languages include MathML, SVG, and SSML.

A markup language that is widely supported by browsers is Scalable Vector Graphics [SVG]. While direct markup is not supported in the QTI 3 qti-item-body structure at this time, it is easy to include via HTML's 'img' or  'object' tag. Domain specific languages such as CML can often be rendered as SVG, thus providing a convenient way to integrate material with QTI 3.

At present, QTI's qti-printed-variable can be used within MathML and HTML.

A feature that is under consideration for future inclusion is the use of SVG and other languages via HTML 5's 'embed' tag [html5]. The use of this tag is not currently supported either within or outside HTML's 'object' tag.

2.2.6 SSML & PLS

There are two different methods for providing pronunciation information in assessment content that could be consumed by Text-to-Speech (TTS) software (and by extension Screen Reader software) in QTI 3. They are:

• PLS
• SSML

See Section 5 for examples that use SSML & PLS pronunciation.

2.3.1 Use of data- attributes

The custom data-* attribute extends QTI 3.0 to support additional features. When defining a custom attribute, the best practice is to utilize clear naming conventions that describe what the attribute does in order to support interoperability. Documentation for your items should also include detailed information about intended use of custom attributes. Below is an example item with documentation on how each custom attribute is intended to be used.

Example of possible use cases:

items/data-attributes.xml

In this example qti-hottext element:

<?xml version="1.0" encoding="UTF-8"?>
<qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 
https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" 
identifier="data-attribute-example" title="Use of data-attribute" 
adaptive="false" time-dependent="false" xml:lang="en-US">
  <qti-response-declaration identifier="RESPONSE" cardinality="single" base-type="identifier">
    <qti-correct-response>
      <qti-value>B</qti-value>
    </qti-correct-response>
  </qti-response-declaration>
  <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float">
    <qti-default-value>
      <qti-value>0</qti-value>
    </qti-default-value>
  </qti-outcome-declaration>
  <qti-item-body>
    <p>Select the error in the following passage of text (or "No Error" if there is none).</p>
    <qti-hottext-interaction response-identifier="RESPONSE" max-choices="1"

      data-group-name="group1" data-deselection-allowed="false" data-dont-word-wrap="false" >

      <p>Sponsors of the Olympic Games <qti-hottext identifier="A">who bought</qti-hottext> 
      advertising time on United States television
        <qti-hottext identifier="B">includes</qti-hottext>
        <qti-hottext identifier="C">at least</qti-hottext> a dozen international firms
        <qti-hottext identifier="D">whose</qti-hottext> names are familiar to American consumers.<br/>
        <qti-hottext identifier="E">No error.</qti-hottext>
      </p>
    </qti-hottext-interaction>
  </qti-item-body>
  <qti-response-processing 
   template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/match_correct.xml"/>
</qti-assessment-item>

The data-group-name  allows for radio button group assignment.

The data-deselection-allowed  sets whether or not students can deselect that option.

The data-dont-word-wrap  defines if that option is allowed to wrap onto a new line.

2.3.2 Markup Styles and Conventions

QTI 3 introduces a limited number of shared CSS style names  and conventions for use by authoring and delivery systems. See the QTI 3 Standardized Shared Vocabulary and CSS Classes for complete documentation.

By implementing these shared styles and conventions, QTI 3 authoring and delivery platforms can safely import/export – or render – items while preserving certain presentation characteristics without using custom stylesheet injection. Note that all of the shared styles are prefaced by the "qti-" string so as to avoid collisions with a delivery platform's existing CSS.

2.3.3 Use of id and identifier in QTI Content

One attribute, "identifier", is about QTI and it has specific rules regarding format and the QTI information model. On the other hand, "id" is an HTML/XML attribute, and it has different formatting rules, as well as the expectation that an element's id must be unique within the document or else the DOM is considered broken.

2.4.1 Use of W3C Standards in QTI

Assessment delivery systems that use web delivery platforms can be made accessible to Assistive Technology audiences by using standardized accessible web markup. QTI v3 supports and encourages the use of W3C standards, including HTML5, WCAG 2.0, WAI-ARIA 1.0, SSML 1.1, MathML 3, CML, CSS3 (except CSS3 Speech), and PLS. The proper use of these standards will greatly increase the accessibility of the assessment content exchanged in a QTI 3 content package. For guidance around the proper use of the W3C standards for accessibility, use the extensive online W3C documentation .

While W3C recommended techniques are continuously being modified, the exchange of QTI 3 content may have more restricted markup, using fixed released versions and accepted best practices for content transfer. However, delivery systems may choose to adopt newer techniques for the candidate-facing code during presentation (a live assessment session). The methods that are most likely to give candidates access to content, and the ability to respond to interactions, are encouraged to be implemented as soon as they are available and robust enough to be practically implemented.

2.4.2 Candidate Profiles

QTI 3 is capable of using candidate profiles to offer assessment presentation modifications for specific candidates. QTI 3 uses the Access for All® (AfA®) 3.0 standard [AFA-30] for the exchange of candidate profiles, also known as Personal Needs & Preferences (PNP) profiles. The vocabulary used in AfA 3.0 is closely aligned with the predefined supports that can be provided in QTI 3 content.

Through the use of a candidate PNP, a delivery system can provide additional assessment tools for candidates, modify the assessment session parameters (e.g., time limits), or inform test proctors of any special needs of the candidate. Additionally, the assessment content can contain content alternatives or supplemental content that can be activated based on the specific support needs of the candidate.

A description of all the QTI 3 predefined supports can be found in Section 5 of this guide.

2.4.3 Using Catalogs to Store Support-Specific Content

QTI 3 uses a feature called "catalogs" to provide additional content for specific supports which can be activated for specific users, either based on their candidate PNP information or through other test administrative controls. Within an item, any element within the qti-item-body (including the qti-item-body element itself) can point to a referenced container called a "catalog" that contains one or more snippets of content that support the referencing content.

A general description of how to reference and use catalogs can be found in Section 3.7.10, and examples for each of the QTI 3 profile of the AfA 3.0 supports can be found in Section 5.

2.7.1 BI-directional Text and Content

Item authors might want to specify the base directionality of their item contents. This is done by the 'dir' attribute, enabling text and content bi-directionality (BIDI). Although the [UNICODE] specification supports directionality of characters, the 'dir' attribute enables item authors to specify the direction of texts but also other kinds of contents, such as tables or interactions. The Content Model described by QTI 3.0 Information Model obey to bidirectional algorithm, inheritance of text direction information, and direction of embedded text specified by the [html40] and [html5] specifications.

The following example is an Hebrew version of the Composition of Water item. An enclosing div' has a 'dir' attribute with a value of "rtl" (Right to Left). As a result, the 'rtl' directionality is in effect (by inheritance) for all nested block elements. The ChoiceInteraction and its content must be then displayed from right to left as well.

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="choice_multiple_rtl_he" title="Composition of Water (Hebrew)" adaptive="false" time-dependent="false" xml:lang="he"> <qti-response-declaration identifier="RESPONSE" cardinality="multiple" base-type="identifier"> <qti-correct-response> <qti-value>H</qti-value> <qti-value>O</qti-value> </qti-correct-response> <qti-mapping lower-bound="0" upper-bound="2" default-value="-2"> <qti-map-entry map-key="H" mapped-value="1"/> <qti-map-entry map-key="O" mapped-value="1"/> <qti-map-entry map-key="Cl" mapped-value="-1"/> </qti-mapping> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float"/> <qti-item-body> <div dir="rtl"> <qti-choice-interaction response-identifier="RESPONSE" shuffle="true" max-choices="0"> <qti-prompt>איזה מהגורמים הבאים משמשים ליצירת מים</qti-prompt> <qti-simple-choice identifier="H" fixed="false">מימן</qti-simple-choice> <qti-simple-choice identifier="He" fixed="false">הליום</qti-simple-choice> <qti-simple-choice identifier="C" fixed="false">פחם</qti-simple-choice> <qti-simple-choice identifier="O" fixed="false">חמצן</qti-simple-choice> <qti-simple-choice identifier="N" fixed="false">חנקן</qti-simple-choice> <qti-simple-choice identifier="Cl" fixed="false">כלור</qti-simple-choice> </qti-choice-interaction> </div> </qti-item-body> <qti-response-processing template="https://www.imsglobal.org/question/qti_v3p0/rptemplates/map_response.xml"/> </qti-assessment-item>

The next example describes the use of the bdo class to turn off the bidirectional algorithm for given text portions ("F1", "Rubens Barrichello", "Jenson Button", "Michael Schumacher").

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="order_rtl_he" title="Grand Prix של בחריין" adaptive="false" time-dependent="false" xml:lang="he" > <qti-response-declaration identifier="RESPONSE" cardinality="ordered" base-type="identifier"> <qti-correct-response> <qti-value>DriverC</qti-value> <qti-value>DriverA</qti-value> <qti-value>DriverB</qti-value> </qti-correct-response> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float"/> <qti-item-body> <div dir="rtl"> <qti-order-interaction response-identifier="RESPONSE" > <qti-prompt><bdo dir="ltr">F1</bdo> הנהגים הבאים סיימו על הפודיום בגרנד פרי בחריין הראשון אי פעם.אתה יכול לארגן אותם בסדר נכון הגמר?</qti-prompt> <qti-simple-choice identifier="DriverA"><bdo dir="ltr">Rubens Barrichello</bdo></qti-simple-choice> <qti-simple-choice identifier="DriverB"><bdo dir="ltr">Jenson Button</bdo></qti-simple-choice> <qti-simple-choice identifier="DriverC"><bdo dir="ltr">Michael Schumacher</bdo></qti-simple-choice> </qti-order-interaction> </div> </qti-item-body> <qti-response-processing template="https://www.imsglobal.org/question/qti_v3p0/rptemplates/match_correct.xml"/> </qti-assessment-item>

2.7.2 Ruby Markup

QTI 3.0 includes Ruby Markup support. Its intent is to provide a way to render small annotations rendered alongside base text. As explained in depth by the W3C Ruby Markup and Styling article, "Ruby is used in East Asian countries to describe characters that readers might not be familiar with, or describe the meaning of ideographic characters". [ruby] Markup in QTI 3.0 adheres to the description of W3C in [html5].

The item example below makes use of the ruby, rb and rt classes to annotate base text in paragraphs and choices. It uses the default Choice Interaction rendering of horizontally presented text from left-to-right.

<?xml version="1.0" encoding="UTF-8"?> <!-- This example adapted from the PET Handbook, copyright University of Cambridge ESOL Examinations --> <!-- The example combines shuffle with the fixation of one simpleChoice in place --> <!-- Ruby markup is defined in NS hq5 (HTML5 for QTI), which is referenced in the main QTI 2.2 XSD --> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" m:xsi="http://www.w3.org/1998/Math/MathML" xsi:schemaLocation=" http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd http://www.w3.org/1998/Math/MathML https://purl.imsglobal.org/spec/mathml/v3p0/schema/xsd/mathml3.xsd" identifier="choice_ruby" title="出身地" adaptive="false" time-dependent="false" xml:lang="ja" > <qti-response-declaration identifier="RESPONSE" cardinality="single" base-type="identifier"> <qti-correct-response> <qti-value>ChoiceHK</qti-value> </qti-correct-response> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float"> <qti-default-value> <qti-value>0</qti-value> </qti-default-value> </qti-outcome-declaration> <qti-item-body> <p>村田<ruby><rb>真</rb><rt>まこと</rt></ruby>の出身地はどこですか</p> <qti-choice-interaction response-identifier="RESPONSE" max-choices="1" class="qti-labels-cjk-ideographic" > <qti-prompt>選びなさい</qti-prompt> <qti-simple-choice identifier="ChoiceHK"><ruby><rb>北海道</rb><rt>ほっかいどう</rt></ruby></qti-simple-choice> <qti-simple-choice identifier="ChoiceTH">東北</qti-simple-choice> <qti-simple-choice identifier="ChoiceHR">北陸</qti-simple-choice> <qti-simple-choice identifier="ChoiceKT">関東</qti-simple-choice> <qti-simple-choice identifier="ChoiceKST">甲信越</qti-simple-choice> <qti-simple-choice identifier="ChoiceKK">近畿</qti-simple-choice> <qti-simple-choice identifier="ChoiceKS">関西</qti-simple-choice> <qti-simple-choice identifier="ChoiceSK">四国</qti-simple-choice> <qti-simple-choice identifier="ChoiceTC">中国</qti-simple-choice> <qti-simple-choice identifier="ChoiceKY">九州</qti-simple-choice> </qti-choice-interaction> </qti-item-body> <qti-response-processing template="https://www.imsglobal.org/question/qti_v3p0/rptemplates/match_correct.xml"/> </qti-assessment-item>

In this next ruby example, the standardized shared vocabulary is used to show the text vertically from right to left. Go to the QTI 3 Standardized Shared Vocabulary and CSS Classes document for additional vertical text options.

<?xml version="1.0" encoding="UTF-8"?> <!-- This example adapted from the PET Handbook, copyright University of Cambridge ESOL Examinations --> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="choice_ruby_i23n" title="出身地" adaptive="false" time-dependent="false" xml:lang="ja" > <qti-response-declaration identifier="RESPONSE" cardinality="single" base-type="identifier"> <qti-correct-response> <qti-value>ChoiceHK</qti-value> </qti-correct-response> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float"> <qti-default-value> <qti-value>0</qti-value> </qti-default-value> </qti-outcome-declaration> <qti-item-body> <div class="qti-height-96 qti-writing-mode-vertical-rl qti-float-right"> <p>村田<ruby><rb>真</rb><rt>まこと</rt></ruby>の出身地はどこですか</p> <qti-choice-interaction response-identifier="RESPONSE" max-choices="1" class="qti-labels-cjk-ideographic qti-writing-orientation-vertical-lr" > <qti-prompt>選びなさい</qti-prompt> <qti-simple-choice identifier="ChoiceHK"><ruby><rb>北海道</rb><rt>ほっかいどう</rt></ruby></qti-simple-choice> <qti-simple-choice identifier="ChoiceTH">東北</qti-simple-choice> <qti-simple-choice identifier="ChoiceHR">北陸</qti-simple-choice> <qti-simple-choice identifier="ChoiceKT">関東</qti-simple-choice> <qti-simple-choice identifier="ChoiceKST">甲信越</qti-simple-choice> <qti-simple-choice identifier="ChoiceKK">近畿</qti-simple-choice> <qti-simple-choice identifier="ChoiceKS">関西</qti-simple-choice> <qti-simple-choice identifier="ChoiceSK">四国</qti-simple-choice> <qti-simple-choice identifier="ChoiceTC">中国</qti-simple-choice> <qti-simple-choice identifier="ChoiceKY">九州</qti-simple-choice> </qti-choice-interaction> </div> </qti-item-body> <qti-response-processing template="https://www.imsglobal.org/question/qti_v3p0/rptemplates/match_correct.xml"/> </qti-assessment-item>

3.1.1 Structures within the qti-assessment-item Node

The QTI-specific XML structures are described in the QTI 3Item XSD. The QTI 3 Item XSD can be found at https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_itemv3p0p1_v1p0.xsd , which is a subset of the full QTI 3 XSD found at https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd. The namespace is http://www.imsglobal.org/xsd/imsqtiasi_v3p0

An item typically includes the following information:

• Scoring data
• The item content presented to the candidate, which itself contains:

• Any directions/instructions
• Any stimuli or references to stimuli
• The prompt(s)
• The interaction(s)
• Feedback for the candidate
• Supplemental content or references to supplemental content
• Content displayed, voiced, or printed, contingent on the candidate's Access for All (AFA) Personal Needs and Preferences (PNP)

The above information is stored in specific QTI 3structures, and must be supplied in the sequence listed below :

1. qti-context-declaration
2. qti-response-declaration
3. qti-outcome-declaration
4. qti-template-declaration
5. qti-template-processing
6. qti-assessment-stimulus-ref
7. qti-companion-materials-info
8. qti-response-processing
9. qti-modal-feedback

The inclusion or exclusion of the above structures depends on the complexity of the item, and on the needs of the assessment program using the assessment content.

Scoring an item can be quite complex, and the information used to provide the response information and the score(s)received (the outcome(s)) are possible using a combination of the following structures:

1. qit-context-declaration
2. qti-response-declaration
3. qti-outcome-declaration
4. qti-response-processing

Content (and content presentation data) to be presented to the candidate is supplied or referenced in a combination of these structures:

1. qti-assessment-stimulus-ref
2. qti-companion-materials-info
3. qti-stylesheet
4. qti-item-body

Content presented to candidates using variables use these structures:

1. qti-template-declaration
2. qti-template-processing
3. qti-catalog-info
4. qti-modal-feedback

A brief introduction to the AssessmentItem structures is provided below.

3.2.1 Interoperability and Utilizing Shared Vocabularies

Previous versions of QTI lack specificity with respect to interaction presentation, styling, and behavior. Consequently, QTI authoring systems and delivery systems have implemented interactions with custom presentation/behavior definitions, which in turn have become an impediment to interoperability. To improve interaction presentation/behavior interoperability, QTI 3 introduces, "shared vocabularies" that describe more fine-grained presentation control and more semantically-explicit styling and behaviors.

There are two primary mechanisms of the QTI 3 interaction shared vocabularies:

1. An interaction's class attribute, and
2. An interaction's " data-" attributes.

In order to prevent collisions with existing classes, the QTI 3 interaction shared vocabularies  use classes with the "qti-" prefix.

Although the class and " data-" attributes already exist in QTI 2.2, the shared vocabularies explicitly define how to use these attributes to achieve certain agreed-upon rendered presentations. By agreeing to implement interaction styling and behaviors according to the definitions of the shared vocabularies, interaction interoperability may be greatly improved.

Implementers of custom presentations/behaviors should avoid using classes with the "qti-" prefix, and should also avoid using the QTI 3 established "data-" attributes from the shared vocabularies. Over time, it is the expectation that the shared vocabularies will evolve as common use-cases emerge.

When using classes that indicate that the presentation of content should be horizontal (qti-orientation-horizontal, qti-choices-stacking-2, etc.), it can force some of the choices outside the single width of the viewing portal, which can be problematic for candidates. For low-vision candidates using magnification (or text-appearance → font-size or word-spacing), the likelihood of horizontal scrolling is increased. When choices are placed off-screen, candidates can accidentally disregard the choices, candidates are required to use additional working memory to respond to the item, and it adds significant time for low-vision candidates.

If the candidate is known to have low-vision, and choices could be displayed beyond the width of a single viewport, presentation systems should consider presenting the choices vertically.

The 1EdTech QTI 3 Standardized Shared Vocabulary and CSS Classes document enumerates and details all of the currently adopted shared vocabulary.

3.2.2 Choice Interaction

The ChoiceInteraction.Type (qti-choice-interaction) interaction presents a collection of choices to the candidate. The candidate's task is to select one or more of the choices, up to a maximum of max-choices. The interaction is always initialized with no choices selected.

The ChoiceInteraction.Type must be bound to a response variable with a base-type of identifier and single or multiple cardinality.

In a choice interaction, it is considered best practice to use the shared vocabulary related to the layout of choices instead of using the optional orientation attribute. If both the shared vocabulary classes and the orientation attribute are used, the shared vocabulary classes take precedence over the orientation attribute value (including the default value of "vertical").

ChoiceInteraction Attributes (element: qti-choice-interaction)

* Deprecated in favor of the shared vocabulary.

The choice interaction is made up of choices, which use the qti-simple-choice element (SimpleChoice.Type) to present an ordered list of choices to the candidate.

As noted in the table above, the "shuffle" attribute is optional and defaults to false.  However, if the shuffle attribute is set to "true", and the delivery engine supports the discretionary "shuffle" feature, the presentation system must randomize the order in which the choices are originally listed in the Assessment Item XML, subject to the value of the fixed attribute of each choice. If fixed is "true" for a choice then the position of this choice within the interaction must not be changed by the presentation system even if the immediately enclosing interaction supports the shuffling of choices. If no value is specified then the choice is free to be shuffled.

SimpleChoice (element: qti-simple-choice) Attributes

Here is an example of a choice interaction that allows the candidate to pick one choice (sometimes called single selection choice).

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item  xmlns="http://www.imsglobal.org/xsd/qti/imsqtiasi_v3p0"  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0  https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_itemv3p0p1_v1p0.xsd"  identifier="beginnersguide007"  title="BG true false example "  time-dependent="false"  xml:lang="en-US">  <qti-response-declaration base-type="identifier" cardinality="single" identifier="RESPONSE">   <qti-correct-response>    <qti-value>true</qti-value>   </qti-correct-response>  </qti-response-declaration>  <qti-outcome-declaration base-type="float" cardinality="single" identifier="SCORE">   <qti-default-value>    <qti-value>1</qti-value>   </qti-default-value>  </qti-outcome-declaration>  <qti-item-body>   <p>This is a True/False question?</p>   <qti-choice-interaction max-choices="1" response-identifier="RESPONSE">     <qti-simple-choice identifier="true">True</qti-simple-choice>     <qti-simple-choice identifier="false">False</qti-simple-choice>   </qti-choice-interaction>  </qti-item-body>  <qti-response-processing template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/match_correct"/> </qti-assessment-item>

Below is an example of a choice interaction that allows the candidate to select multiple response options to respond to the prompt.

Example: qti-choice-interaction (multiple cardinality)

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="QTI3multiplechoice2" title="QTI 3 Choice with Multiple Cardinality" xml:lang="en-US" time-dependent="false"> <qti-response-declaration identifier="RESPONSE" cardinality="multiple" base-type="identifier"> <qti-correct-response> <qti-value>H</qti-value> <qti-value>O</qti-value> </qti-correct-response> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float"/> <qti-item-body> <qti-choice-interaction response-identifier="RESPONSE" min-choices="1" max-choices="6"> <qti-prompt>Which of the following elements are used to form water?</qti-prompt> <qti-simple-choice identifier="H">Hydrogen</qti-simple-choice> <qti-simple-choice identifier="He">Helium</qti-simple-choice> <qti-simple-choice identifier="C">Carbon</qti-simple-choice> <qti-simple-choice identifier="O">Oxygen</qti-simple-choice> <qti-simple-choice identifier="N">Nitrogen</qti-simple-choice> <qti-simple-choice identifier="Cl">Chlorine</qti-simple-choice> </qti-choice-interaction> </qti-item-body> <qti-response-processing template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/match_correct"/> </qti-assessment-item>

By default, in the absence of any shared vocabulary, the presentation of each choice control, label, label suffix, and description, is left to the implementer, with the only requirement that the choices are displayed in a single column, vertically oriented.

The qti-choice-interaction has a considerable amount of its shared vocabulary dedicated to the presentation/layout of the interaction's associated qti-simple-choices. Each qti-simple-choice consists of a collection of elements, displayed from left to right, defined as follows:

1. A "control"; e.g., either a radio button or checkbox control, and
2. A "label"; e.g., often an alphanumeric character such as, "A", "B", "1", "2", etc.
3. A "label suffix"; e.g., a "." or ")" character after the label, and
4. A "description"; e.g., the HTML content contained by a qti-simple-choice element

Go to the 1EdTech QTI 3 Standardized Shared and CSS Classes section on Choice Interaction classes for full details.

3.2.3 Text Entry Interaction

A Text Entry Interaction is an inline interaction that obtains a simple piece of text from the candidate. Like qti-inline-choice-interaction, the delivery engine must allow the candidate to review their choice within the context of the surrounding text.

The TextEntryInteraction.Type (qti-text-entry-interaction) must be bound to a response variable with single or record cardinality only. If the response variable has single cardinality the base-type must be one of string, integer or float; if it has record cardinality the permitted fields are 'stringValue', 'floatValue', etc.

TextEntryInteraction Attributes (element: qti-text-entry-interaction)

Below is an example of a Text Entry Interaction:

<?xml version="1.0" encoding="UTF-8"?>
<qti-assessment-item 
 xmlns="http://www.imsglobal.org/xsd/qti/imsqtiasi_v3p0" 
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 
 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_itemv3p0p1_v1p0.xsd"
 identifier="bpig010"
 title="Text Entry example"
 time-dependent="false" 
 xml:lang="en-US">
 <qti-response-declaration identifier="RESPONSE" base-type="string" cardinality="single">
  <qti-correct-response>
   <qti-value>York</qti-value>
  </qti-correct-response>
  <qti-mapping default-value="0">
   <qti-map-entry map-key="York" mapped-value="1" case-sensitive="true" />
   <qti-map-entry map-key="york" mapped-value="0.5" />
  </qti-mapping>
 </qti-response-declaration>
 <qti-outcome-declaration base-type="float" cardinality="single" identifier="SCORE" />
 <qti-item-body>
  <p>Identify the missing word in this famous quote from Shakespeare's Richard III.</p>
  <div>
   <blockquote>
    <p>Now is the winter of our discontent<br/>
      Made glorious summer by this sun of <qti-text-entry-interaction response-identifier="RESPONSE" />;<br/>
      And all the clouds that lour'd upon our house<br/>
      In the deep bosom of the ocean buried.</p>
   </blockquote>
  </div>
 </qti-item-body>
 <qti-response-processing template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/map_response" />
</qti-assessment-item>

Which might look something like this when presented to candidates:

The scoring for this item could have just matched the correct response (in the response declaration) but actually uses a mapping to enable partial credit for an improperly capitalized city name (spelled without a capital letter, or all caps, or other capitilization error). When mapping strings the mapping, by default, is NOT case sensitive. This example also illustrates the use of the mapping when the response only has single cardinality.

The bulk of the shared vocabulary for the Text Entry interaction adds further definition to the presentation width of the input element by utilizing the class attribute. Go to the 1EdTech QTI 3 Standardized Shared and CSS Classes section on Text Entry Interaction classes for full details.

3.2.4 Extended Text Interaction

If an extended written response is required from the candidate then the Extended Text Interaction (qti-extended-text-interaction) is appropriate. An extended text interaction is a block Interaction that allows the candidate to enter an extended amount of text.

ExtendedTextInteraction Attributes (element: qti-extended-text-interaction)

The qti-extended-text-interaction must be bound to a response variable of single, multiple, ordered or record cardinality. If the response variable has record cardinality the fields in the record must be 'stringValue', 'floatValue', etc. Otherwise it must have a base-type of string, integer or float. When bound to response variable with single cardinality a single string of text is required from the candidate. When bound to a response variable with multiple or ordered cardinality several separate text strings may be required.

The extended text interaction allows a candidate to supply a text string for a response. A basic example of the markup is shown below.

<?xml version="1.0" encoding="UTF-8"?>
<qti-assessment-item 
 xmlns="http://www.imsglobal.org/xsd/qti/imsqtiasi_v3p0" 
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 
 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_itemv3p0p1_v1p0.xsd"
 identifier="bpig009"
 title="Extended Text example"
 time-dependent="false" 
 xml:lang="en-US">
 <qti-response-declaration identifier="RESPONSE" base-type="string" cardinality="single" />
 <qti-outcome-declaration base-type="float" cardinality="single" identifier="SCORE" />
 <qti-item-body>
  <p>Read this postcard from your English pen-friend, Sam.</p> 
   <div>
    <blockquote class="postcard">
     <p>Here is a postcard of my town. Please send me<br/>
       A postcard from your town. What size is your Town?<br/>What is the nicest part of your town?<br/>
       Where do you go in the evenings?</p>
     <p>Sam</p>
    </blockquote>
   </div>
   <qti-extended-text-interaction response-identifier="RESPONSE">
    <qti-prompt>Write Sam a postcard. Answer the questions. Write 23–30 words</qti-prompt>
   </qti-extended-text-interaction>
 </qti-item-body>
</qti-assessment-item>

The cardinality of "single" in the qti-response-processing element means that a single string of text is used in the response, though it may include multiple words or paragraphs within that string.

The example does not include a response processing node, as automated scoring of extended text responses is beyond the scope of the QTI specification.

The shared vocabulary for the extended text interaction is intended to provide more precision when describing:

1. Interaction height
2. Character counter behavior
3. Plain or Rich Text options
4. A custom pattern-mask message
5. Placeholder text

Responsive design implies that delivery systems should display an input area (typically, this will be a <textarea> or <div> html element) that has a width equal to 100% of the interaction's encapsulating container. Consequently, there is no shared vocabulary for overriding the width of this interaction.

Go to the 1EdTech QTI 3 Standardized Shared Vocabulary and CSS document for details related to the Extended Text Interaction.

3.2.5 Gap Match Interaction

A gap match interaction is a block Interaction that contains a number of gaps that the candidate can fill from an associated set of choices. The candidate must be able to review the content with the gaps filled in context, as indicated by their choices.

The GapMatchInteraction.Type (qti-gap-match-interaction)  is similar to Match Interaction (qti-match-interaction) except that the choices in the second set are gaps (qti-gap) in a given passage of text and the task involves selecting choices from the first set and using them to fill the gaps. The same attributes are involved in controlling which, and how many, pairings are allowed, though there is no match-max attribute for the gaps because they can only ever have one associated choice. The scoring is again done with a mapping.

GapMatchInteration Attributes (element: qti-gap-match-interaction)

Sub-elements include qti-gap-text (GapText.Type) and qti-gap-img (GapImg.Type).

GapText Attributes (element: qti-gap-text)

The qti-gap-img contains a single HTML object element.

GapImg Attributes (element: qti-gap-img)

Additional formatting may be applied within the qti-gap-text element allowing for a greater variation.' Allowed formats include:

'br', 'img', 'xi:include', 'm:math', 'object', 'qti-printed-variable', 'a', 'abbr', 'acronym', 'b', 'big', 'cite', 'code', 'dfn', 'em', 'qti-feedback-inline', 'i', 'kbd', 'q', 'samp', 'small', 'span', 'strong', 'sub', 'sup', 'tt', 'var', 'qti-template-inline', 'bdi', 'bdo', 'label', 'ruby', 'ssml11:*'.

The qti-gap-match-interaction must be bound to a response variable with base-type directedPair and either single or multiple cardinality, depending on the number of gaps. The choices represent the source of the pairing and gaps the targets. Each gap can have at most one choice associated with it. The maximum occurrence of the choices is controlled by the match-max attribute of qti-gap-text or qti-gap-img.

The following is an example of a gap match interaction:

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="gap-match-example-1" title="Gap Match Example 1" time-dependent="false" xml:lang="en-US" > <qti-response-declaration identifier="RESPONSE" cardinality="multiple" base-type="directedPair"> <qti-correct-response> <qti-value>W G1</qti-value> <qti-value>Su G2</qti-value> </qti-correct-response> <qti-mapping default-value="-1" lower-bound="0"> <qti-map-entry map-key="W G1" mapped-value="1"/> <qti-map-entry map-key="Su G2" mapped-value="2"/> </qti-mapping> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float"/> <qti-item-body> <qti-gap-match-interaction max-associations="0" response-identifier="RESPONSE" class="qti-choices-top" > <qti-prompt>Identify the missing words in this famous quote from Shakespeare's Richard III.</qti-prompt> <qti-gap-text identifier="W" match-max="1">winter</qti-gap-text> <qti-gap-text identifier="Sp" match-max="1">spring</qti-gap-text> <qti-gap-text identifier="Su" match-max="1">summer</qti-gap-text> <qti-gap-text identifier="A" match-max="1">autumn</qti-gap-text> <blockquote> <p> Now is the <qti-gap identifier="G1"/> of our discontent<br/> Made glorious <qti-gap identifier="G2"/> by this sun of York;<br/> And all the clouds that lour'd upon our house<br/> In the deep bosom of the ocean buried. </p> </blockquote> </qti-gap-match-interaction> </qti-item-body> <qti-response-processing template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/map_response.xml"/> </qti-assessment-item>

The shared vocabulary for the Gap Match Interaction is intended to provide more precision when describing:

1. Positioning of the Gap Choices container with respect to the passage of text containing the Gaps.
2. Gap Choices container width.
3. Gap element widths.
4. Custom max|min-associations message overrides.

The full list of the Gap Match Interaction vocabulary is enumerated in the 1EdTech QTI 3 Standardized Shared Vocabulary and CSS document.

3.2.6 Hotspot Interaction

A HotspotInteraction.Type (qti-hotspot-interaction) is a graphical interaction with a corresponding set of choices that are defined as areas of the graphic image. The candidate's task is to select one or more of the areas (hotspots).

The hotspot interaction should only be used when the spatial relationship of the choices with respect to each other (as represented by the graphic image) is important to the needs of the item. Otherwise, Choice Interaction should be used instead with separate material for each option.

The delivery engine must clearly indicate selected hotspots when such hotspots are selected.  If the Shared Vocabulary class qti-unselected-hidden is present, the delivery engine must hide the hotspots in their unselected and unfocused state.  If the qti-unselected-hidden is not present, indicating hotspots in their unselected and unfocused state is left to the delivery engine.

HotspotInteraction Attributes (element: qti-hotspot-interaction)

The sub-element sequence for the qti-hotspot-interaction:

1. either img, picture, or object (must have only 1, note that the use of object is deprecated in QTI 3)
2. qti-hotspot-choice (at least 1)

HotspotChoice Attributes (element: qti-hotspot-choice)

The hotspot interaction must be bound to a response variable with a base-type of identifier and single or multiple cardinality.

The shared vocabulary for the Hotspot Interaction is intended to provide more precision when describing:

1. Hotspot Selections theming.
2. Custom max|min-choices message overrides.

All information related to the Hotspot Interaction shared vocabulary is enumerated in the 1EdTech QTI 3 Standardized Shared Vocabulary and CSS document.

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="QTI3-hotspot" title="hotspot" time-dependent="false" xml:lang="en-US"> <qti-response-declaration identifier="RESPONSE" cardinality="single" base-type="identifier"> <qti-correct-response> <qti-value>H</qti-value> </qti-correct-response> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float" /> <qti-item-body> <p>The picture illustrates four of the most popular lighthouses on outer Cape Cod, Massachusetts: Chatham Lighthouse, Highland Lighthouse, Nauset Lighthouse, and Race Point Lighthouse.</p> <qti-hotspot-interaction response-identifier="RESPONSE" max-choices="1"> <qti-prompt>Which one is Highland Lighthouse?</qti-prompt> <img src="images/map_cape_cod.svg" width="700" height="550" alt="a map of Cape Cod Massachusetts with 4 lighthouse icons distributed on the outer Cape" /> <qti-hotspot-choice identifier="R" shape="circle" coords="418,29,40" /> <qti-hotspot-choice identifier="H" shape="circle" coords="546,56,40" /> <qti-hotspot-choice identifier="N" shape="circle" coords="596,182,40" /> <qti-hotspot-choice identifier="C" shape="circle" coords="598,316,40" /> </qti-hotspot-interaction> </qti-item-body> <qti-response-processing template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/match_correct.xml"/> </qti-assessment-item>

3.2.7 Hot Text Interaction

The HotTextInteraction.Type (qti-hottext-interaction) presents a set of choices to the candidate represented as selectable runs of text embedded within a surrounding context, such as a simple passage of text. Like Choice Interaction, the candidate's task is to select one or more of the choices, up to a maximum of max-choices.

The interaction is initialized from the qti-default-value of the associated response variable, a NULL value indicating that no choices are selected (the usual case).

HotTextInteraction Attributes (element: qti-hottext-interaction)

The qti-hottext-interaction must be bound to a response variable with a base-type of identifier and single or multiple cardinality.

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="hot-text-example-1" title="Q12 Hot-text Interaction - Single Cardinality" adaptive="false" time-dependent="false" xml:lang="en-US"> <qti-response-declaration identifier="RESPONSE" cardinality="single" base-type="identifier"> <qti-correct-response> <qti-value>B</qti-value> </qti-correct-response> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float"> <qti-default-value> <qti-value>0</qti-value> </qti-default-value> </qti-outcome-declaration> <qti-item-body> <p> Select the error in the following passage of text (or <em>No Error</em> if there is none). </p> <qti-hottext-interaction response-identifier="RESPONSE" max-choices="1"> <p>Sponsors of the Olympic Games <qti-hottext identifier="A">who bought</qti-hottext> advertising time on United States television <qti-hottext identifier="B">includes</qti-hottext> <qti-hottext identifier="C">at least</qti-hottext> a dozen international firms <qti-hottext identifier="D">whose</qti-hottext> names are familiar to American consumers. <qti-hottext identifier="E">No error.</qti-hottext> </p> </qti-hottext-interaction> </qti-item-body> <qti-response-processing template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/match_correct.xml"/> </qti-assessment-item>

The above example demonstrates an interaction with a single selection. For multiple selections, the response processing cardinality would be "multiple" and you may choose to limit the number of selections using the max-choices attribute in the qti-hottext-interaction element (or set to "0" for unlimited/all selections).

The shared vocabulary for the Hot Text Interaction is intended to provide more precision when describing:

1. Hiding the input control of the Hot Text choices.
2. Custom max|min-choices message overrides.

All information related to the Hot Text Interaction shared vocabulary is enumerated in the 1EdTech QTI 3 Standardized Shared Vocabulary and CSS document.

3.2.8 Inline Choice

The InlineChoiceInteraction.Type (qti-inline-choice-interaction) is an inline interaction to display a set of simple text choices in context in a surrounding text, which may be subject to variable value substitution with qti-printed-variable.

InlineChoiceInteraction Attributes (element: qti-inline-choice-interaction)

The sub-element seCoolquence of qti-inline-choice-interaction is:

1. qti-label (maximum of 1)
2. qti-inline-choice (at least 1)

InlineChoice Attributes (element: qti-inline-choice)

When rendering an inline choice interaction, the common implementation is an embodiment of a <select> html form element or a combo box form control.  

Below is an example of an inline choice interaction that allows the candidate to select one answer option to respond to the prompt.

Example: qti-inline-choice-interaction

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="QTI3-inline-choice" title="Inline Choice Interaction" time-dependent="false" xml:lang="en-US">   <qti-response-declaration base-type="identifier" cardinality="single" identifier="RESPONSE">     <qti-correct-response>       <qti-value>Y</qti-value>     </qti-correct-response>   </qti-response-declaration>   <qti-outcome-declaration base-type="float" cardinality="single" identifier="SCORE"/>   <qti-item-body>     <p>Identify the missing word in this famous quote from Shakespeare's Richard III.</p>     <blockquote>       <p>Now is the winter of our discontent       <br/>Made glorious summer by this sun of       <qti-inline-choice-interaction response-identifier="RESPONSE" shuffle="false">         <qti-inline-choice identifier="G">Gloucester</qti-inline-choice>         <qti-inline-choice identifier="L">Lancaster</qti-inline-choice>         <qti-inline-choice identifier="Y">York</qti-inline-choice>       </qti-inline-choice-interaction>;       <br/>And all the clouds that lour'd upon our house       <br/>In the deep bosom of the ocean buried.</p>     </blockquote>   </qti-item-body>   <qti-response-processing template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/match_correct.xml"/> </qti-assessment-item>

The bulk of the shared vocabulary for this interaction adds further definition to the presentation width of the selection element by utilizing the class attribute.

Go to the QTI 3 Standardized Shared Vocabulary and CSS section on Inline Choice for full details.

3.2.9 Match Interaction

A MatchInteraction.Type (qti-match-interaction) is a blockInteraction that presents candidates with two sets of choices and allows them to create associations between pairs of choices in the two sets, but not between pairs of choices in the same set. Further restrictions can still be placed on the allowable associations using the match-max characteristic of the choices.

The sub-element within qti-match-interaction is qti-simple-match-set.   MatchInteration Attributes (element: qti-match-interaction)

The sub-element of qti-match-interaction is qti-simple-match-set (SimpleMatchSet.Type). The qti-simple-match-set has an optional "id" attribute which contains a UniqueIdentifier.Type. The qti-simple-match-set contains an ordered set of choices using qti-simple-associable-choice (SimpleAssociableChoice.Type) elements.

SimpleAssociableChoice Attributes (element: qti-simple-associable-choice)

The match interaction must be bound to a response variable with base-type directedPair and either single or multiple cardinality.

In the match interaction example below, the candidate's response is declared to have directedPair because the task involves pairing up choices from a source set into a target set. In this case characters from plays with the names of the plays from which they are drawn. Notice that match-max on the characters (the first set of associable choices) is "1" because each character can be in only one play but it is "4" on the plays (the second set of associable choices) because each play could contain all the characters. For example, Demetrius and Lysander were both in A Midsummer-Night's Dream, so in the correct response that play has two associations. In the mapping used for response processing these two associations have been awarded only a half a mark each.

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="QTI3-match" title="Match Example" time-dependent="false" xml:lang="en-US"> <qti-response-declaration identifier="RESPONSE" cardinality="multiple" base-type="directedPair"> <qti-correct-response> <qti-value>C R</qti-value> <qti-value>D M</qti-value> <qti-value>L M</qti-value> <qti-value>P T</qti-value> </qti-correct-response> <qti-mapping default-value="0"> <qti-map-entry map-key="C R" mapped-value="1" /> <qti-map-entry map-key="D M" mapped-value="0.5" /> <qti-map-entry map-key="L M" mapped-value="0.5" /> <qti-map-entry map-key="P T" mapped-value="1" /> </qti-mapping> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float" /> <qti-item-body> <qti-match-interaction response-identifier="RESPONSE" max-associations="4"> <qti-prompt>Match the following characters to the Shakespeare play they appeared in:</qti-prompt> <qti-simple-match-set> <qti-simple-associable-choice identifier="C" match-max="1">Capulet</qti-simple-associable-choice> <qti-simple-associable-choice identifier="D" match-max="1">Demetrius</qti-simple-associable-choice> <qti-simple-associable-choice identifier="L" match-max="1">Lysander</qti-simple-associable-choice> <qti-simple-associable-choice identifier="P" match-max="1">Prospero</qti-simple-associable-choice> </qti-simple-match-set> <qti-simple-match-set> <qti-simple-associable-choice identifier="M" match-max="4">A Midsummer-Night's Dream</qti-simple-associable-choice> <qti-simple-associable-choice identifier="R" match-max="4">Romeo and Juliet</qti-simple-associable-choice> <qti-simple-associable-choice identifier="T" match-max="4">The Tempest</qti-simple-associable-choice> </qti-simple-match-set> </qti-match-interaction> </qti-item-body> <qti-response-processing template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/map_response.xml"/> </qti-assessment-item>

The shared vocabulary for the Match Interaction is intended to provide more precision when describing:

1. Non-tabular Match Interaction positioning of the first Simple Match Set choices with respect to the second Simple Match Set choices.
2. Tabular Match Interaction styling.
3. Custom max|min-associations message overrides.

Go to the QTI 3 Standardized Shared Vocabulary and CSS section on Match Interaction for full details.

3.2.10 Order

In an OrderInteraction.Type (qti-order-interaction) the candidate's task is to reorder the choices, the order in which the choices are displayed initially is significant. By default the candidate's task is to order all of the choices but a subset of the choices can be requested using the max-choices and min-choices attributes. When specified the candidate must first select a (sub)set of the choices and then impose an ordering on them.

OrderInteraction Attributes (element: qti-order-interaction)

The sub-element of qti-order-interaction is qti-simple-choice (SimpleChoice.Type) where there must be at least one qti-simple-choice in the interaction to be valid, and at least 2 choices to be useful as an order interaction.

SimpleChoice (element: qti-simple-choice) Attributes

This example below illustrates the Order Interaction. The candidate's response is declared to have ordered and the correct value is therefore composed of an ordered list of value. The question uses the standard response processing template Match Correct to score 1 for a completely correct answer and 0 otherwise.

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="QTI3-order" title="Order Interaction Example" time-dependent="false" xml:lang="en-US"> <qti-response-declaration identifier="RESPONSE" cardinality="ordered" base-type="identifier"> <qti-correct-response> <qti-value>DriverC</qti-value> <qti-value>DriverA</qti-value> <qti-value>DriverB</qti-value> </qti-correct-response> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float" /> <qti-item-body> <p>The following F1 drivers finished on the podium in the first ever Grand Prix of Bahrain.</p> <qti-order-interaction response-identifier="RESPONSE" orientation="horizontal"> <qti-prompt> <p>Rearrange them into the correct finishing order.</p> </qti-prompt> <qti-simple-choice identifier="DriverA">Rubens Barrichello</qti-simple-choice> <qti-simple-choice identifier="DriverB">Jenson Button</qti-simple-choice> <qti-simple-choice identifier="DriverC">Michael Schumacher</qti-simple-choice> </qti-order-interaction> </qti-item-body> <qti-response-processing template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/match_correct.xml"/> </qti-assessment-item>

The shared vocabulary for the Order Interaction is intended to provide more precision when describing:

1. Target Labels
2. Target Label Suffixes
3. Choices | Targets Container Positioning
4. Choices Container Widths
5. Custom max|min -associations Messages

Go to the QTI 3 Standardized Shared Vocabulary and CSS section on Order Interaction for full details.

3.2.11 Graphic Order Interaction

A GraphicOrderInteraction.Type (qti-associate-interaction) is a graphic interaction with a corresponding set of choices that are defined as areas of the graphic image. The candidate's task is to impose an ordering on the areas (hotspots). The order hotspot interaction should only be used when the spatial relationship of the choices with respect to each other (as represented by the graphic image) is important to the needs of the item.

Otherwise, Order interaction should be used instead with separate material for each option. The delivery engine must clearly indicate all defined area(s) of the image.

Graphic Order Interaction Attributes (element: qti-graphic-order-interaction)

The sub-element sequence for the qti-graphic-order-interaction:

1. either img, picture, or object (must have only 1, object is deprecated)
2. qti-hotspot-choice (at least 1)

HotspotChoice Attributes (element: qti-hotspot-choice)

The graphic order interaction must be bound to a response variable with a base-type of identifier and ordered cardinality.

Example: Demonstrates qti-graphic-order-interaction

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="QTI3-graphic-order" title="Graphic Order Interaction Example" time-dependent="false" xml:lang="en-US"> <qti-response-declaration identifier="RESPONSE" cardinality="ordered" base-type="identifier"> <qti-correct-response> <qti-value>A</qti-value> <qti-value>D</qti-value> <qti-value>C</qti-value> <qti-value>B</qti-value> </qti-correct-response> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float" /> <qti-item-body> <p>Lorna is flying back home to the UK. Ideally, she would like to fly in directly to her home town of Glasgow. Edinburgh is her second choice and, if necessary, she could fly into London and pick up an internal connecting flight. Although she has been offered a cheap flight to Manchester it remains her least favourite option as connecting flights to Glasgow are not very reliable from there.</p> <qti-graphic-order-interaction response-identifier="RESPONSE"> <qti-prompt>Mark the airports shown on the map according to Lorna's preferences.</qti-prompt> <img src="images/ukair.png" width="206" height="280" alt="map of airports of the United Kingdom"/> <qti-hotspot-choice shape="circle" coords="78,102,8" identifier="A" aria-label="Airport A" /> <qti-hotspot-choice shape="circle" coords="117,171,8" identifier="B" aria-label="Airport B" /> <qti-hotspot-choice shape="circle" coords="166,227,8" identifier="C" aria-label="Airport C" /> <qti-hotspot-choice shape="circle" coords="100,102,8" identifier="D" aria-label="Airport D" /> </qti-graphic-order-interaction> </qti-item-body> <qti-response-processing template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/match_correct.xml" /> </qti-assessment-item>

3.2.12 Associate Interaction

An AssociateInteraction.Type (qti-associate-interaction) is a block interaction that presents candidates with a number of  choices and allows them to create associations between them.

AssociateInteraction Attributes (element: qti-associate-interaction)

The sub-element of qti-associate-interaction is qti-simple-associable-choice, where there must be at least one qti-simple-associable-choice.

SimpleAssociableChoice Attributes (element: qti-simple-associable-choice)

The qti-associate-interaction must be bound to a response variable with base-type pair and either single or multiple cardinality.

Example: Demonstrates qti-associate-interaction allowing for 3 pairings

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="QTI3-associate" title="Classic Associate Interaction Example" time-dependent="false" xml:lang="en-US"> <qti-response-declaration identifier="RESPONSE" cardinality="multiple" base-type="pair"> <qti-correct-response> <qti-value>A P</qti-value> <qti-value>C M</qti-value> <qti-value>D L</qti-value> </qti-correct-response> <qti-mapping default-value="0"> <qti-map-entry map-key="A P" mapped-value="2" /> <qti-map-entry map-key="C M" mapped-value="1" /> <qti-map-entry map-key="D L" mapped-value="1" /> </qti-mapping> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float" /> <qti-item-body> <qti-associate-interaction response-identifier="RESPONSE" max-associations="3"> <qti-prompt> Hidden in this list of characters from famous Shakespeare plays are three pairs of rivals. Can you match each character to his adversary? </qti-prompt> <qti-simple-associable-choice identifier="A" match-max="1"> Antonio </qti-simple-associable-choice> <qti-simple-associable-choice identifier="C" match-max="1"> Capulet </qti-simple-associable-choice> <qti-simple-associable-choice identifier="D" match-max="1"> Demetrius </qti-simple-associable-choice> <qti-simple-associable-choice identifier="L" match-max="1"> Lysander </qti-simple-associable-choice> <qti-simple-associable-choice identifier="M" match-max="1"> Montague </qti-simple-associable-choice> <qti-simple-associable-choice identifier="P" match-max="1"> Prospero </qti-simple-associable-choice> </qti-associate-interaction> </qti-item-body> <qti-response-processing template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/map_response.xml" /> </qti-assessment-item>

3.2.13 Graphic Associate Interaction

A GraphicAssociateInteraction.Type (qti-graphic-associate-interaction) is a graphic interaction with a corresponding set of choices that are defined as areas of the graphic image. The candidate's task is to associate the areas (hotspots) with each other. The graphic associate interaction should only be used when the graphical relationship of the choices with respect to each other (as represented by the graphic image) is important to the needs of the item. Otherwise, an Associate Interaction should be used instead with separate material for each option. The delivery engine must clearly indicate all defined area(s) of the image.

AssociateInteraction Attributes (element: qti-associate-interaction)

The sub-element sequence:

1. img, picture, or object (limited to a single occurrence, object is deprecated)
2. qti-associable-hotspot (at least 1)

AssociableHotspot Attributes (element: qti-associable-hotspot)

The qti-graphic-associate-interaction must be bound to a response variable with base-type pair and either single or multiple cardinality.

Example: Demonstrates qti-graphic-associate-interaction

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_itemv3p0p1_v1p0.xsd" identifier="example-graphic-assoc-1" title="Graphic Associate Example 1" time-dependent="false" xml:lang="en-US"> <qti-response-declaration identifier="RESPONSE" cardinality="multiple" base-type="pair"> <qti-correct-response> <qti-value>C B</qti-value> <qti-value>C D</qti-value> </qti-correct-response> <qti-mapping lower-bound="0" default-value="0"> <qti-map-entry map-key="A B" mapped-value="-1" /> <qti-map-entry map-key="A C" mapped-value="-1" /> <qti-map-entry map-key="A D" mapped-value="-1" /> <qti-map-entry map-key="B D" mapped-value="-1" /> <qti-map-entry map-key="B C" mapped-value="1" /> <qti-map-entry map-key="C D" mapped-value="1" /> </qti-mapping> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float" /> <qti-item-body> <p> Frizz, a new low cost airline, already operates a service connecting Manchester and Edinburgh but has recently opened two new routes: a service between London and Edinburgh and one between London and Manchester. </p> <qti-graphic-associate-interaction response-identifier="RESPONSE" max-associations="3"> <qti-prompt>Mark the airline's new routes on the airport map.</qti-prompt> <img src="images/ukair.svg" alt="Map of United Kingdom airports" width="206" height="280" /> <qti-associable-hotspot shape="circle" coords="78,102,10" identifier="A" match-max="3"/> <qti-associable-hotspot shape="circle" coords="117,171,10" identifier="B" match-max="3"/> <qti-associable-hotspot shape="circle" coords="166,227,10" identifier="C" match-max="3"/> <qti-associable-hotspot shape="circle" coords="100,102,10" identifier="D" match-max="3"/> </qti-graphic-associate-interaction> <p class="interaction-instruction" >Drag the route markers by their ends to connect the airports.</p> </qti-item-body> <qti-response-processing template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/map_response.xml" /> </qti-assessment-item>

Alternatively, you may wish to use the picture element to reference the source for the more highly compressed WebP version and with a PNG alternative within the img element for browsers that do not support WebP.

Example: Demonstrates qti-graphic-associate-interaction with picture element

<?xml version="1.0" encoding="UTF-8"?>
<qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0
  https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_itemv3p0p1_v1p0.xsd"
  identifier="example-graphic-assoc-1alt" title="Alternative Graphic Associate Example" 
xml:lang="en-US" time-dependent="false">
<qti-response-declaration identifier="RESPONSE" cardinality="multiple" base-type="pair">
    <qti-correct-response>
      <qti-value>C B</qti-value>
      <qti-value>C D</qti-value>
    </qti-correct-response>
    <qti-mapping lower-bound="0" default-value="0">
      <qti-map-entry map-key="A B" mapped-value="-1" />
      <qti-map-entry map-key="A C" mapped-value="-1" />
      <qti-map-entry map-key="A D" mapped-value="-1" />
      <qti-map-entry map-key="B D" mapped-value="-1" />
      <qti-map-entry map-key="B C" mapped-value="1" />
      <qti-map-entry map-key="C D" mapped-value="1" />
    </qti-mapping>
  </qti-response-declaration>
  <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float" />
    <qti-item-body>
      <p>
        Frizz, a new low cost airline, already operates a service
        connecting Manchester and Edinburgh but has recently opened two
        new routes: a service between London and Edinburgh and one
        between London and Manchester.
      </p>
      <qti-graphic-associate-interaction response-identifier="RESPONSE" max-associations="3">
        <qti-prompt>
          Mark the airline's new routes on the airport map:
        </qti-prompt>

        <picture>
         <source srcset="images/ukair.webp" type="image/webp"/>
         <img src="images/ukair.png" alt="Map of United Kingdom airports" width="206" height="280" />
        </picture>

        <qti-associable-hotspot shape="circle" coords="78,102,10" identifier="A" match-max="3"/>
        <qti-associable-hotspot shape="circle" coords="117,171,10" identifier="B" match-max="3"/>
        <qti-associable-hotspot shape="circle" coords="166,227,10" identifier="C" match-max="3"/>
        <qti-associable-hotspot shape="circle" coords="100,102,10" identifier="D"  match-max="3"/>
      </qti-graphic-associate-interaction>
  <p>Drag the route markers by their ends to connect the airports. </p>
    </qti-item-body>
  <qti-response-processing 
   template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/map_response.xml" />  
  </qti-assessment-item>

3.2.14 Graphic Gap Match Interaction

A GraphicGapMatchInteraction.Type (qti-graphic-gap-match-interaction) is a graphical interaction with a set of gaps that are defined as areas (hotspots) of the graphic image and an additional set of gap choices that are defined outside the image. The candidate must associate the gap choices with the gaps in the image and be able to review the image with the gaps filled in context, as indicated by their choices.

Care should be taken when designing these interactions to ensure that the gaps in the image are a suitable size to receive the required gap choices. It must be clear to the candidate which hotspot each choice has been associated with. When associated, choices must appear wholly inside the gaps if at all possible and, where overlaps are required, should not hide each other completely. If the candidate indicates the association by positioning the choice over the gap (e.g. drag and drop) the system should 'snap' it to the nearest position that satisfies these requirements.

GraphicGapMatchInteraction Attributes (element: qti-graphic-gap-match-interaction)

The sequence of elements within the qti-graphic-gap-match-interaction is:

• qti-prompt
• either img, picture, or object (deprecated)
• qti-gap-text
• qti-gap-img
• qti-associable-hotspot

GapText Attributes (element: qti-gap-text)

GapImg Attributes (element: qti-gap-img)

AssociableHotspot Attributes (element: qti-associable-hotspot)

The graphic-gap-match-interaction must be bound to a response variable with base-type directedPair and multiple cardinality. The choices represent the source of the pairing and the gaps in the image (the hotspots) the targets. Unlike the simple GapMatchInteraction, each gap can have several choices associated with it if desired, furthermore, the same choice may be associated with an qti-associable-hotspot multiple times, in which case the corresponding directed pair appears multiple times in the value of the response variable.

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="graphic-gap-match-item1" title="Q8 GGM Images - Airport Tags" adaptive="false" time-dependent="false" xml:lang="en-US" > <qti-response-declaration identifier="RESPONSE" cardinality="multiple" base-type="directedPair"> <qti-correct-response> <qti-value>GLA A</qti-value> <qti-value>EDI B</qti-value> <qti-value>MAN C</qti-value> </qti-correct-response> <qti-mapping default-value="-1" lower-bound="0"> <qti-map-entry map-key="GLA A" mapped-value="1"/> <qti-map-entry map-key="EDI B" mapped-value="1"/> <qti-map-entry map-key="MAN C" mapped-value="1"/> </qti-mapping> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float"/> <qti-item-body> <p>The International Air Transport Association assigns three-letter codes to identify airports worldwide. For example, London Heathrow has code LHR.</p> <qti-graphic-gap-match-interaction max-associations="0" response-identifier="RESPONSE" class="qti-choices-left" > <qti-prompt> <p>Some of the labels on the following diagram are missing: can you identify the correct three-letter codes for the unlabelled airports?</p> </qti-prompt> <img src="images/ukairtags2024.png" width="305" height="390" alt="Outline map of the United Kingdom" /> <qti-gap-img identifier="CBG" match-max="1"> <img src="images/cbg.png" width="53" height="29" alt="The initials CBG" /> </qti-gap-img> <qti-gap-img identifier="EBG" match-max="1"> <img src="images/ebg.png" width="53" height="29" alt="The initials EBG" /> </qti-gap-img> <qti-gap-img identifier="EDI" match-max="1"> <img src="images/edi.png" width="53" height="29" alt="The initials EDI" /> </qti-gap-img> <qti-gap-img identifier="GLA" match-max="1"> <img src="images/gla.png" width="53" height="29" alt="The initials GLA" /> </qti-gap-img> <qti-gap-img identifier="MAN" match-max="1"> <img src="images/man.png" width="53" height="29" alt="The initials MAN" /> </qti-gap-img> <qti-gap-img identifier="MCH" match-max="1"> <img src="images/mch.png" width="53" height="29" alt="The initials MCH" /> </qti-gap-img> <qti-associable-hotspot identifier="A" match-max="1" shape="rect" coords="11,122,64,151" /> <qti-associable-hotspot identifier="B" match-max="1" shape="rect" coords="187,105,240,134" /> <qti-associable-hotspot identifier="C" match-max="1" shape="rect" coords="91,206,144,235" /> </qti-graphic-gap-match-interaction> </qti-item-body> <qti-response-processing template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/map_response.xml"/> </qti-assessment-item>

The shared vocabulary for the Graphic Gap Match Interaction is intended to provide more precision when describing:

1. Positioning of the Gap Choices container with respect to the image containing the hotspots.
2. Gap Choices container width.
3. Associable Hotspot Selections theming.
4. Custom max|min-associations message overrides.

Go to the QTI 3 Standardized Shared Vocabulary and CSS section on Graphic Gap Match Interaction for full details.

3.2.15 Media

The MediaInteraction.Type (qti-media-interaction) enables measurement of the number of times the media object was experienced.  This quantity is reported in the value of the interaction's response variable.

MediaInteraction Attributes (element: qti-media-interaction)

The sub-elements include:

• audio
• video
• object (deprecated)

The qti-media-interaction must be bound to a response variable of base-type integer and single cardinality.

Note that for the audio and video elements in QTI 3 markup, the "controls" attribute MUST include a value for the attribute to be valid XML. As per the HTML 5 specification, the way to exclude controls is to explicitly not include the attribute in the audio or video element. In QTI 3, valid values to include controls are "controls" (as per the HTML specification) or "true" (the more traditional boolean value for XML). So <video> would mean the controls are not provided to the candidate (as in the example below), and <video controls="controls"> would indicate the candidate should be provided with media controls.

Example: Demonstrates qti-media-interaction

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="media-example-1" title="Media Interaction Example" adaptive="false" time-dependent="false" xml:lang="en-US" > <qti-response-declaration base-type="integer" cardinality="single" identifier="RESPONSE_1"/> <qti-item-body> <qti-media-interaction autostart="false" loop="false" response-identifier="RESPONSE_1" max-plays="3" > <qti-prompt>Play this video.</qti-prompt> <video width="320" height="240" > <source src="images/bubble.mp4" type="video/mp4"/> <source src="images/bubble.ogv" type="video/ogv"/> </video> </qti-media-interaction> </qti-item-body> </qti-assessment-item>

3.2.16 Position Object Interaction

The PositionObjectInteraction.Type (qti-position-object-interaction) consists of a single image which must be positioned on another graphic image (the stage) by the candidate. Like Select Point Interaction, the associated response may have a qti-area-mapping that scores the response on the basis of comparing it against predefined areas but the delivery engine must not indicate these areas of the stage. Only the actual position(s) selected by the candidate shall be indicated.

PositionObjectInteraction Attributes (element: qti-position-object-interaction)

The sub-element for the qti-position-object-interaction is either the HTML "img" or "picture" element. The object element is deprecated in QTI 3.

The qti-position-object-interaction must be bound to a response variable with a base-type of point and single or multiple cardinality. The point records the coordinates, with respect to the stage, of the centre point of the image being positioned.

Position Object Interaction, has a required parent, the qti-position-object-stage, which is a graphic image (represented as an "object"), on top of which the Position Object Interaction image is to be positioned. A single qti-position-object-stage may have several Position Object Interactions as child elements, representing several objects to be positioned on the same "stage".

Example: Demonstrates qti-position-object-interaction

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="position-object-1" title="Position Object, those UK airports again!" adaptive="false" time-dependent="false" xml:lang="en-US" > <qti-response-declaration identifier="RESPONSE" cardinality="multiple" base-type="point"> <qti-correct-response> <!-- Manchester (MAN) --> <qti-value>118 184</qti-value> <!-- London Heathrow (LHR) --> <qti-value>150 235</qti-value> <!-- Edinburgh (EDI) --> <qti-value>96 114</qti-value> </qti-correct-response> <qti-area-mapping default-value="0"> <qti-area-map-entry shape="circle" coords="118,184,12" mapped-value="1"/> <qti-area-map-entry shape="circle" coords="150,235,12" mapped-value="1"/> <qti-area-map-entry shape="circle" coords="96,114,12" mapped-value="1"/> </qti-area-mapping> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float"/> <qti-item-body> <p>When flying into the UK, you may well find yourself landing at Edinburgh, Manchester or London Heathrow; but where are these airports actually located? </p> <qti-position-object-stage> <img src="images/uk.svg" alt="Map of airports of the United Kingdom" width="206" height="280" /> <qti-position-object-interaction response-identifier="RESPONSE" max-choices="3"> <img src="images/airplane.png" alt="Icon of an airplane" width="30" height="30" /> </qti-position-object-interaction> </qti-position-object-stage> <p>Drag the airport marker to the city locations on the map.</p> </qti-item-body> <qti-response-processing template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/map_response_point.xml"/> </qti-assessment-item>

3.2.17 Select Point Interaction

The SelectPointInteraction.Type (qti-select-point-interaction) is a graphic interaction. The candidate's task is to select one or more points. The associated response may have an qti-area-mapping  that scores the response on the basis of comparing it against predefined areas but the delivery engine must not indicate these areas of the image. Only the actual point(s) selected by the candidate shall be indicated.

SelectPointInteraction Attributes (element: qti-select-point-interaction)

The sub-element for the qti-select-point-interaction is either the HTML "img" or "picture" element. The object element is deprecated in QTI 3.

The select point interaction must be bound to a response variable with a base-type of point and single or multiple cardinality.

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="select-point-item_1" title="Classic Where is Edinburgh Example" adaptive="false" time-dependent="false" xml:lang="en-US" > <qti-response-declaration identifier="RESPONSE" cardinality="single" base-type="point"> <qti-correct-response> <qti-value>93 111</qti-value> </qti-correct-response> <qti-area-mapping default-value="0" > <qti-area-map-entry shape="circle" coords="93,111,16" mapped-value="1"/> </qti-area-mapping> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float"/> <qti-item-body> <qti-select-point-interaction max-choices="1" response-identifier="RESPONSE" > <qti-prompt> <p>Mark Edinburgh on this map of the United Kingdom.</p> </qti-prompt> <img width="196" height="280" src="images/uk_green.png" alt="A map of the United Kingdom" /> </qti-select-point-interaction> </qti-item-body> <qti-response-processing template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/map_response_point.xml"/> </qti-assessment-item>

3.2.18 Slider Interaction

The SliderInteraction.Type (qti-slider-interaction) presents the candidate with a control for selecting a numerical value between a lower and upper bound. It must be bound to a response variable with single cardinality with a base-type of either integer or float.

Note that a slider interaction does not have a default or initial position except where specified by a default value for  the associated response variable. The currently selected value, if any, must be clearly indicated to the candidate.

Because a slider interaction does not have a default or initial position, except where specified by a default value for the associated response variable, it is difficult to distinguish between an intentional response that corresponds to the slider's initial position and a NULL response. As a workaround, slider interaction items have to either a) not count NULL responses (i.e. count all responses as intentional) or b) include a 'skip' button and count its activation combined with a response variable that is equal to the slider's initial position as a NULL response.

There are six attributes for the qti-slider-interaction where the lower-bound and upper-bound are required attributes:

Slider Interaction Attributes (element: qti-slider-interaction)

Example: Demonstrates qti-slider-interaction

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="slider-1" title="Slider Interaction – Water" adaptive="false" time-dependent="false" xml:lang="en-US" > <qti-response-declaration identifier="RESPONSE" cardinality="single" base-type="integer"> <qti-correct-response> <qti-value>70</qti-value> </qti-correct-response> </qti-response-declaration> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float"/> <qti-item-body> <qti-slider-interaction response-identifier="RESPONSE" lower-bound="0" upper-bound="100" step="10" orientation="horizontal" > <qti-prompt> Roughly (to the nearest 10%) what percentage of the Earth's surface is covered in water? </qti-prompt> </qti-slider-interaction> </qti-item-body> <qti-response-processing template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/map_response.xml"/> </qti-assessment-item>

3.2.19 Upload

The UploadInteraction.Type (qti-upload-interaction) allows the candidate to upload a pre-prepared file representing their response.

The qti-upload-interaction must be bound to a response variable with base-type  file and single cardinality.

UploadInteraction Attributes (element: qti-upload-interaction)

Example: Demonstrates qti-upload-interaction

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="upload-interaction" title="Upload Chocolate Spreadsheet" adaptive="false" time-dependent="false" xml:lang="en-US" > <qti-response-declaration identifier="RESPONSE" cardinality="single" base-type="file" /> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float"/> <qti-item-body> <p>A chocolate factory produces several types of chocolate, some of which have nut centres. The chocolates are mixed together and are randomly packed into cartons of ten.</p> <qti-upload-interaction response-identifier="RESPONSE" > <qti-prompt> <p>Build a spreadsheet to simulate 50 cartons of chocolates when each carton contains 10 chocolates, and when one-seventh of the chocolates have nut centres. Your spreadsheet should include 50 rows representing the 50 cartons, each row containing 10 columns to represent the chocolates.</p> </qti-prompt> </qti-upload-interaction> </qti-item-body> </qti-assessment-item>

A chocolate factory produces several types of chocolate, some of which have nut centres. The chocolates are mixed together and are randomly packed into cartons of ten. Build a spreadsheet to simulate 50 cartons of chocolates when each carton contains 10 chocolates, and when one-seventh of the chocolates have nut centres. Your spreadsheet should include 50 rows representing the 50 cartons, each row containing 10 columns to represent the chocolates.

3.2.20 Drawing Interaction

The DrawingInteraction.Type (qti-drawing-interaction) allows the candidate to use a set of drawing tools to modify a given graphical image (the canvas).  It must be bound to a response variable with base type file and single cardinality.

DrawingInteraction Attributes (element: qti-drawing-interaction)

The sub-element of the qti-drawing-interaction are the HTML elements img, picture, or object. The image specified within one of the aforementioned elements acts as the canvas on which the drawing takes place. It is best practice to use the img or picture elements for this interaction. If using the deprecated object element it MUST be of an image type, as specified by the type attribute.

Example: Demonstrates qti-drawing-interaction

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="drawing-interaction-1" title="Draw an Angle" adaptive="false" time-dependent="false" xml:lang="en-US" > <qti-response-declaration identifier="RESPONSE" cardinality="single" base-type="file" /> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float"/> <qti-item-body> <qti-drawing-interaction response-identifier="RESPONSE"> <qti-prompt> <p>Use the compass provided to bisect the angle <em>PQR</em> in the figure below.</p> </qti-prompt> <picture> <source srcset="images/anglePQR.svg" media="(min-width: 600px)" type="image/svg" /> <img src="images/anglePQR_HiRes.jpg" alt="drawing of angle PQR where point P connects with point Q and point Q connects to point R and length of PQ equals the length of QR" width="322" height="260" /> </picture> </qti-drawing-interaction> </qti-item-body> </qti-assessment-item>

3.2.21 End Attempt Interaction

End Attempt Interaction is a special interaction which immediately ends the current attempt on an assessment item.  It may be used, for example, to allow the candidate to request a hint or model solution, or in an adaptive item to let the candidate display feedback or to move to the next in a series of interactions in the item.

EndAttemptInteraction Attributes (element: qti-end-attempt-interaction)

Example: Demonstrates qti-end-attempt-interaction with a Hint

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="end-attempt-example-1" title="End Attempt Example" adaptive="false" time-dependent="false" xml:lang="en-US" > <qti-response-declaration identifier="RESPONSE" cardinality="single" base-type="identifier"> <qti-correct-response> <qti-value>C</qti-value> </qti-correct-response> </qti-response-declaration> <qti-response-declaration identifier="HINTREQUEST" cardinality="single" base-type="boolean"/> <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float"/> <qti-outcome-declaration identifier="FEEDBACK" cardinality="single" base-type="identifier"/> <qti-item-body> <qti-choice-interaction response-identifier="RESPONSE" shuffle="false" max-choices="1"> <qti-prompt>Who was the President of Mexico from 2000 to 2006?</qti-prompt> <qti-simple-choice identifier="A">George W Bush</qti-simple-choice> <qti-simple-choice identifier="B">Tony Blair</qti-simple-choice> <qti-simple-choice identifier="C">Vicente Fox</qti-simple-choice> <qti-simple-choice identifier="D">Ariel Sharon</qti-simple-choice> </qti-choice-interaction> <p> <qti-end-attempt-interaction response-identifier="HINTREQUEST" title="Show Hint"/> </p> <qti-feedback-block identifier="HINT" outcome-identifier="FEEDBACK" show-hide="show"> <qti-content-body> Tony lived in the United Kingdom and George lived in Washington, DC. </qti-content-body> </qti-feedback-block> </qti-item-body> <qti-response-processing> <qti-set-outcome-value identifier="FEEDBACK"> <qti-base-value base-type="identifier">NOHINT</qti-base-value> </qti-set-outcome-value> <qti-response-condition> <qti-response-if> <qti-variable identifier="HINTREQUEST"/> <qti-set-outcome-value identifier="FEEDBACK"> <qti-base-value base-type="identifier">HINT</qti-base-value> </qti-set-outcome-value> </qti-response-if> <qti-response-else> <qti-response-condition> <qti-response-if> <qti-match> <qti-variable identifier="RESPONSE"/> <qti-correct identifier="RESPONSE"/> </qti-match> <qti-set-outcome-value identifier="SCORE"> <qti-base-value base-type="float">1</qti-base-value> </qti-set-outcome-value> </qti-response-if> <qti-response-else> <qti-set-outcome-value identifier="SCORE"> <qti-base-value base-type="float">0</qti-base-value> </qti-set-outcome-value> </qti-response-else> </qti-response-condition> </qti-response-else> </qti-response-condition> </qti-response-processing> </qti-assessment-item>

3.2.22 Custom Interaction

The CustomInteraction.Type (qti-custom-interaction) is a deprecated feature in QTI 3. It is recommended to use Portable Custom Interaction (next section) in place of the custom interaction. The Custom Interaction provides an opportunity for delivery platform-specific extensibility of this specification to include support for interactions not currently built into the QTI specification.  This can be used, for example, to develop technology-enhanced items.

As the user interface and behavior of a qti-custom-interaction are custom, there is no predefined shared vocabulary for qti-custom-interaction.  However if a qti-custom-interaction implements a feature or behavior in a way which is consistent with how that has been defined for the pre-defined interaction types then it may use qti- prefixed class names to indicate it supports a behaviour consistent with the use of that shared vocabulary elsewhere in this specification; e.g., a qti-custom-interaction which supports text entry by the candidate may support the qti-input-width set of classes to control the visible width allocated to display of the candidate's input.

CustomInteraction Attributes (element: qti-custom-interaction)

Example: Demonstrates qti-custom-interaction

<?xml version="1.0" encoding="UTF-8"?> <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="custom-deprecated-example-1" title="Custom Interaction Example" adaptive="false" time-dependent="false" xml:lang="en-US" > <qti-response-declaration cardinality="single" base-type="string" identifier="RESPONSE">   <qti-correct-response>     <qti-value>3/8</qti-value>   </qti-correct-response> </qti-response-declaration> <qti-outcome-declaration cardinality="single" base-type="float" identifier="SCORE"/> <qti-item-body>   <p>     A pie is divided into quarters. Each slice is then divided in half. One half of the     pie is eaten at lunch. One slice is eaten at snack time.   </p>   <p>     Use the Fraction Tool below to shade the portion of the pie that is left. The Fraction Tool     buttons divide the circle into fewer or more pieces. Pieces of the circle can be     shaded by selecting them.   </p>   <!-- docking div for the custom interaction -->   <div id="myfractionmodel"></div> <qti-custom-interaction class="tei-fractionmodel" response-identifier="RESPONSE">     <!-- Not required to kebab-case or use qti- as this custom-option is completely          custom element.  However, best practice in QTI 3 is to kebab-case it for          webcomponent-friendliness.     -->     <custom-option><![CDATA[       {         dockingDivId: 'myfractionmodel',         alignment: 'center',         models: [{             active: true,           startSegments: 2,           minSegments: 1,           maxSegments: 12, selectedSegments: [],           text: 'The Fraction Tool',           style: {             radius: 150,             fillColor: '#FF0000',             strokeColor: '#000000',             strokeWeight: 2           }         }]       }     ]]></custom-option> </qti-custom-interaction> </qti-item-body> </qti-assessment-item>

3.2.23 Portable Custom Interaction (PCI)

The PortableCustomInteraction.Type (qti-portable-custom-interaction) allows an item author with the support of a PCI module developer the ability to render an interaction with a custom user interface and behaviors by providing custom Javascript code supporting the interaction. This can be used, for example, to develop technology-enhanced items.

The Javascript code which implements a PCI may be included with the item in the content package or may reside elsewhere on the network. It will be loaded dynamically by the delivery engine when the item containing the PCI is presented.  These Javascript modules must be AMD (Asynchronous Module Definition) modules, and must conform to the PCI API, detailed later in this document.   The markup of a PCI may include any HTML5, MathML, and SSML elements supported elsewhere in QTI.  In addition, a PCI may contain feedback, template, and printed variable elements.  Finally, a special templateelement may be included. This may be used only in a PCI and is a container for any valid XML markup.

As the user interface and behavior of a PCI are custom, there is no predefined shared vocabulary for PCIs.  However if a PCI implements a feature or behavior in a way which is consistent with how that has been defined for the pre-defined interaction types then it MAY use qti- prefixed CSS class names to indicate it supports a behaviour consistent with the use of that shared vocabulary elsewhere in this specification; e.g. a PCI which supports text entry by the candidate may support the qti-input-width set of classes to control the visible width allocated to display of the candidate's input.

PCI allows for referencing a stylesheet using the qti-stylesheet element, where the stylesheet is specific to the code referenced within the PCI. PCI also allows for the inclusion of catalog information that is specific to the PCI. PCI is the only interaction that allows for these elements within the interaction. All other interactions would use the item level stylesheet reference and the item level catalog node.

There is a detailed example of a PCI in Section 3.7.12 .  Consequently, example definitions and expected renderings are not provided here.

3.4.1 Response Processing Rules

Response processing consists of a sequence of rules that are carried out, in order, by the response processor. A ResponseCondition  rule is a special type of rule which contains sub-sequences of rules divided into responseIf , responseElseIf  and responseElse  sections. The response processor evaluates the expressions in the responseIf and responseElseIf elements to determine which sub-sequence to follow. In this example, the responseIf section is followed only if the variable with identifier RESPONSE matches the correct response declared for it. The responseElseIf section is followed if RESPONSE matches the response explicitly given (which places the correct driver 1st but confuses the other two). Finally, the responseElse section is followed if neither of the previous two apply. The responseElse section has no corresponding expression of course. The qti-set-outcome-value  element is just a ResponseRule  that tells the processor to set the value of the specified outcome variable to the value of the expression it contains.

The qti-variable , qti-correct  and qti-base-value  elements are examples of simple expressions. In other words, expressions that are indivisible. In contrast, the qti-match  and qti-ordered  elements are examples of operators. Operators are expressions that combine other expressions to form new values. For example, match is used to form a boolean depending on whether or not two expressions have matching values.

3.4.2 Fixed and General Response Processing

There are two forms of response processing:

1. Fixed Template Response Processing
2. General Response Processing.

In  "fixed template" response processing, the processing to be done is identified by a "template name".   There are three standard template names, and a delivery engine may define additional template names.   For simple scenarios, the "match_correct" and "map_response" standard templates may be used because this maximizes interoperability.   All conformant delivery systems are required to provide response processing as defined by these two templates, while there is no assurance that a template other than these two will be supported, or that general response processing will be supported.

The three standard "fixed" response processing templates are:

For "general" response processing, QTI defines an XML-based Domain Specific Language (DSL) with a large number of commands and operators for computing and setting template and outcome variables. General response processing is necessary for more complex items, such as items generated from templates, adaptive items involving feedback, and composite items.

The same Domain Specific Language is also used for Outcome Processing, Template Defaults, Constraints, and Processing, and for evaluating Preconditions and Branch Rules.

3.4.3 Partial Scoring

Please see section 3.3 Composite Items for an example of response processing that implements partial scoring.

3.4.4 Conformance

It is possible to define the effect of the standard templates using the "general" response processing DSL, but it is not required that a QTI 3 Entry-level delivery system implement the standard templates through support of the DSL. A "built-in" implementation of the standard templates is sufficient for conformance in a QTI 3 Entry-level delivery system.

At the QTI 3 Core-level of conformance, a delivery system is required to support enough of the response processing DSL to be able to load and execute at least the "match_correct" and "map_response" standard templates, as well as other templates or inline response processing blocks using the same subset of the Domain Specific Language as these two standard templates.  For convenience and performance, a QTI 3 Core-level delivery system may still also use the "built-in" approach for some of the templates which it supports, in addition to supporting the response processing language.

3.4.5 External Scoring

In some cases, response processing is undertaken by external systems or human scorers. This is typically the case for items asking candidates to write an essay. However, it might be important for external systems or human scorers to know which outcome value has to be set to derive an appropriate score.

External Scoring Example

<?xml version="1.0" encoding="UTF-8"?>
<qti-assessment-item
     xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0
    https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd" identifier="essay"
     title="Write an essay" adaptive="false" time-dependent="false" xml:lang="en-US">
  <qti-response-declaration identifier="RESPONSE" cardinality="single" base-type="string"/>
  <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float"  external-scored="human"/>
  <qti-item-body>
     <p class="stem">
        In the classroom, we discovered Martin Luther King Jr. and his devotion.
     </p>
     <qti-extended-text-interaction response-identifier="RESPONSE">
        <qti-prompt>Write an abstract about the life of this historical figure.</qti-prompt>
     </qti-extended-text-interaction>
  </qti-item-body>
  </qti-assessment-item>

This example describes an item with a single qti-extended-text-interactionasking the candidate to write an essay. As the item does not contain qti-response-processing, the SCORE qti-outcome-declaration has its external-scored attribute value set to "human". This makes QTI compliant systems aware that the final value of SCORE has to be set by a human scorer after the Item Session has closed.

3.6.1 Custom Styles

For QTI 3, the best practice is to avoid using custom styles, and instead use the Shared CSS Vocabulary as described above. By using the Shared CSS style names, Test Delivery Systems can optimize the rendering experience for accessibility and for design responsiveness.

However, as a last resort, custom stylesheets may be injected into an item and other QTI content, such as tests, stimuli, and feedback, rubric, and template blocks, using the qti-stylesheet element:

...
<qti-assessment-item>
  <qti-stylesheet href="samples/Quizzco-Custom-Styles.css" type="text/css"/>
  <qti-item-body>
    <div id="Quizzco__item123" class="qti-layout-row">
      ...
     </div>
  </qti-item-body>
</qti-assessment-item>

As in earlier versions of QTI, it is not required for conformance for delivery systems to support the qti-stylesheet element -- a further reason why stylesheet injection is likely not to be interoperable.  Notwithstanding these issues, if your implementation will be using stylesheets,  QTI 3 recommends the use of CSS 3 stylesheets. For more information on CSS 3 stylesheets, see the W3C documentation at https://www.w3schools.com/css/default.asp  .

The best practice convention in QTI 3 is that stylesheets referenced within an AssssmentItem file apply to the item itself, and are not assumed to apply to associated content such as stimulus ( qti-assessment-stimulus) or rubric blocks ( qti-rubric-block), both of which can have their own associated stylesheets. An item's stylesheets are assumed to apply to content within qti-item-body, qti-catalog-info,  as well as to any content generated from the use of feedback or templates. Any included content using XInclude that is placed within the qti-item-body, qti-catalog-info, and qti-modal-feedback, or qti-template-block generated content is also assumed to be covered by the stylesheet reference made within an item.

It is the responsibility of an item author to limit the scope of an injected stylesheet to the content with which it is associated. Because of the way CSS scoping is defined, this is admittedly difficult.  The following describes some approaches to limiting CSS scope:

• Use class naming conventions. Use a naming convention for CSS classes which includes a prefix with an item vendor-specific code, and which is likely to make custom  class names globally unique.
• Avoid bare element or attribute selectors. Avoid CSS style rules which apply broadly, such as those using "bare" element or attribute selectors.  Such rules are very likely to have a wider impact than intended.  Do not write rules like "div {color: red}". There are bound to be many other div'sin the document, not all of which should be red.  Instead, write ".vendorprefix-red { color: red }", and add the "vendorprefix-red" class to elements in the content which should be red.   Further note: at all costs, avoid specifying any colors in custom style definitions as these are practically guaranteed to result in an accessibility problem for the delivery platform.
• Do not assume defaults are in effect. Do not assume that CSS properties will have their default values.  If it is important for an element to have the default CSS property values, you should set the properties explicitly to the default values.
• Use id attributes and descendent selectors. QTI 3 allows the use of the id attribute on HTML5 elements.  It may be helpful to assign an id to a higher level element within the HTML content you are styling, such as a div,and write style rules against that id, possibly combined with descendant selectors. Choose ids that are likely to be globally unique so that other stylesheets in the environment don't affect your content, and vice-versa.  
• Do not assume order.Do not assume an injected stylesheet will be first or last, or in any particular position relative to other stylesheets in the delivery environment. That is, if item 1 injects stylesheet A, and the next item, item 2, injects stylesheet B, a delivery engine is free to insert the two stylesheets in any order, and an author cannot rely on stylesheet B being after stylesheet A. Even worse, stylesheet C, from somewhere else entirely, may land in between the two. In short, it is not really possible to rely on the CSS cascade between stylesheets, because the ultimate ordering of the stylesheets is not defined.
• Be aware of delivery system artifacts. You may observe that the HTML generated by the delivery system for QTI content includes HTML elements which were not in the original content.  This is because delivery engines commonly transform QTI content such as interactions, interaction components (e.g. qti-prompt, or qti-simple-choice), the qti-item-body, catalog cards, rubrics, feedback blocks, etc, into standard HTML elements, and these will end up as the parents, children, or siblings of the HTML elements placed in the item directly.  It is unwise to style these  system-generated elements or to rely on the generated structure in CSS style rules, because another delivery system, or even another version of the same delivery system, will generate a different structure.  Be aware when writing style rules that delivery system artifacts may appear "out of nowhere" and "get in the way" of sibling selectors, child selectors, adjacency selectors, first- and last-child pseudo-selectors, and the like.
• Do not depend on the stylesheet. To be interoperable, QTI content should fall back to a functional and accessible presentation even if the stylesheet is not injected. When injecting a stylesheet, authors should still rely on the CSS Shared Vocabulary for most of the styling and reserve the additional rules in the stylesheet  for styling which cannot be achieved through Shared Vocabulary.  An author should ensure that the content is acceptable with just Shared Vocabulary and be prepared for a stylesheet not to be injected at all.

Here is an example item, generated by a fictional vendor Quizzco, with some of these best practices applied:

Item with External Stylesheet Example

<?xml version="1.0" encoding="UTF-8"?>
<qti-assessment-item xmlns="http://www.imsglobal.org/xsd/qti/imsqtiasi_v3p0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0
https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd"
identifier="QTI3-custom-stylesheet" title="Custom Stylesheet" 
time-dependent="false" xml:lang="en-US">
  <qti-response-declaration base-type="identifier" cardinality="single" identifier="RESPONSE1">
      <qti-correct-response>
        <qti-value>Y</qti-value>
      </qti-correct-response>
    </qti-response-declaration>
  <qti-response-declaration base-type="identifier" cardinality="single" identifier="RESPONSE">
      <qti-correct-response>
        <qti-value>Y</qti-value>
      </qti-correct-response>
    </qti-response-declaration>
  <qti-outcome-declaration base-type="float" cardinality="single" identifier="SCORE"/>
  <qti-stylesheet href="samples/Quizzco-Custom-Styles.css" type="text/css"/>
  <qti-item-body>
   <div id="Quizzco__item123" class="qti-layout-row">
    <div class="qti-layout-col7">
     <p class="Quizzco__item__prompt">
      Identify the missing word in this famous quote from Shakespeare's Richard III.</p>
       <blockquote class="Quizzco__item__passage">
        Now is the winter of our discontent<br />
        Made glorious summer by this sun of 
        <qti-inline-choice-interaction response-identifier="RESPONSE">
          <qti-inline-choice identifier="G">Gloucester</qti-inline-choice>
          <qti-inline-choice identifier="L">Lancaster</qti-inline-choice>
          <qti-inline-choice identifier="Y">York</qti-inline-choice>
          </qti-inline-choice-interaction>;<br />
        And all the clouds that lour'd upon our house<br />
        In the deep bosom of the ocean buried.</p>
        </blockquote>
       </div>
   </div>
     </qti-item-body>
     <qti-response-processing 
   template="https://purl.imsglobal.org/spec/qti/v3p0/rptemplates/match_correct.xml"/>
   </qti-assessment-item>

External Stylesheet Example: Quizzco-Custom-Styles.css

#Quizzco__item123 Quizzco__item__prompt {
     all: initial;
     display: block;
     margin-block-start: 1em;
     text-align: start;
     padding: 5px;
     font-weight: normal;
  }

  #Quizzco__item123 Quizzco__item__passage {
     line-height: 1.3em;
     font-weight: bolder;
  }

3.7.1 Customized Response Processing

The qti-custom-operator extension mechanism allows the inclusion of custom, non-QTI response evaluation rules.  In general, such APIs are likely to be particular to a specific software library or programming language. For that reason, it is difficult to predict what form such custom operators will take, and, by extension, how to generalise functions or syntax between different custom operators.

By way of illustration, the following fragment illustrates the use of the Maxima engine as a response processing library via the qti-custom-operator element.

<qti-set-outcome-value identifier="oDummy">
     <qti-custom-operator class="org.qtitools.mathassess.ScriptRule" ma:simplify="false"
    ma:syntax="text/x-maxima" xmlns:ma="http://mathassess.qtitools.org/xsd/mathassess">
        <qti-base-value base-type="string"><[!CDATA[
              oInput:RESPONSE;        
              equalp(p,q):= block([simp:false], if p=q then return(true)
                   else return(false) )$
               isEqual: equalp(RESPONSE,mAns);
              equivp(p,q):= block([simp:true], if is(equal(p,q))=true then return(true)
                      else return(false) )$
              isEquiv: equivp(RESPONSE,mAns);        
              isRecip: equivp(RESPONSE,1/mAns);
              numOrig: equivp(num(RESPONSE),mNum);
              denomOrig: equivp(denom(RESPONSE),mDen);                
              isOrig: if (numOrig and denomOrig) then true else false;        
              denR1: equivp(denom(RESPONSE),1);
              denR2: equalp(denom(RESPONSE),iN^(-iC));
              numR1: equalp(num(RESPONSE),iN^iC);
              numR2: equivp(num(RESPONSE),1);                
              negPower: is(ev(-iC,numer,simp)>0);
              isSimp: equalp(RESPONSE,ev(RESPONSE,simp));
              isNotSimp: if((numR2 and denR2 and not negPower) or (isEquiv and not isSimp)) then true
                     else false;
              isOK: if ((numR1 and denR1) or (negPower and numR2 and denR2)) then true
                        else false;        
              isAdded: equivp(RESPONSE,mAdd);
              isSubtracted: equivp(RESPONSE,mSub);
              isMultiplied: equivp(RESPONSE,mMult);
        ]]></qti-base-value>
     </qti-custom-operator>
  </qti-set-outcome-value>

In this case, a qti-custom-operator is used as a very slim container for what is effectively a complete script in Maxima's language. A QTI processor designed to work with this qti-custom-operator could pass the script verbatim to Maxima, and use its response to set the 'oDummy' outcome value.

3.7.2 Adaptive Items

Adaptive items are a feature that allows an item to be scored adaptively over a sequence of attempts. This allows the candidate to alter their answer following feedback or to be posed additional questions based on their current answer. Response processing works differently for adaptive items. Normally (for non-adaptive items) each attempt is independent and the outcome variables are set to their default values each time response processing is carried out. For adaptive items, the outcome variables retain their values across multiple attempts and are only updated by subsequent response processing. This difference is indicated by the value of the adaptive attribute of the Assessment Item. Adaptive items must of course provide feedback to the candidate in order to allow them to adjust their response(s).

In the following example, the feedback is used to contain a solution which is displayed when the candidate clicks the "Show Solution" button.

<?xml version="1.0" encoding="UTF-8"?>
  <qti-assessment-item xmlns="http://www.imsglobal.org/xsd/imsqtiasi_v3p0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:m="http://www.w3.org/1998/Math/MathML"
  xsi:schemaLocation="http://www.imsglobal.org/xsd/imsqtiasi_v3p0 
  https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0_v1p0.xsd 
  http://www.w3.org/1998/Math/MathML 
  https://purl.imsglobal.org/spec/mathml/v3p0/schema/xsd/mathml3.xsd" 
  identifier="Example03-feedbackBlock-solution" title="Using feedbackBlock to show a solution" 
  adaptive="true" time-dependent="false" xml:lang="en-US"
  tool-name="Mathqurate" tool-version="0.9.7b">
  <qti-response-declaration base-type="float" cardinality="single" identifier="RESPONSE">
    <qti-correct-response>
      <qti-value>7.389</qti-value>
    </qti-correct-response>
  </qti-response-declaration>
  
  <!-- This response variable is set to true if the solution button is clicked.-->
  <qti-response-declaration base-type="boolean" cardinality="single" identifier="SOLREQUEST"/>
  <qti-outcome-declaration base-type="identifier" cardinality="multiple" identifier="FEEDBACK"/>
  <qti-outcome-declaration base-type="identifier" cardinality="single" identifier="EMPTY"/>
  <qti-outcome-declaration base-type="float" cardinality="single" identifier="SCORE" normal-maximum="10.0" 
   normal-minimum="0.0">
    <qti-default-value>
      <qti-value>0.0</qti-value>
      </qti-default-value>
  </qti-outcome-declaration>
  
  <!-- This outcome variable is set to true if the solution has been viewed.-->
  <qti-outcome-declaration base-type="boolean" cardinality="single" identifier="seenSolution">
    <qti-default-value>
      <qti-value>false</qti-value>
    </qti-default-value>
  </qti-outcome-declaration>
  
  <!-- This outcome variable controls the display of the solution button.-->
  <qti-outcome-declaration base-type="identifier" cardinality="single" identifier="ASKSOLUTION">
    <qti-default-value>
      <qti-value>asksolution</qti-value>
    </qti-default-value>
  </qti-outcome-declaration>
  <qti-item-body>
    <div>
      <p>Find the value of <math xmlns="http://www.w3.org/1998/Math/MathML" id="mathML0">
          <semantics>
            <mrow><msup><mi>e</mi><mn>2</mn></msup></mrow>
            <annotation encoding="LaTeX">[e^2]</annotation>
          </semantics></math> to 3 decimal places.
      </p>
      <div class="qti-margin-b-2">
        <table>
          <tbody>
            <tr>
              <td class="qti-padding-e-2">
                <qti-text-entry-interaction class="qti-input-width-10" pattern-mask="([0-9.\-]{0,10})"
                  id="textEntryInteraction0" label="mathInput" response-identifier="RESPONSE"/>
              </td>
              <td>
                <qti-feedback-inline id="feedbackInline0" identifier="CORRECT"
                  outcome-identifier="FEEDBACK" show-hide="show">Correct </qti-feedback-inline>
                <qti-feedback-inline id="feedbackInline1" identifier="INCORRECT"
                  outcome-identifier="FEEDBACK" show-hide="show">
                   No, that is not the correct answer
                </qti-feedback-inline>
              </td>
            </tr>
          </tbody>
        </table>
      </div>
  
      <!-- this feedbackBlock contains the solution -->
      <qti-feedback-block class="" id="feedbackBlock2" identifier="SOLUTION" outcome-identifier="FEEDBACK" show-hide="show">
          <qti-content-body>
            <div class="qti-well">
              <math xmlns="http://www.w3.org/1998/Math/MathML" display="block" id="mathML1">
                <semantics>
                  <mtable>
                        <mtr>
                          <mtd columnalign="right">
                            <msup><mi>e</mi><mn>2</mn></msup>
                          </mtd>
                          <mtd columnalign="center">
                            <mo>=</mo>
                          </mtd>
                          <mtd columnalign="left">
                            <mi>exp</mi><mfenced close=")"><mn>2</mn></mfenced>
                          </mtd>
                        </mtr>
                        <mtr>
                          <mtd columnalign="right"/>
                          <mtd columnalign="center">
                            <mo>=</mo>
                          </mtd>
                          <mtd columnalign="left">
                            <mi>7.389</mi>
                          </mtd>
                        </mtr>
                    </mtable>
                  <annotation encoding="SnuggleTeX">\begin{eqnarray*}e^2 
                   &amp;=&amp; exp(2) &amp;=&amp; 7.389 \end{eqnarray*}
                  </annotation>
                </semantics>
              </math>
            </div>
          </qti-content-body>
      </qti-feedback-block>
  
      <!-- Explain why the score is zero (after viewing solution) -->
      <qti-feedback-block identifier="SEEN-SOLUTION" outcome-identifier="FEEDBACK" show-hide="show">
        <qti-content-body>
          <p>Since you have viewed the solution, your score for this question will be 0.</p>
        </qti-content-body>
      </qti-feedback-block>
  
      <!-- Show the solution button -->
      <qti-feedback-block identifier="asksolution" outcome-identifier="ASKSOLUTION" show-hide="show">
        <qti-content-body>
          <p>
            <qti-end-attempt-interaction response-identifier="SOLREQUEST" title="Show Solution"/>
          </p>
        </qti-content-body>
      </qti-feedback-block>
    </div>
  </qti-item-body>
  <qti-response-processing>
    <qti-set-outcome-value identifier="FEEDBACK">
      <qti-multiple>
        <qti-variable identifier="EMPTY"/>
      </qti-multiple>
    </qti-set-outcome-value>
    <qti-response-condition>
      <qti-response-if>
        <qti-variable identifier="SOLREQUEST"/>
        <!-- In response processing, the outcome variable FEEDBACK is set to the identifier
             (SOLUTION) of the solution feedbackBlock, so that the solution appears.-->
        <qti-set-outcome-value identifier="FEEDBACK">
          <qti-multiple>
            <qti-base-value base-type="identifier">SOLUTION</qti-base-value>
          </qti-multiple>
        </qti-set-outcome-value>
        <!-- The seenSolution flag is set to true so that the message about the score will
             appear if an answer is submitted.-->
        <qti-set-outcome-value identifier="seenSolution">
          <qti-base-value base-type="boolean">true</qti-base-value>
        </qti-set-outcome-value>
        <!-- The built-in outcome variable completionStatus is set to completed – this must
             happen at some stage in any adaptive question otherwise the question is never
             complete, which is a problem in tests.-->
        <qti-set-outcome-value identifier="completionStatus">
          <qti-base-value base-type="identifier">completed</qti-base-value>
        </qti-set-outcome-value>
        <!-- The solution button is removed by setting the ASKSOLUTION outcome variable to null-->
        <qti-set-outcome-value identifier="ASKSOLUTION">
          <qti-base-value base-type="identifier">null</qti-base-value>
        </qti-set-outcome-value>
      </qti-response-if>
      <qti-response-else>
        <qti-response-condition>
          <qti-response-if>
            <qti-is-null>
              <qti-variable identifier="RESPONSE"/>
            </qti-is-null>
            <qti-set-outcome-value identifier="SCORE">
              <qti-base-value base-type="float">0</qti-base-value>
            </qti-set-outcome-value>
          </qti-response-if>
          <qti-response-else>
            <qti-response-condition>
              <qti-response-if>
                <qti-equal-rounded figures="3" rounding-mode="decimalPlaces">
                  <qti-variable identifier="RESPONSE"/>
                  <qti-correct identifier="RESPONSE"/>
                </qti-equal-rounded>
                <qti-set-outcome-value identifier="FEEDBACK">
                  <qti-multiple>
                    <qti-base-value base-type="identifier">CORRECT</qti-base-value>
                  </qti-multiple>
                </qti-set-outcome-value>
                <qti-set-outcome-value identifier="SCORE">
                  <qti-base-value base-type="float">2</qti-base-value>
                </qti-set-outcome-value>
              </qti-response-if>
              <qti-response-else>
                <qti-set-outcome-value identifier="FEEDBACK">
                  <qti-multiple>
                    <qti-base-value base-type="identifier">INCORRECT</qti-base-value>
                  </qti-multiple>
                </qti-set-outcome-value>
                <qti-set-outcome-value identifier="SCORE">
                  <qti-base-value base-type="float">0</qti-base-value>
                </qti-set-outcome-value>
              </qti-response-else>
            </qti-response-condition>
  
            <!-- When an answer has been submitted, once again the built-in outcome
                 variable completionStatus is set to completed and the solution button is removed.-->
            <qti-set-outcome-value identifier="completionStatus">
              <qti-base-value base-type="identifier">completed</qti-base-value>
            </qti-set-outcome-value>
            <qti-set-outcome-value identifier="ASKSOLUTION">
              <qti-base-value base-type="identifier">null</qti-base-value>
            </qti-set-outcome-value>
          </qti-response-else>
        </qti-response-condition>
      </qti-response-else>
    </qti-response-condition>
  
    <!-- When an answer has been submitted, if the solution has been displayed,
         the message about the score is added to the FEEDBACK, and SCORE is set to 0.0 -->
    <qti-response-condition>
      <qti-response-if>
        <qti-variable identifier="seenSolution"/>
        <qti-set-outcome-value identifier="FEEDBACK">
          <qti-multiple>
            <qti-variable identifier="FEEDBACK"/>
            <qti-base-value base-type="identifier">SEEN-SOLUTION</qti-base-value>
          </qti-multiple>
        </qti-set-outcome-value>
        <qti-set-outcome-value identifier="SCORE">
          <qti-base-value base-type="float">0.0</qti-base-value>
        </qti-set-outcome-value>
      </qti-response-if>
    </qti-response-condition>
  </qti-response-processing>
  </qti-assessment-item>