IMS Logo

IMS Question and Test Interoperability Addendum

Version 1.2.1 Final Specification

Copyright © 2003 IMS Global Learning Consortium, Inc. All Rights Reserved.
The IMS Logo is a trademark of IMS Global Learning Consortium, Inc.
Document Name: IMS Question and Test Interoperability Addendum
Revision: 31 March 2003 

IPR and Distribution Notices

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the specification set forth in this document, and to provide supporting documentation.

IMS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on IMS's procedures with respect to rights in IMS specifications can be found at the IMS Intellectual Property Rights web page: http://www.imsglobal.org/ipr/imsipr_policyFinal.pdf.

Copyright © IMS Global Learning Consortium 2006. All Rights Reserved.

If you wish to distribute this document or use this document to implement a product or service, you must complete a valid license registration with IMS and receive an email from IMS granting the license. To register, follow the instructions on the IMS website: http://www.imsglobal.org/specificationdownload.cfm.

This document may be copied and furnished to others by Licensee organizations registered on the IMS website provided that the above copyright notice and this paragraph are included on all such copies. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to IMS, except as needed for the purpose of developing IMS specifications, under the auspices of a chartered IMS work group.

Use of this specification to develop products or services is governed by the license with IMS found on the IMS website: http://www.imsglobal.org/question/qtiv1p2p1/qtiv1p2p1speclicense.html.

The limited permissions granted above are perpetual and will not be revoked by IMS or its successors or assigns.

THIS SPECIFICATION IS BEING OFFERED WITHOUT ANY WARRANTY WHATSOEVER, AND IN PARTICULAR, ANY WARRANTY OF NONINFRINGEMENT IS EXPRESSLY DISCLAIMED. ANY USE OF THIS SPECIFICATION SHALL BE MADE ENTIRELY AT THE IMPLEMENTER'S OWN RISK, AND NEITHER THE CONSORTIUM, NOR ANY OF ITS MEMBERS OR SUBMITTERS, SHALL HAVE ANY LIABILITY WHATSOEVER TO ANY IMPLEMENTER OR THIRD PARTY FOR ANY DAMAGES OF ANY NATURE WHATSOEVER, DIRECTLY OR INDIRECTLY, ARISING FROM THE USE OF THIS SPECIFICATION.

Table of Contents


1. Introduction
     1.1 Question and Test Interoperability Overview
     1.2 Scope and Context
     1.3 Structure of this Document
     1.4 Nomenclature
     1.5 References

2. Amendments and Errata Instructions
     2.1 Functional Corrections
           2.1.1 ASI Information Model Document
           2.1.2 ASI XML Binding V1.2 Document
     2.2 Editorial Amendments
           2.2.1 ASI Information Model Document
           2.2.2 ASI Best Practice and Implementation Document
     2.3 Typographic Changes
           2.3.1 ASI Information Model V1.2 Document
           2.3.2 ASI XML Binding V1.2 Document
           2.3.3 ASI Best Practice and Implementation Guide V1.2 Document
           2.3.4 ASI Selection and Ordering V1.2 Document
           2.3.5 ASI Outcomes Processing V1.2 Document
           2.3.6 Results Reporting Best Practice and Implementation V1.2 Document
           2.3.7 ASI V1.2 XML Schema Files
           2.3.8 Results Reporting V1.2 XML Schema Files
           2.3.9 ASI V1.2 Example Files
           2.3.10 Results Reporting V1.2 Example Files

3. Deliverables

Appendix A - The Initial Issues List

About This Document
     List of Contributors

Revision History

Index

1. Introduction

1.1 Question and Test Interoperability Overview

The Question and Test Interoperability (QTI) Specification describes a basic structure for the representation of question (item) and test (assessment) data and their corresponding results reports [QTI, 02j]. Therefore, the specification enables the exchange of this test, assessment and results data between Learning Management Systems, as well as content authors and, content libraries and collections. The QTI Specification is defined in XML to promote the widest possible adoption. XML is a powerful, flexible, industry standard markup language used to encode data models for Internet-enabled and distributed applications. The QTI Specification is extensible and customizable to permit immediate adoption, even in specialized or proprietary systems. Leading suppliers and consumers of learning products, services and content contributed time and expertise to produce this final specification. This document describes the amendment and errata changes to the V1.2 specification to create the V1.2.1 specification.

1.2 Scope and Context

This document describes amendments that should be made by adopters of the IMS QTI Specification V1.2, thereby creating the IMS QTI V1.2.1 Specification. The differences between the V1.2 and the V1.2.1 specifications are limited to:

1.3 Structure of this Document

The structure of this document is:

2. Amendments & Errata Instructions
 The resolution of the issues that were not deferred until a later release. Each instruction describes the changes to be made to the documentation;
3. Deliverables
 The set of documents and supporting information that is released to form the IMS QTI V1.2.1 specification;
Appendix A - The Initial Issues List
 The full set of issues that were addressed as a part of this revision of the IMS QTI specification. Many of the issues were deferred for consideration under a later release of the specification.

1.4 Nomenclature

ASI
 Assessment, Section, Item
DTD
 Document Type Definition
QTI
 Question & Test Interoperability
W3C
 World Wide Web Consortium
XML
 Extensible Mark-up Language
XSD
 XML Schema Data

1.5 References

[QTI, 02a]
 IMS Question & Test Interoperability: ASI Information Model Specification, C.Smythe, E.Shepherd, L.Brewer and S.Lay, Final Specification, Version 1.2, IMS, February 2002.
[QTI, 02b]
 IMS Question & Test Interoperability: ASI XML Binding Specification, C.Smythe, E.Shepherd, L.Brewer and S.Lay, Final Specification, Version 1.2, IMS, February 2002.
