1EdTech Question and Test Interoperability Addendum

Version 1.2.1 Final Specification

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.

qti-20020607-02

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.

qti-20020607-02

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.

qti-20020607-02

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.

qti-20020322-01

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.

qti-20020211-26

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.

qti-20020322-01

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.

qti-20020607-02

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.

qti-20021129-11

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'.

qti-20020211-26

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:

qti-20021129-01 and qti-20021129-02

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.

qti-20021202-03

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.

qti-20020211-34 and qti-20020211-35

Page 4.

Change the lines in Section 1.2
From:

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

To:

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

qti-20021108-01

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.

qti-20021108-01

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 1EdTech QTI ASI Selection & Ordering Specification [QTI, 02c].

To:
The detailed definition and description of the selection and ordering is supplied in the 1EdTech 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.

qti-20021108-01

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 1EdTech QTI ASI Selection & Ordering Specification [QTI, 02c].

To:
The detailed definition and description of the selection and ordering is supplied in the 1EdTech 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.

qti-20021108-01

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.

qti-20021108-01

Page 32.

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

<blank>

To:
'n'.

qti-20021108-01

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.

qti-20021108-01

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.

qti-20021108-01

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.

qti-20020211-01

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.

qti-20020211-21

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.

qti-20020211-33

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.

qti-20020211-33

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

qti-20020211-20

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.

qti-20021129-03

Page 48.

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

'n'

To:
<blank>

qti-20021129-03

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>.

qti-20021108-01

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".

qti-20020211-07

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"/>

qti-20020211-07

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.

qti-20020211-29

Page 26.

Replace Figure 3.9
With:

qti-20020211-01

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.

qti-20020211-29

Page 36.

Replace Figure 3.14
With:

qti-20021129-03

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.

qti-20020211-11

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.

qti-20020211-11

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.

qti-20020211-13

Page 51.

Replace Figure 3.25
With:

qti-20021129-03

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.

qti-20020211-12

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.

qti-20020211-01

Page 68.

Replace Figure 3.3
With:

qti-20021129-03

Page 82.

Replace Figure 3.41
With:

qti-20021129-03

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"/>

qti-20020211-07

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"/>

qti-20020211-07

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"/>

qti-20020211-07

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>

qti-20020211-17

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.

qti-20020211-31

Page 17.

Change Figure 3.1 to:

qti-20021203-01

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>

qti-20020211-23

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.

qti-20020211-23

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.

qti-20020211-23

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"

qti-20020211-28

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

qti-20021114-01

Page 16.

Change line 11 of the multiple choice Item example
From:

<correct_response>T</correct_response>

To:
<correct_response>B</correct_response>

qti-20020211-08

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.

qti-20021208-02

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

qti-20020211-15

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

General

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

qti-20020211-03

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

qti-20020211-04

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.

qti-20020211-14

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.

qti-20020211-19

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.

qti-20020211-22

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.

qti-20020211-08

Can Studios, Ltd.

Can Studios, Ltd.

University of Cambridge Local Examinations Syndicate, UK

Can Studios, Ltd.

1EdTech

Final 1.2.1

31 March 2003

The first formal release of this 1EdTech QTI Addendum document that describes the amendments and errata changes to be made to the 1EdTech QTI v1.2 Specification.