[QTI, 02c]
 IMS Question & Test Interoperability: ASI Best Practice & Implementation Guide, C.Smythe, E.Shepherd, L.Brewer and S.Lay, Final Specification, Version 1.2, IMS, February 2002.
[QTI, 02d]
 IMS Question & Test Interoperability: ASI Selection & Ordering, C.Smythe, L.Brewer and S.Lay, Final Specification, Version 1.2, IMS, February 2002.
[QTI, 02e]
 IMS Question & Test Interoperability: ASI Outcomes Processing Specification, C.Smythe, L.Brewer and S.Lay, Final Specification, Version 1.2, IMS, February 2002.
[QTI, 02f]
 IMS Question & Test Interoperability: Results Reporting Information Model, C.Smythe, L.Brewer and S.Lay, Final Specification, Version 1.2, IMS, February 2002.
[QTI, 02g]
 IMS Question & Test Interoperability: Results Reporting XML Binding, C.Smythe, L.Brewer and S.Lay, Final Specification, Version 1.2, IMS, February 2002.
[QTI, 02h]
 IMS Question & Test Interoperability: Results Reporting Best Practice & Implementation Guide, C.Smythe, L.Brewer and S.Lay, Final Specification, Version 1.2, IMS, February 2002.
[QTI, 02i]
 IMS Question & Test Interoperability: QTILite, C.Smythe, E.Shepherd, L.Brewer and S.Lay, Final Specification, Version 1.2, IMS, February 2002.
[QTI, 02j]
 IMS Question & Test Interoperability: An Overview, C.Smythe, E.Shepherd, L.Brewer and S.Lay, Final Specification, Version 1.2, IMS, February 2002.

2. Amendments and Errata Instructions

2.1 Functional Corrections

2.1.1 ASI Information Model Document

Amendment Instructions:

Page 26

Add to the 'Explanation' cell for row 2.8 in Table 5.2 the sentence:

If this element is absent then the default states for the switches should be assumed by the implementation.

Issue Number:

qti-20020607-02


Amendment Instructions:

Page 27

Add to the 'Explanation' cell for row 3.8 in Table 5.3 the sentence:

If this element is absent then the default states for the switches should be assumed by the implementation.

Issue Number:

qti-20020607-02


Amendment Instructions:

Page 31

Add to the 'Explanation' cell for row 4.12 in Table 5.4 the sentence:

If this element is absent then the default states for the switches should be assumed by the implementation.

Issue Number:

qti-20020607-02


Amendment Instructions:

Page 32.

Change the 'Notes' cell of row 4.15.9.5.5.3 in Table 5.4
From:

Information describing the key points must be given. The ellipse is 'x,y,r1,r2', the rectangle is 'x0,y0,height,width' and the bounded area is 'x1y1,...,xnyn'.

To:
Information describing the key points must be given. The ellipse is 'x,y,height,width ('x,y' being the centre of the ellipse), the rectangle is 'x0,y0,height,width' (with 'x0,y0' being the top left hand corner) and the bounded area is 'x1y1,...,xnyn'. For the ellipse the height and width are diameters.

Issue Number:

qti-20020322-01


Amendment Instructions:

Page 44.

Change the 'Note' cell of row 5.4.7 (<varsubstring>) in Table 5.5
From:

'True' is returned if the substring (the user response) is contained.

To:
'True' is returned if the substring defined in the <varsubstring> element is contained within the user's response string.

Issue Number:

qti-20020211-26


Amendment Instructions:

Page 44.

Change the Type cell of row 5.4.8 in Table 5.5
From:

String 4 chars.

CDATA of the co-ordinates of the areas:

Ellipse x0,y0,height,width

Rectangle x0,y0,height,width

Bounded x1,y1, x2,y2,...,xk,yk.

To:
String 4 chars.

CDATA of the co-ordinates of the areas:

Ellipse x,y,height,width (x,y is the centre point and height and width are diameters of the ellipse)

Rectangle x0,y0,height,width (x0,y0 is the top left hand corner)

Bounded x1,y1, x2,y2,...,xk,yk.

Issue Number:

qti-20020322-01


Amendment Instructions:

Page 51 (Table 5.7)

Add to the 'Note' cells of rows 7.4, 7.5 and 7.6 the following statement:

The default conditions shall be assumed if this field is not defined in the implementation instance.

Issue Number:

qti-20020607-02


2.1.2 ASI XML Binding V1.2 Document

Amendment Instructions:

Page 70

Change the '3.6.18 <rubric> Element Description' subsection
From:

Description: The rubric element is used to contain contextual information that is important to the element e.g. it could contain standard data values that might or might not be useful for answering the question. Different sets of rubric can be defined for each of the possible 'views'. The material contained within the rubric must be displayed to the participant.

To:
Description: The rubric element is used to contain contextual information that is important to the element e.g. it could contain standard data values that might or might not be useful for answering the question. Different sets of rubric can be defined for each of the possible 'views'. The material contained within the rubric for the view 'All' and 'Participant' must be displayed to the participant as this may be required to correctly answer the question.

Issue Number:

qti-20021129-11

Amendment Instructions:

Page 76.

Change the Description of the element 3.6.23.7 <varsubstring>
From:

The <varsubstring> element is used to determine if a given string is a substring of some other string.

To:
The <varsubstring> element is used to determine if the user's response contains a reference string as defined by the content of the element. If the reference string is 'April' and the user's response string is 'The month is April' then the <varsubstring> condition will be 'True'.

Issue Number:

qti-20020211-26


2.2 Editorial Amendments

2.2.1 ASI Information Model Document

Amendment Instructions:

Page 20

Change the following paragraph
From:

In V1.1/1.2 flows may or may not be used - this ensures backwards compatibility. When flows are used this will be indicated by the presence of the top-level <flow> element within the <presentation> element. If any flow construct is to be used then the <flow> element must be present within the <presentation> element. Three separate elements have been defined to support flows:

To:
In V1.1/1.2 flows may or may not be used - this ensures backwards compatibility. When flows are used this will be indicated by the presence of the top-level <flow> element within the <presentation> element. If any flow construct is to be used then the <flow> element must be present within the <presentation> element. The <flow> structure itself can have any number of nested <flow> substructures and so an arbitrarily complex organization can be imposed on the material as required. However, it must be noted that all but the simplest combinations may result in unexpected interoperability behavior. Three separate elements have been defined to support flows:

Issue Number:

qti-20021129-01 and qti-20021129-02

Amendment Instructions:

Page 43

Change the 'Notes' entries for rows 5.2.4 and 5.2.5 in Table 5.5
From:

Applies to the value of the score after all of the item processing has been completed.

To:
Applies to the value of the score after all of the response processing instructions have been completed within the <resprocessing> block i.e. the limits are not applied at the execution of each <setvar> operation on the variable. The values that fall outside the ranges are truncated.

Issue Number:

qti-20021202-03


2.2.2 ASI Best Practice and Implementation Document

Amendment Instructions:

Page 87

Add the following paragraph onto the end of the 'Response and Rendering Types' sub-section of Section 7.3.2.

In the case of hotspots, as identified by the usage of the <render_hotspot> element, then the associated labels are defined by using the <material> element within the <response_label> element. An example of this is: 

<render_hotspot>
 <response_label ident="A" rarea="Ellipse">
 <material>
 <mattext>Paris</mattext>
 </material>100,100,2,2
 </response_label>
</render_hotspot>

In this example the label 'Paris' is assigned to the hotspot point as defined by the co-ordinates '100,100,2,2'. The actual positioning of the label is implementation dependent.

Issue Number:

qti-20020211-34 and qti-20020211-35

2.3 Typographic Changes

2.3.1 ASI Information Model V1.2 Document

Amendment Instructions:

Page 4.

Change the lines in Section 1.2
From:

  • IMS Question & Test Interoperability: ASI XML Binding Specification v1.2 [QTI, 02b];
  • IMS Question & Test Interoperability: ASI Best Practice & Implementation Guide v1.2 [QTI, 02c];

To:

  • IMS Question & Test Interoperability: ASI XML Binding Specification v1.2 [QTI, 02a];
  • IMS Question & Test Interoperability: ASI Best Practice & Implementation Guide v1.2 [QTI, 02b];
Issue Number:

qti-20021108-01

Amendment Instructions:

Page 26.

Change the 'Type/Note' cell of row 2.9 in Table 5.2
From:

As per structure 5.12.

To:
As per structure 5.11.

Issue Number:

qti-20021108-01


Amendment Instructions:

Page 26.

Change the 'No' cell of row 2.32.2 in Table 5.2
From:

2.32.2.

To:
2.13.2.

Change the 'No' cell of row 2.32.4 in Table 5.2
From:

2.32.4.

To:
2.13.4.

Change the 'Type/Note' cell of row 2.14 in Table 5.2
From:

The detailed definition and description of the outcomes processing is supplied in the IMS QTI ASI Selection & Ordering Specification [QTI, 02c].

To:
The detailed definition and description of the selection and ordering is supplied in the IMS QTI: ASI Selection & Ordering Specification [QTI, 02c].].

Change phrase of row 2.16.1 in Table 5.2
From:

As per structure 6.14.

To:
As per structure 7.14.

Issue Number:

qti-20021108-01


Amendment Instructions:

Page 28.

Change the 'Reqd' cell of row 3.15 in Table 5.3
From:

M.

To:
O.

Change the 'Type/Note' cell of row 3.16 in Table 5.3
From:

The detailed definition and description of the outcomes processing is supplied in the IMS QTI ASI Selection & Ordering Specification [QTI, 02c].

To:
The detailed definition and description of the selection and ordering is supplied in the IMS QTI ASI Selection & Ordering Specification [QTI, 02c].

Change phrase of row 3.18 in Table 5.3
From:

As per structure 2.15.

To:
As per structure 2.16.

Remove row 3.18.1 from the document.

Issue Number:

qti-20021108-01


Amendment Instructions:

Page 31.

Add the row 4.12.5 to Table 5.4.

No: 4.12.5

Name: qticomment

Explanation: Comments on the feedback.

Reqd: O

Mult:

Type/Note: As per structure 5.6.

Issue Number:

qti-20021108-01


Amendment Instructions:

Page 32.

Change the 'Mult' cell of row 4.15.9.5.5 in Table 5.4
From:

<blank>

To:
'n'.

Issue Number:

qti-20021108-01


Amendment Instructions:

Page 33.

Add new row to Table 5.4 (between 4.15.9.5.7.1 and 4.15.9.5.7.2).

No: 4.15.9.5.7.1a

Name: qticomment

Explanation: Comments on the feedback.

Reqd: O

Mult:

Type/Note: As per structure 5.6.

Issue Number:

qti-20021108-01


Amendment Instructions:

Page 36.

Add new row to Table 5.4 (between 4.15.14.1 and 4.15.14.2).

No: 4.15.14.1a

Name: qticomment

Explanation: Comments on the feedback.

Reqd: O

Mult:

Type/Note: As per structure 5.6.

Issue Number:

qti-20021108-01


Amendment Instructions:

Page 38.

Add the following row (row 4.19) to the end of Table 5.4
With:

No: 4.19

Name: reference

Explanation: The container for material that is to be referenced by the Sections and/or Items contained within the Section.

Reqd: O

Mult:

Type/Note: As per structure 5.15.

Issue Number:

qti-20020211-01


Amendment Instructions:

Page 41.

Add the definition 5.1.10.5 after the entry 5.1.10.4. This new definition is identical in format to the entry 5.1.9.7.

Issue Number:

qti-20020211-21


Amendment Instructions:

Page 44.

Change the Note cell of row 5.4.2 in Table 5.5
From:

'True' is returned if equivalent.

To:
'True' is returned if the value is less than the comparison value.

Change the Note cell of row 5.4.3 in Table 5.5
From:

'True' is returned if the value is less than or equal to the comparator.

To:
'True' is returned if the value is less than or equal to the comparison value.

Change the Note cell of row 5.4.4 in Table 5.5
From:

'True' is returned if the value is greater than to the comparator.

To:
'True' is returned if the value is greater than the comparison value.

Change the Note cell of row 5.4.5 in Table 5.5
From:

'True' is returned if the value is greater than or equal to the comparator.

To:
'True' is returned if the value is greater than or equal to the comparison value.

Issue Number:

qti-20020211-33


Amendment Instructions:

Page 44.

Change the 'Note' cell of row 5.4.6 (<varsubset>) in Table 5.5
From:

'True' is returned if the value is contained within the comparator.

To:
'True' is returned if the value is contained within the comparison set.

Issue Number:

qti-20020211-33


Amendment Instructions:

Page 45-46.

Change the multiplicity of the following elements to 'n'.

5.4.14 not

5.4.15 and

5.4.16 or

5.4.17 unanswered

5.4.18 other

Issue Number:

qti-20020211-20


Amendment Instructions:

Page 48.

Add new row to Table 5.5 (between 5.13.1 and 5.13.2).

No: 5.13.1a

Name: qticomment

Explanation: Comment string.

Reqd: O

Mult:

Type/Note: As per structure 5.6.

Issue Number:

qti-20021129-03


Amendment Instructions:

Page 48.

Change the 'Mult' cell of row 5.15.1 in Table 5.5
From:

'n'

To:
<blank>

Issue Number:

qti-20021129-03


Amendment Instructions:

Page 52.

Change the 'Note' cell of row 7.20 in Table 5.7
From:

Default is "SumofScores"

To:
<blank>.

Change the 'Note' cell of row 7.21 in Table 5.7
From:

Default value=0

To:
<blank>.

Change the 'Note' cell of row 7.22 in Table 5.7
From:

Default value=0

To:
<blank>.

Issue Number:

qti-20021108-01


Amendment Instructions:

Page 56.

Delete the second sentence of the first paragraph of Section 6.3 i.e.

The vocabulary is supplied as a comma separated list in the text file "imsqtiv1p2_metadata.txt".

Issue Number:

qti-20020211-07


Amendment Instructions:

Page 58.

Change the example code at the end of Section 6.3
From:

<vocabulary uri="imsqtiv1p2_metadata.txt" vocab_type="text/plain"/>

To:
<vocabulary uri="extvocabulary_metadata.txt" vocab_type="text/plain"/>

Issue Number:

qti-20020211-07


2.3.2 ASI XML Binding V1.2 Document

Amendment Instructions:

Page 25.

Change the Multiplicity line in Section 3.4.16
From:

Occurs one or more times within the <section> element.

To:
Occurs zero or more times within the <section> element.

Issue Number:

qti-20020211-29

Amendment Instructions:

Page 26.

Replace Figure 3.9
With:

structured view of <item> elements
Issue Number:

qti-20020211-01


Amendment Instructions:

Page 32.

Change the Description of the <objectives> element
From:

The objectives element is used to store the information that describes the educational aims of the Item. These objectives can be defined for each of the different 'view' perspectives. This element should not be used to contain information specific to an Item because the question-engine may not make this information available to the Item during the actual test.

To:
The objectives element is used to store the information that describes the educational aims of the Item. These objectives can be defined for each of the different 'view' perspectives. This element should not be used to contain information required for the rendering of an Item because the question-engine may not make this information available to the Item during the actual test.

Issue Number:

qti-20020211-29


Amendment Instructions:

Page 36.

Replace Figure 3.14
With:

structured view of <flow> elements
Issue Number:

qti-20021129-03


Amendment Instructions:

Page 45.

Change the Multiplicity line in Section 3.5.17.2
From:

Occurs zero or more times within the <response_choice> element.

To:
Occurs zero or more times within the <render_choice> element.

Issue Number:

qti-20020211-11


Amendment Instructions:

Page 48.

Change the Multiplicity line in Section 3.5.19.2
From:

Occurs zero or more times within the <response_fib> element.

To:
Occurs zero or more times within the <render_fib> element.

Issue Number:

qti-20020211-11


Amendment Instructions:

Page 49.

Change the first attribute description in Section 3.5.20
From:

orientation (optional - enumerated list of: Horizontal, Vertical. Default = Box). The orientation of the slider.

To:
orientation (optional - enumerated list of: Horizontal, Vertical. Default = Horizontal). The orientation of the slider.

Issue Number:

qti-20020211-13


Amendment Instructions:

Page 51.

Replace Figure 3.25
With:

structured view of <flow_label> elements
Issue Number:

qti-20021129-03


Amendment Instructions:

Page 55.

Change the Multiplicity line in Section 3.5.25.3
From:

This occurs once within the <respcondition> element.

To:
This occurs zero or more times within the <respcondition> element.

Issue Number:

qti-20020211-12


Amendment Instructions:

Page 59.

Insert sub-section 3.5.32 (to the end of Section 3.5)
With:

3.5.32 <reference> Element

Description: This element is used to contain any common materials that are to be available to any of the child objects with the Item. The common material may or may not be presented to the participant.

Multiplicity: Occurs zero or once within the <item> element.

Attributes: None.

Issue Number:

qti-20020211-01


Amendment Instructions:

Page 68.

Replace Figure 3.3
With:

structured view of <flow_mat> elements
Issue Number:

qti-20021129-03


Amendment Instructions:

Page 82.

Replace Figure 3.41
With:

structured view of <reference> elements
Issue Number:

qti-20021129-03


2.3.3 ASI Best Practice and Implementation Guide V1.2 Document

Amendment Instructions:

Page 81.

Change the example code on Section 7.1.1
From:

<vocabulary uri="imsqtiv1p2_metadata.txt" vocab_type="text/plain"/>

To:
<vocabulary uri="extvocabulary_metadata.txt" vocab_type="text/plain"/>

Issue Number:

qti-20020211-07

Amendment Instructions:

Page 84.

Change the example code on Section 7.2.1
From:

<vocabulary uri="imsqtiv1p2_metadata.txt" vocab_type="text/plain"/>

To:
<vocabulary uri="extvocabulary_metadata.txt" vocab_type="text/plain"/>

Issue Number:

qti-20020211-07


Amendment Instructions:

Page 86.

Change the example code on Section 7.3.1
From:

<vocabulary uri="imsqtiv1p2_metadata.txt" vocab_type="text/plain"/>

To:
<vocabulary uri="extvocabulary_metadata.txt" vocab_type="text/plain"/>

Issue Number:

qti-20020211-07


Amendment Instructions:

Page 92.

Change lines 41-47 in the example XML starting at the foot of the page. From: 

 <varequal respident="Mcb_01" index="1">E</varequal>
 <varequal respident="Mcb_01" index="2">>B</varequal>
 <varequal respident="Mcb_01" index="3">>D</varequal>
 <varequal respident="Mcb_01" index="4">>C</varequal>
 <varequal respident="Mcb_01" index="5">>G</varequal>
 <varequal respident="Mcb_01" index="6">>F</varequal>
 <varequal respident="Mcb_01" index="6">>A</varequal>

To: 

 <varequal respident="Mcb_01" index="1">E</varequal>
 <varequal respident="Mcb_01" index="2">B</varequal>
 <varequal respident="Mcb_01" index="3">D</varequal>
 <varequal respident="Mcb_01" index="4">C</varequal>
 <varequal respident="Mcb_01" index="5">G</varequal>
 <varequal respident="Mcb_01" index="6">F</varequal>

<varequal respident="Mcb_01" index="7">A</varequal>

Issue Number:

qti-20020211-17


Amendment Instructions:

Page 110.

Change the definition of the 'Class' term
From:

The class attribute is used by the flow, flow_label and flow_mat elements. It is used to define the nature of the block - the possible values are determined using an external vocabulary contained in the file 'ims_qti_flowvocabulary.html'. The default value is 'Block' but 'List' is another common value.

To:
The class attribute is used by the flow, flow_label and flow_mat elements. It is used to define the nature of the block - the permissible values should be defined in an external file that can be referenced. The default value is 'Block' but 'List' is another common value. The handling of this attribute with respect to rendering of the material is implementation dependent because there is no agreed vocabulary and semantics.

Issue Number:

qti-20020211-31


2.3.4 ASI Selection and Ordering V1.2 Document

Amendment Instructions:

Page 17.

Change Figure 3.1 to:

structured view of <selection_ordering> elements
Issue Number:

qti-20021203-01

Amendment Instructions:

Page 17.

Change the Example subsection in Section 3.1.
From:

Example: 

<selection_ordering>
 <selection sequence_type="Normal"/>
 <order order_type="All"/>
</selection_ordering>

To:

Example: 

<selection_ordering>
 <selection/>
 <order order_type="All"/>

</selection_ordering>

Issue Number:

qti-20020211-23


Amendment Instructions:

Page 18.

Change the Multiplicity subsection of 3.1.2
From:

Multiplicity: Occurs zero or once within the <selection_ordering> element.

To:
Multiplicity: Occurs zero or more times in the <selection_ordering> element.

Issue Number:

qti-20020211-23


Amendment Instructions:

Page 18.

Change the Multiplicity subsection in Section 3.2.
From:

Multiplicity: The <selection> occurs once or more times in the <selection_ordering> element.

To:
Multiplicity: The <selection> occurs zero or more times in the <selection_ordering> element.

Issue Number:

qti-20020211-23


2.3.5 ASI Outcomes Processing V1.2 Document

Amendment Instructions:

Page 12.

Change the second to last paragraph in Section 2.3.
From:

Section_Ident_2.SCORE = Item_Ident_2.1.SCORE + Item_Ident_2.1.SCORE + Item_Ident_2.1.SCORE

To:
"Section_Ident_2.SCORE = Item_Ident_2.1.SCORE + Item_Ident_2.2.SCORE + Item_Ident_2.3.SCORE"

Issue Number:

qti-20020211-28

Amendment Instructions:

Page 24.

Change the heading of 3.1
From:

outcomes_processing> Elements

To:
<outcomes_processing> Elements

Change the elements list of <outcomes_processing>
From:

  • qticomment
  • outcomes
  • objects_condition
  • processing_parameter
  • map_outcome
  • outcomes_feedback_test

To:

  • qticomment
  • outcomes
  • objects_condition
  • processing_parameter
  • map_output
  • outcomes_feedback_test
Issue Number:

qti-20021114-01


2.3.6 Results Reporting Best Practice and Implementation V1.2 Document

Amendment Instructions:

Page 16.

Change line 11 of the multiple choice Item example
From:

<correct_response>T</correct_response>

To:
<correct_response>B</correct_response>

Issue Number:

qti-20020211-08

Amendment Instructions:

Page 105.

Remove Table 6.1. The reason for its removal is that the mapping is incorrect with respect to the 'n.objectives'. These should be mapped to the <score> element, however SCORM objectives are more than just a score. Further work needs to be done on this mapping.

Issue Number:

qti-20021208-02


2.3.7 ASI V1.2 XML Schema Files

Amendment Instructions:

Replace the ASI DTD files with the new V1.2.1 DTDs.

Issue Number:

qti-20020211-15

2.3.8 Results Reporting V1.2 XML Schema Files

Amendment Instructions:

Replace the Results Reporting DTD files with the new V1.2.1 DTDs.

Issue Number:

General

2.3.9 ASI V1.2 Example Files

A new set of example files has been created. Changes that were made in response to registered issues are detailed below.

Amendment Instructions:

The Object-bank example files are supplied in the directory 'ims_qtiasiv1p2p1_examples/bank' V1.2.1 distribution kit.

Issue Number:

qti-20020211-03

Amendment Instructions:

The Advanced Chinese example files are supplied in the directory 'ims_qtiasiv1p2p1_examples/advanced/chinese' V1.2.1 distribution kit.

Issue Number:

qti-20020211-04


Amendment Instructions:

Replace the file 'oobj_i_001.xml' in the directory 'ims_qtiasiv1p2p1_examples/basic/oobj_i_001' with the file supplied in the V1.2.1 distribution kit.

Replace the file 'oobj_i_002.xml' in the directory 'ims_qtiasiv1p2p1_examples/basic/oobj_i_002' with the file supplied in the V1.2.1 distribution kit.

Replace the file 'oobj_ir_001.xml' in the directory 'ims_qtiasiv1p2p1_examples/basic/oobj_i_001' with the file supplied in the V1.2.1 distribution kit.

Replace the file 'oobj_ir_002.xml' in the directory 'ims_qtiasiv1p2p1_examples/basic/oobj_i_002' with the file supplied in the V1.2.1 distribution kit.

Issue Number:

qti-20020211-14


Amendment Instructions:

Replace the file 'mixd_imr_101.xml' in the directory 'ims_qtiasiv1p2p1_examples/advanced/mixd_imr_101' with the file supplied in the V1.2.1 distribution kit.

Issue Number:

qti-20020211-19


Amendment Instructions:

Replace the files in the directory 'ims_qtiasiv1p2p1_examples/basic/mchc_i_002' with those supplied in the V1.2.1 distribution kit.

Replace the file in the directory 'ims_qtiasiv1p2p1_examples/basic/mchc_ir_002' with those supplied in the V1.2.1 distribution kit.

Replace the files in the directory 'ims_qtiasiv1p2p1_examples/basic/mchc_i_003' with those supplied in the V1.2.1 distribution kit.

Replace the file in the directory 'ims_qtiasiv1p2p1_examples/basic/mchc_ir_003' with those supplied in the V1.2.1 distribution kit.

Replace the files in the directory 'ims_qtiasiv1p2p1_examples/basic/mchc_i_004' with those supplied in the V1.2.1 distribution kit.

Replace the file in the directory 'ims_qtiasiv1p2p1_examples/basic/mchc_ir_004' with those supplied in the V1.2.1 distribution kit.

Replace the files in the directory 'ims_qtiasiv1p2p1_examples/basic/mrsp_i_001' with those supplied in the V1.2.1 distribution kit.

Replace the file in the directory 'ims_qtiasiv1p2p1_examples/basic/mrsp_ir_001' with those supplied in the V1.2.1 distribution kit.

Replace the files in the directory 'ims_qtiasiv1p2p1_examples/basic/oobj_i_002' with those supplied in the V1.2.1 distribution kit.

Replace the file in the directory 'ims_qtiasiv1p2p1_examples/basic/oobj_i_002' with those supplied in the V1.2.1 distribution kit.

Replace the files in the directory 'ims_qtiasiv1p2p1_examples/basic/ctpt_i_001' with those supplied in the V1.2.1 distribution kit.

Replace the file in the directory 'ims_qtiasiv1p2p1_examples/basic/ctpt_ir_001' with those supplied in the V1.2.1 distribution kit.

Replace the files in the directory 'ims_qtiasiv1p2p1_examples/basic/ctpt_i_002' with those supplied in the V1.2.1 distribution kit.

Replace the file in the directory 'ims_qtiasiv1p2p1_examples/basic/ctpt_ir_002' with those supplied in the V1.2.1 distribution kit.

Replace the files in the directory 'ims_qtiasiv1p2p1_examples/basic/ihsp_i_001' with those supplied in the V1.2.1 distribution kit.

Replace the file in the directory 'ims_qtiasiv1p2p1_examples/basic/ihsp_ir_001' with those supplied in the V1.2.1 distribution kit.

Issue Number:

qti-20020211-22

2.3.10 Results Reporting V1.2 Example Files

A new set of example files has been created. Changes that were made in response to registered issues are detailed below.

Amendment Instructions:

Replace the file 'qtires_item_mc01.xml' in the directory 'ims_qtiresv1p2p1_examples/item' with the file supplied in the V1.2.1 distribution kit.

Issue Number:

qti-20020211-08

3. Deliverables

The set of deliverables to be issued as the IMS QTI V1.2.1 specification and documentation set is:

  1. IMS Question & Test Interoperability: Addendum, Version 1.2.1 (this document);
  2. IMS Question & Test Interoperability: ASI Information Model Specification, Version 1.2;
  3. IMS Question & Test Interoperability: ASI XML Binding Specification, Version 1.2;
  4. IMS Question & Test Interoperability: ASI Best Practice & Implementation Guide, Version 1.2;
  5. IMS Question & Test Interoperability: ASI Selection & Ordering, Version 1.2;
  6. IMS Question & Test Interoperability: ASI Outcomes Processing Specification, Version 1.2;
  7. IMS Question & Test Interoperability: QTILite Specification, Version 1.2;
  8. IMS Question & Test Interoperability: Results Reporting Information Model, Version 1.2;
  9. IMS Question & Test Interoperability: Results Reporting XML Binding, Version 1.2;
  10. IMS Question & Test Interoperability: Results Reporting Best Practice & Implementation Guide, Version 1.2;
  11. IMS Question & Test Interoperability: An Overview, Version 1.2;
  12. IMS QTI V1.2.1 DTDS and XSDs set;
  13. IMS QTI V1.2.1 Examples set.

Appendix A - The Initial Issues List

The full set of issues addressed is shown in Table A11. The possible status of each issue is defined as:

Table A1 - The list of issues considered for resolution as part of the IMS QTI v1.2.1 release.

Issue Identifier Status Comment
qti-20011214-01
 Deferred
 Inclusion of the <render_menu> element to provide a menu-based question rendering.
qti-20020114-01
 Deferred
 Clarification on the operation of comparators on the values of the QTI-specific and IMS meta-data.
qti-20020211-01
 Closed/Actioned
 Full description of the <reference> element in Items.
qti-20020211-02
 Closed/Rejected
 The organization and ordering of the <decvar> and <interpretvar> elements in <outcomes> needs to be finalised to permit multiple <interpretvar>s for each <decvar>.
qti-20020211-03
 Closed/Actioned
 The Object-bank examples are missing from the V1.2 Examples in the distribution kit.
qti-20020211-04
 Closed/Actioned
 Provision of the Advanced Chinese Examples that conform to the IMS QTI V1.2.1 specifications.
qti-20020211-05
 Closed/Rejected
 There is an issue of an ambiguity in the ASI DTD when using the XEmacs for XML parser.
qti-20020211-06
 Deferred
 Inconsistencies between the ASI and Results Reporting specifications for the enumerations and naming conventions of some attributes.
qti-20020211-07
 Closed/Actioned
 The file 'imsqtiv1p2_metadata.txt' is missing from the distribution kit. It is named as being supplied in the IMS QTI specifications.
qti-20020211-08
 Closed/Actioned
 Typographic correction on Page 20 of the IMS QTI Results Reporting Best Practice & Implementation Guide and the example file 'ims_qtiresv1p2/item/qtires_item_mc01.xml'.
qti-20020211-09
 Closed/Rejected
 Clarification on how to report a 'No' correct response in the case of multiple responses when the number of choices exceeds the correct number of answers.
qti-20020211-10
 Deferred
 ETS issues presented as part of the IMS QTI V1.2 Final Release vote.
qti-20020211-11
 Closed/Actioned
 Typographic changes in Sections 3.5.17.2 and 3.5.19.2 of the IMS QTI ASI XML Binding and the usage of the <material_ref> element.
qti-20020211-12
 Closed/Actioned
 Typographic changes in Section 3.5.25.3 and the number of occurrences of the <setvar> element in the <respcondition> element.
qti-20020211-13
 Closed/Actioned
 Typographic correction in Section 3.5.20 of the IMS QTI ASI: XML Binding document.
qti-20020211-14
 Closed/Actioned
 Typographic correction in the IMS QTI ASI: Best Practice document such that the 'orientation' attribute on the <ims_render_object> should be made optional. The associated example files should also be changed.
qti-20020211-15
 Closed/Actioned
 The e-dtype' token should be removed from the non-commented full ASI DTD for the 'sequence_parameter' attribute.
qti-20020211-16
 Deferred
 There is a bug in the data model for the <selection> element in the IMS QTI ASI: Selection & Ordering document. The style should be similar to that in the Outcome Processing document.
qti-20020211-17
 Closed/Actioned
 Typographic corrections on page 96 of the IMS QTI ASI: Best Practice & Implementation Guide document.
qti-20020211-18
 Closed/Rejected
 Typographic correction on page 25 of the IMS QTI ASI: Information Model document.
qti-20020211-19
 Closed/Actioned
 The reference to the URL at Question Mark should be removed from the example: 'advanced:mixd_imr_101/mixd_imr_101.xml'.
qti-20020211-20
 Closed/Actioned
 Typographic changes in Section 5 of the IMS QTI ASI: Information Model document.
qti-20020211-21
 Closed/Actioned
 The 'embedded' attribute is missing from the <matapplication> element description in the IMS QTI ASI: Information Model document.
qti-20020211-22
 Closed/Actioned
 The images and audio files for the examples are missing from the Example folder files.
qti-20020211-23
 Closed/Actioned
 In the IMS QTI ASI: Selection & Ordering specification there are typographic changes required on pages 10 and 18.
qti-20020211-24
 Closed/Actioned
 Typographic error on page 17 of the IMS QTI ASI: Selection & Ordering document.
qti-20020211-25
 Deferred
 In the IMS QTI ASI: Selection & Ordering document the description of the repeat mechanism in the selection and ordering process needs to be corrected.
qti-20020211-26
 Closed/Actioned
 Clarification on the functional operation of the <varsubstring> element.
qti-20020211-27
 Closed/Rejected
 Typographic correction on page 127 of the IMS QTI ASI: Best Practice & Implementation Guide.
qti-20020211-28
 Closed/Actioned
 Typographic corrections on page 12 (Section 2.4) of the IMS QTI ASI: Outcomes Processing document.
qti-20020211-29
 Closed/Actioned
 Typographic corrections on pages 26 and 32 of the IMS QTI ASI: XML Binding document.
qti-20020211-30
 Closed/Rejected
 Clarification of the outcomes processing algorithms as described in pages 40-42, of the IMS QTI ASI: Outcomes Processing document.
qti-20020211-31
 Closed/Actioned
 In the IMS QTI ASI: Best Practice & Implementation document the definition of the 'class' attribute states that the vocabulary will be supplied in an HTML file but this file is not given.
qti-20020211-32
 Deferred
 IMS TB voting comments issued by ETS on required improvements to the specification (see also qti-20020211-10).
qti-20020211-33
 Closed/Actioned
 Clarification on the functional operation of the <varsubset> element.
qti-20020211-34
 Closed/Actioned
 Clarification on the representation of labels associated with hotspots on an image.
qti-20020211-35
 Closed/Actioned
 A proposal that mixed content should not be permitted in the <response_label> element.
qti-20020211-36
 Deferred
 Usage of a co-ordinate system that is relative to the image as opposed absolute with respect to the virtual display.
qti-20020211-37
 Deferred
 Support for the exchange of tracking information (information about transient states) using the IMS QTI Result Reporting mechanism.
qti-20020211-38
 Deferred
 Explicit meta-data support on the <material> and <altmaterial> elements.
qti-20020211-39
 Deferred
 Support for adaptive selection and ordering in which the objects to be selected and ordered is dependent upon the past responses of the participant.
qti-20020211-40
 Deferred
 Support for adaptive outcomes processing in which the aggregation is dependent on past states in the assessment.
qti-20020211-41
 Deferred
 Support for new Items by extending the current set of response and render types.
qti-20020211-42
 Deferred
 Support for adaptive Items i.e. Items that are dynamically generated depending on previous participant responses.
qti-20020211-43
 Deferred
 Support for alternative response processing mechanisms in Items. This uses predefined algorithms as per the outcomes processing mechanism added in V1.2.
qti-20020211-44
 Deferred
 Inclusion of support for a human-rater scoring mechanism in Items based upon a patterns definition mechanism.
qti-20020211-45
 Deferred
 A total reworking of the QTI content model as defined by the <material> element.
qti-20020211-46
 Deferred
 The introduction of Accessibility support capabilities.
qti-20020211-47
 Deferred
 The introduction of navigation control within Sections to enable functions such as 'skipping' etc. of Items and/or Sections.
qti-20020211-48
 Deferred
 The addition of a new Selection algorithm based upon participant control.
qti-20020211-49
 Deferred
 The provision of an outcomes processing algorithm that supports rescaling as part of the aggregation mechanism.
qti-20020211-50
 Deferred
 Within the Selection & Ordering mechanism the inclusion of the capability to include or exclude Items/Sections depending on the selection or otherwise of other Items/Sections.
qti-20020211-51
 Deferred
 Provision of the <render_menu> element to support menus in the rendering capability.
qti-20020211-52
 Deferred
 The usage of multiple namespaces for different data structures within the specification.
qti-20020211-53
 Deferred
 The creation of four separate XML schemas - one for each core data object.
qti-20020211-54
 Deferred
 Creation of a QTI profile for the IMS Meta-data specification.
qti-20020211-55
 Deferred
 The creation of data-typing for the data structures within the QTI-specific meta-data.
qti-20020211-56
 Deferred
 Changing the co-ordinate system so that it is relative to the image and not to the top left hand corner of the virtual display.
qti-20020315-01
 Closed/Actioned
 Typographic correction in Section 4.1.6 of the IMS QTI ASI: Best Practice document.
qti-20020315-02
 Deferred
 Clarification on the behaviour for all of the combinations of the <response_***> with each of the <render_***> elements.
qti-20020322-01
 Closed/Actioned
 Clarification on the definition of the area bounded by an 'Ellipse' in the IMS QTI ASI: Information Model.
qti-20020408-01
 Deferred
 Support for regular expression matching elements other that those of <varsubset> and <varsubstring>.
qti-20020419-01
 Deferred
 Support for non-unique response labels i.e. a common response label identifier for more than one response label.
qti-20020419-02
 Closed/Actioned
 Clarification on the permitted values for the QTI-specific meta-data fields such as 'qmd_itemtype' etc.
qti-20020509-01
 Deferred
 The explicit identification of the 'correct' answer(s) in the definition of the Item.
qti-20020523-01
 Deferred
 Support for multivariate conditional branching logic as a part of ASI sequencing.
qti-20020607-01
 Deferred
 The ability to supply a file as part of a user response i.e. the uploading of a file as a response.
qti-20020607-02
 Closed/Actioned
 Clarification in the IMS QTIASI: Information Model on the default conditions for the control switches when the <itemcontrol> element is not used.
qti-20021108-01
 Closed/Actioned
 Various typographic corrections in the IMS QTI ASI: Information Model.
qti-20021114-01
 Closed/Actioned
 Typographic errors in the IMS QTI ASI: Outcomes Processing document.
qti-20021114-02
 Closed/Rejected
 Typographic errors in the <responselabel> element within the ims_qtiasiv1p2.xsd.xml file.
qti-20021129-01
 Closed/Actioned
 Increase the multiplicity of the <flow> element within <presentation>.
qti-20021129-02
 Closed/Actioned
 Permit the usage of any combination of <flow> and <material> elements within the <presentation> element.
qti-20021129-03
 Closed/Actioned
 The usage and multiplicity of the <qticomment> element in the specification.
qti-20021129-04
 Closed/Rejected
 Support for any ordering of the <rubric> and <objectives> elements.
qti-20021129-05
 Closed/Rejected
 Explanation of why the <response_na> element occurs as located within the <render_***> elements.
qti-20021129-06
 Closed/Rejected
 Clarification on the ordering of the <setvar> and <displayfeedback> elements.
qti-20021129-07
 Deferred
 Support for wider usage of implicit 'anding'.
qti-20021129-08
 Deferred
 Confusion over the 'minnumber' and 'maxnumber' attributes on the <render_choice> element and the 'rcardinality' attribute on <response_lid'>.
qti-20021129-09
 Closed/Rejected
 Support for multiple occurrences of the <material> element in <response_***> elements.
qti-20021129-10
 Deferred
 The usage of the 'Index' attribute on the <var***> elements.
qti-20021129-11
 Closed/Actioned
 The default display of <rubric> information.
qti-20021129-12
 Deferred
 Support for random numbers.
qti-20021202-01
 Deferred
 Clarification of the different ways in which ASI objects can be packaged using IMS Content Packaging.
qti-20021202-02
 Deferred
 Forcing the <conditionvar> element to return a state of 'True' thereby always triggering associated feedback.