Final Specification Version 1.2
|
IMS Question & Test Interoperability: Results Reporting XML Binding
Final Specification Version 1.2 |
|
Copyright © 2002 IMS Global Learning Consortium, Inc. All Rights Reserved. The IMS Logo is a trademark of IMS Global Learning Consortium, Inc. Document Name: IMS Question & Test Interoperability: Results Reporting XML Binding Date: 11 February 2002
|
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 © 2002 IMS Global Learning Consortium. All Rights Reserved.
Permission is granted to all parties to use excerpts from this document as needed in producing requests for proposals.
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/license.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.
The IMS Question & Test Interoperability (QTI) specification describes a basic structure for the representation of question (item) and test (assessment) data and their corresponding results reports. Therefore, the specification enables the exchange of this item, 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. The QTI specification, like all IMS specifications, does not limit product designs by specifying user interfaces, pedagogical paradigms, or establishing technology or policies that constrain innovation, interoperability, or reuse.
This document describes the implementation of the Results Reporting information model in XML. XML is introduced by outlining XML basics, including a conceptual discussion of the XML schema. The XML schema description of the QTI specification (ims_qtiresrootv1p2.xsd and ims_qtiresv1p2.dtd) defines the results report objects as XML elements. An example schema is included, along with details of the meta-data used to catalogue the results report.
This document is the IMS Question & Test Interoperability: Results Reporting XML Binding V1.2 Base Document. As such it will be used as the basis for the development of the following documents:
This requirement has been derived from the agreed IMS Q&TI V1.x Scoping document [QTI, 00] and the IMS QTI Results Reporting Information Model V1.2 [QTI, 02d]. This XML Binding complements the IMS QTI: ASI XML Binding [QTI, 02b] but it can be applied to assessments that have not been represented using that specification.
The structure of this document is:
| 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 |
The Question & Test Interoperability data model can be defined as a hierarchy. Hierarchical models are convenient for representing data consisting of many elements and sub-elements. XML is perfectly suited for representing hierarchical models. An XML document is a hierarchy comprised of elements that have contents and attributes.
An element is a component of a document that has been identified in a way a computer can understand. Each element has a tag name. When a tag name is shown as "<TAGNAME>", with less-than and greater-than symbols before and after the tag name, it serves as the start-tag to mark the beginning of an element. When that same tag name has a forward slash "/" added, it serves as an end-tag such as "</TAGNAME>". An element may have contents between its start and end-tags and may have one or more attributes. When an XML element has a start and end-tag (also called an opening and closing tag) with a common name, it is considered to be "well-formed" XML. The contents of an element are placed between the start and end-tags as shown below:
<TAGNAME>contents</TAGNAME>
An element may contain other elements, Parsed Character Data (PCDATA), Character Data (CDATA), or a mixture of PCDATA and elements. The allowable contents of an element are its content model. PCDATA really means any character string that does not contain elements. PCDATA is what the bulk of elements will use between their start and end-tags. CDATA is different in that it is a method for adding any character data that should not be processed. For example, you could add some Java script code instructions using a CDATA section. A CDATA section tells the parser not to look for any markup until after it locates the end of the CDATA section.
An attribute provides additional information about an element. Attributes are a way of attaching characteristics or properties to the elements of a document. An element may have more than one attribute and they are contained within the start tag of an element. Attributes are represented by an attribute name followed by an equal sign and the attribute value in quotation marks:
<timeframe>
<begin restrict="1">1999-07-23</begin>
</timeframe>
In this example the <timeframe> element contains another element, the <begin> element. The <begin> element has one attribute "restrict", with the value 1. The value for the element <begin> is "1999-07-23". These two elements then make up a 'timeframe begin' date.
Each element has a unique name, referred to as the tag name. XML is case-sensitive in its processing of tag names. The IMS Question & Test Interoperability XML Binding Specification adheres to the following tag name rules:
The IMS QTI Results Reporting version 1.2 XML binding is defined in an XML-Schema1. XML-Schema is the primary XML binding control document format of IMS (at present these bindings are working to the May 2001 version of XML Schema). The XML-Schema defines elements, their content models, and attributes. It also defines the standard IMS vocabularies. The XML-Schema defines the element types and attribute groups separately from the elements. This serves three purposes:
The XML Schema for the IMS QTI Results Reporting (for version 1.2) is named:
The tag name, content model, and attributes of elements are defined in a Document Type Definition (DTD) statement. These may exist as an external file or a block of text internal to an XML document. Internal DTDs should be used with care. The DTD defines the elements that may be used, and may define the contents of the elements.
This specification defines the external DTD with the file name (for version 1.2):
Some XML editors may make use of a DTD to help guide the developer in creating the proper elements at the proper locations in an XML file. Other developers will make use of the DTDs to validate their XML documents to ensure their document is consistent with all of the element names and locations defined in the DTD. An XML document is valid if it has an associated document type declaration and if the document complies with the constraints expressed in it. Details of the construction of DTDs are outside the scope of this document, but links to the XML Version 1.0 specification are included in the References section of this document.
The information specifying the order and usage of allowable contents for an element are its content model. The content model is declared in a DTD (see below). The declaration of the content model is of the general form:
<!ELEMENT tagname (Content Model)>
The SHORT element can again serve as an example of how an element is declared with its content model:
<!ELEMENT short (#PCDATA)>
This element will contain character data (#PCDATA) that can be processed. The XML Specification provides more information about the details for creating and interpreting content models.
A list is a repetition of the contents of an element. In XML, this is accomplished by repeating the containing element: for example, the section element contains an element item. Described in the DTD as:
<!ELEMENT section (item*, extension?)>
When instantiated in XML a repeating list of ITEM elements would appear:
<section>
<item> "The first question set."</item>
<item> "The second question set."</item>
</section>
In this example, the element item is repeated. Thus item is the containing element for the repeated contents descriptions. The notation for repetitions of an element in a content model follows the XML specification. An asterisk (*) specifies that none or more repetitions of the element may be included in the XML instantiation whereas a plus (+) specifies that one or more repetitions of the element may be included in the XML instantiation. The extension element is not used - a question mark (?) specifies that none or one repetitions of the element may be included.
An example of how the attributes for the element assessment is declared in a DTD is found below:
<!ELEMENT assessment (description, section+, objectives?, result, extension?)> <!ATTLIST assessment title CDATA #IMPLIED>
The first line declares that there is an element named assessment that must have the description, section and result elements and is additionally allowed to have objectives and/or extension elements as its contents. The second line begins with "!ATTLIST" to start an attribute list declaration for the assessment element. The word title will serve as the attribute's name. The allowable value for this attribute must be of type CDATA.
At the end of the example above is the term IMPLIED. It is at this location in the attribute declaration, where a default value for an attribute may be specified. It is also possible to use the keyword REQUIRED which would force a TYPE value to be supplied and there would be no default value. In the example above, the IMPLIED designation means that the designer wants to allow users to omit the value for the attribute without forcing a particular default value.
Within the IMS XML binding, the use of attributes is reserved for information about the structure of the relevant data object. This means that an attribute is used to create a specific type of element e.g. the element could be the date and its attribute could be used to define the date as the date of birth.
Some characters used in XML must be escaped when used outside of their XML defined usage as found in Section 2.4 of the XML 1.0 Specification. These characters are ampersand (&), less than (<), greater than (>), apostrophe(') and the double-quotes character("). These characters may be represented using either numeric character references or the strings ",&", "<", ">", "'", and """. Below is a more complete quote from the W3C XML specification:
Quote from Extensible Markup Language (XML) 1.0
W3C Recommendation 10-February-1998
2.4 Character Data and Markup
Text consists of intermingled character data and markup. Markup takes the form of start-tags, end-tags, empty-element tags, entity references, character references, comments, CDATA section delimiters, document type declarations, and processing instructions.
All text that is not markup constitutes the character data of the document.
The ampersand character (&) and the left angle bracket(<) may appear in their literal form only when used as markup delimiters or within a comment, a processing instruction or a CDATA section. They are also legal within the literal entity value of an internal entity declaration; see "4.3.2 Well-Formed Parsed Entities". If they are needed elsewhere, they must be escaped using either numeric character references or the strings "&" and "<" respectively. The right angle bracket (>) may be represented using the string ">" and must, for compatibility, be escaped using ">" or a character reference when it appears in the string "]]>" in content, when that string is not marking the end of a CDATA section.
In the content of elements, character data is any string of characters which does not contain the start delimiter of any markup. In a CDATA section, character data is any string of characters not including the CDATA-section-close delimiter, "]]>".
To allow attribute values to contain both single and double quotes, the apostrophe or single-quote character (') may be represented as "'", and the double-quote character (") as """.
Questions arise as to whether web-based data transmission tools might inadvertently strip-off or transform some of the white space characters embedded in the Enterprise data transmitted between systems using XML. To eliminate concern about this issue, refer to the following quote from the W3C XML standards, which indicate that all white space must be preserved where it is part of the data.
Quote from Extensible Markup Language (XML) 1.0
W3C Recommendation 10-February-1998
2.10 White Space Handling
In editing XML documents, it is often convenient to use "white space" (spaces, tabs, and blank lines, denoted by the non-terminal S in this specification) to set apart the markup for greater readability. Such white space is typically not intended for inclusion in the delivered version of the document. On the other hand, "significant" white space that should be preserved in the delivered version is common, for example in poetry and source code.
An XML processor must always pass all characters in a document that are not markup through to the application. A validating XML processor must also inform the application which of these characters constitute white space appearing in element content.
A special attribute named xml:space may be attached to an element to signal an intention that in that element, white space should be preserved by applications. In valid documents, this attribute, like any other, must be declared if it is used. When declared, it must be given as an enumerated type whose only possible values are "default" and "preserve". For example:
<!ATTLIST poem xml:space (default | preserve)'preserve'>
The value "default" signals that applications' default white-space processing modes are acceptable for this element; the value "preserve" indicates the intent that applications preserve all the white space. This declared intent is considered to apply to all elements within the content of the element where it is specified, unless overridden with another instance of the xml:space attribute.
Some providers will find the current element set defined in the QTI specification too restrictive to accomplish their purposes. To ensure extensibility, the specification requires that there be no limit on potential extensions to major elements. An extension is the addition of information to an existing XML structure.
<!ELEMENT resp_extension ANY>
An example of the inclusion of resp_extension in the content model of element presentation is:
<!ELEMENT presentation (render_choice, render_hotspot, resp_extension?)>
The use of the resp_extension element is illustrated as follows:
<presentation>
<render_choice> ... Multiple choice selections ... </render_choice>
<render_hotspot> ... Image hot spot selections ... </render_hotspot>
<resp_extension>
<comment>This is a test to demo extensions</comment>
</resp_extension>
</presentation>
The contents, but not a content model, of an extension must be declared in an internal or external DTD. Many extensions can be created through the use of existing elements. Care must be used with internal DTDs, as they over-ride external DTD declarations. The content of an extension must obey the attribute and content models of the elements employed. New elements that duplicate the definitions of existing elements should not be introduced.
Prefacing the resp_extension element with an appropriate namespace may reference descriptions of extensions. For example, a group such as the Advanced Distributed Learning (ADL) initiative may wish to add the "adl" prefix to an extension element to uniquely identify ADL extensions (the prefix must be declared in the head of the XML instance). The following is an example of this:
<item>
... mandatory elements of item elements here ...
<description lang= " en " >
<short>Military psychometric question </short>
</description>
<adl:resp_extension adl:classification="Not classified">
<adl:comment>Discusses how the questions are constructed for defence posts.
<adl:comment>
</adl:resp_extension>
</item>
This serves to note the entire extension structure. Extensions should always be added at the lowest point (farthest from the root element) in the hierarchy possible, to the degree that the structure defines the meaning of the extension.
This specification defines the XML format using narrative.
Description: The <qti_result_report> element is the outermost container for the QTI results report i.e. the container of the Assessment results, Section results, Item results and summary results.
Multiplicity: The <qti_result_report> occurs only once in each XML instance file that is used to support results reports.
Description: This element contains the comments that are relevant to the structure as a whole.
Multiplicity: Occurs zero or once within the <qti_result_report> element.
Attributes: As per sub-section 3.8.1.
Description: The <result> element is used to contain the information about an actual evaluation undertaken by a participant. Each result can contain information about either a single Assessment, or Section, or Item, or summary information about an evaluation.
Multiplicity: The <result> occurs once or more times within the <qti_result_report> element.
Attributes: As per sub-section 3.2.
Description: The <result> element is used to contain the information about an actual evaluation undertaken by a participant. Each result can contain information about either a single Assessment, or Section, or Item, or summary information about an evaluation.
Multiplicity: The <result> occurs once or more times within the <qtiresreport> element.
Description: This element contains the comments that are relevant to the context data structure.
Multiplicity: Occurs zero or once within the <result> element.
Attributes: As per sub-section 3.8.1.
Description: This element is used to set the context for the set of results being reported.
Multiplicity: Occurs once within the <result> element.
Attributes: As per sub-section 3.3.
Description: This element is used to contain the set of summary results that are being reported.
Multiplicity: Occurs zero or once within the <result> element.
Attributes: As per sub-section 3.4.
Description: This element is used to contain the Assessment result that is being reported.
Multiplicity: Occurs zero or once within the <result> element.
Attributes: As per sub-section 3.5.
Description: This element is used to contain the Section result that is being reported.
Multiplicity: Occurs zero or once within the <result> element.
Attributes: As per sub-section 3.6.
Description: This element is used to contain the Item result that is being reported.
Multiplicity: Occurs zero or once within the <result> element.
Attributes: As per sub-section 3.7.
Description: This element is use to support proprietary extensions to the <result> structure.
Multiplicity: Occurs zero or once within the <result> element.
Description: The <context> element is used to contain the information about an actual evaluation undertaken by a participant. Each instance can contain information about either a single Assessment, or one or more Sections, or one or more Items. Summary information about the evaluation may also be contained.
Multiplicity: Occurs once or more in the <result> element.
Description: This element contains the comments that are relevant to the context.
Multiplicity: Occurs zero or once within the <context> element.
Attributes: As per sub-section 3.8.1.
Description: This element is use to store the formatted name of the participant undertaking the evaluation. The data-type is a string (1-256 chars).
Multiplicity: Occurs zero or once within the <context> element.
Description: This element stores the appropriate identifiers that are required to uniquely describe the evaluation, the participant and the host environment. Each identifier is described using it's own instance.
Multiplicity: Occurs zero or more times within the <context> element.
Attributes: As per sub-section 3.8.2.
Description: This element stores the appropriate dates that correspond to the evaluation. Each date is stored in it's own instance.
Multiplicity: Occurs zero or more times within the <context> element.
Attributes: As per sub-section 3.8.3.
Description: This element is used to support proprietary extensions to the <context> structure.
Multiplicity: Occurs zero or once within the <context> element.
Description: The <summary_result> element is used to contain the information that is a summary of the evaluation undertaken. This summary may be for a single Assessment, Section or Item.
Multiplicity: Occurs zero or once within the <result> element.
Description: This element contains the comments that are relevant to the structure as a whole.
Multiplicity: Occurs zero or once within the <summary_result> element.
Attributes: As per sub-section 3.8.1.
Description: This element is used to identify the type of summary result e.g. an Assessment summary, an Item summary, etc.
Multiplicity: Occurs zero or once within the <summary_result> element.
Description: This element stores the appropriate identifiers that are required to uniquely describe the summary results from the evaluation. Each identifier is described using it's own instance.
Multiplicity: Occurs zero or more times within the <summary_result> element.
Attributes: As per sub-section 3.8.2.
Description: This element stores the appropriate dates that correspond to the evaluation summary results. Each date is stored in it's own instance.
Multiplicity: Occurs zero or more times within the <summary_result> element.
Attributes: As per sub-section 3.8.3.
Description: This element stores the status of the evaluation. This status describes the current state of the evaluation e.g. 'complete', 'active', etc. A predefined vocabulary is to be made available (see the QTI Results Reporting Information Model).
Multiplicity: Occurs zero or once within the <summary_result> element.
Attributes: As per sub-section 3.8.7.
Description: This element stores the time taken to reach the current state of the evaluation. The duration is recorded using the ISO8601 format.
Multiplicity: Occurs zero or once within the <summary_result> element.
Description: This element stores the numerical score from the primary scoring variable used within the evaluation.
Multiplicity: Occurs zero or once within the <summary_result> element.
Attributes: As per sub-section 3.8.8.
Description: This element stores the grade variables used within the evaluation.
Multiplicity: Occurs zero or once within the <summary_result> element.
Attributes: As per sub-section 3.8.9.
Description: This element is used to store the summary results other than those recorded already recorded in the <score> and <grade> elements.
Multiplicity: Occurs zero or once within the <summary_result> element.
Attributes: As per sub-section 3.8.6.
Description: This element is use to support proprietary extensions to the <summary_result> structure.
Multiplicity: Occurs zero or once within the <summary_result> element.
Description: The <assessment_result> element is the container for results data that is specific to a particular Assessment. The Assessment information may include results about the contained Section(s) and/or Items(s).
Multiplicity: Occurs zero or once in the <result> element.
Description: This element contains the comments that are relevant Assessment result summary.
Multiplicity: Occurs zero or once within the <assessment_result> element.
Attributes: As per sub-section 3.8.1.
Description: The container for all of the vocabulary based QTI-specific meta-data.
Multiplicity: Occurs zero or once within the <assessment_result> element.
Attributes: As per sub-section 3.8.4.
Description: This element is used to store a textual description of the Assessment itself or to point to a file containing the appropriate description of the Assessment. String (1-2048 chars).
Multiplicity: Occurs zero or once within the <assessment_result> element.
Description: This element stores the appropriate dates that correspond to the Assessment results. Each date is stored in it's own instance.
Multiplicity: Occurs zero or more times within the <assessment_result> element.
Attributes: As per sub-section 3.8.3.
Description: This element stores the time taken to reach the current state of the Assessment. The duration is recorded using the ISO8601 format.
Multiplicity: Occurs zero or once within the <assessment_result> element.
Description: A record of the objectives that are covered by the Assessment. Mastery of this Assessment implies that the participant has learnt the associated learning objectives.
Multiplicity: Occurs zero or more times within the <assessment_result> element.
Description: A record of the feedback mechanisms that were revealed to the participant as a part of the evaluation. Contains a string that summarizes the control switch status.
Data-type = String (max of 128 chars).
Multiplicity: Occurs zero or once within the <assessment_result> element.
Description: This element is used to store the actual Assessment results being recorded. Any number of numeric scores or grades can be recorded.
Multiplicity: Occurs zero or once within the <assessment_result> element.
Attributes: As per sub-section 3.8.6.
Description: This element is used to describe the type of feedback shown to the participant.
Multiplicity: Occurs zero or more times within the <assessment_result> element.
Description: The total number of Items that are contained and referenced by the Assessment.
Data-type = String (max of 32 chars representing the number 1-231-1).
Multiplicity: Occurs zero or once within the <assessment_result> element.
Description: The number of Sections that are contained by the Assessment.
Data-type = String (max of 32 chars representing the number 1-231-1).
Multiplicity: Occurs zero or once within the <assessment_result> element.
Description: The number of Items that have been presented to the participant as part of the Assessment.
Data-type = String (max of 32 chars representing the number 1-231-1).
Multiplicity: Occurs zero or once within the <assessment_result> element.
Description: The number of Items that have been attempted the participant as part of the Assessment.
Data-type = String (max of 32 chars representing the number 1-231-1).
Multiplicity: Occurs zero or once within the <assessment_result> element.
Description: The number of Sections that have been presented to the participant as part of the Assessment.
Data-type = String (max of 32 chars representing the number 1-231-1).
Multiplicity: Occurs zero or once within the <assessment_result> element.
Description: This element is used to contain the set of Section results that are being reported within the Assessment.
Multiplicity: Occurs zero or more times within the <assessment_result> element.
Attributes: As per sub-section 3.6.
Description: This element is use to support proprietary extensions to the <assessment_result> structure.
Multiplicity: Occurs zero or once within the <assessment_result> element.
Description: The <section_result> element is the container for results data that is specific to a particular Section. The Section information may include results about the contained Section(s) and/or Items(s).
Multiplicity: Occurs zero or once within the <result> element.
Description: This element contains the comments that are relevant Section result summary.
Multiplicity: Occurs zero or once within the <section_result> element.
Attributes: As per sub-section 3.8.1.
Description: The container for all of the vocabulary based QTI-specific meta-data.
Multiplicity: Occurs zero or once within the <section_result> element.
Description: This element is used to store a textual description of the Section itself or to point to a file containing the appropriate description of the Section.
Multiplicity: Occurs zero or once within the <section_result> element.
Description: This element stores the appropriate dates that correspond to the Section results. Each date is stored in it's own instance.
Multiplicity: Occurs zero or more times within the <section_result> element.
Attributes: As per sub-section 3.8.3.
Description: This element stores the time taken to reach the current state of the Section. The duration is recorded using the ISO8601 format.
Multiplicity: Occurs zero or once within the <section_result> element.
Description: A record of the objectives that are covered by the Section. Mastery of this Section implies that the participant has learnt the associated learning objectives.
Multiplicity: Occurs zero or more times within the <section_result> element.
Description: A record of the feedback mechanisms that were revealed to the participant as a part of the evaluation.
Multiplicity: Occurs zero or once within the <section_result> element.
Description: This element is used to store the actual Section results being recorded. Any number of numeric scores or grades can be recorded.
Multiplicity: Occurs zero or once within the <section_result> element.
Attributes: As per sub-section 3.8.6.
Description: This element is used to describe the type of feedback shown to the participant.
Multiplicity: Occurs zero or more times within the <section_result> element.
Description: The number of Items that are contained and referenced by the Section.
Data-type = String (max of 32 chars representing the number 1-231-1).
Multiplicity: Occurs zero or once within the <section_result> element.
Description: The number of Sections that are contained by the Section.
Data-type = String (max of 32 chars representing the number 1-231-1).
Multiplicity: Occurs zero or once within the <section_result> element.
Description: The number of Items that have been presented to the participant as part of the Section.
Data-type = String (max of 32 chars representing the number 1-231-1).
Multiplicity: Occurs zero or once within the <section_result> element.
Description: The number of Items that have been attempted the participant as part of the Section.
Data-type = String (max of 32 chars representing the number 1-231-1).
Multiplicity: Occurs zero or once within the <section_result> element.
Description: The number of Sections that have been presented to the participant as part of the Section.
Data-type = String (max of 32 chars representing the number 1-231-1).
Multiplicity: Occurs zero or once within the <section_result> element.
Description: This element is used to contain the set of Section results that are being reported within the Section.
Multiplicity: Occurs zero or more times within the <section_result> element.
Attributes: As per sub-section 3.6.
Description: This element is used to contain the set of Item results that are being reported within the Section.
Multiplicity: Occurs zero or more times within the <section_result> element.
Attributes: As per sub-section 3.7.
Description: This element is use to support proprietary extensions to the <section_result> structure.
Multiplicity: Occurs zero or once within the <section_result> element.
Description: The <item_result> element is the container for results data that is specific to a particular Item. The Item information may contain the actual responses supplied by the participant.
Multiplicity: Occurs zero or once in the <result> element.
Description: This element contains the comments that are relevant to the structure as a whole.
Multiplicity: Occurs zero or once within the <item_result> element.
Attributes: As per sub-section 3.8.1.
Description: The container for all of the vocabulary based QTI-specific meta-data.
Multiplicity: Occurs zero or once within the <item_result> element.
Description: This element is used to store a textual description of the Item itself or to point to a file containing the appropriate description of the Item.
Multiplicity: Occurs zero or once within the <item_result> element.
Description: This element stores the appropriate dates that correspond to the Item results. Each date is stored in it's own instance.
Multiplicity: Occurs zero or more times within the <item_result> element.
Attributes: As per sub-section 3.8.3.
Description: This element stores the time taken to reach the current state of the Item. The duration is recorded using the ISO8601 format.
Multiplicity: Occurs zero or once within the <item_result> element.
Description: A record of the objectives that are covered by the Item. Mastery of this Item implies that the participant has learnt the associated learning objectives.
Multiplicity: Occurs zero or more times within the <item_result> element.
Description: A record of the feedback mechanisms that were revealed to the participant as a part of the evaluation. Contains a string that summarizes the control switch status.
Data-type = String (max of 128 chars).
Multiplicity: Occurs zero or once within the <item_result> element.
Description: This element is used to contain the original structure of the Item presented to the participant plus the responses made by the participant in answering the question posed in the Item.
Multiplicity: Occurs once or more in the <item_result> element.
Description: This element contains the comments that are relevant to the response as a whole.
Multiplicity: Occurs zero or once within the <response> element.
Attributes: As per sub-section 3.8.1.
Description: This element is use to support proprietary extensions to the <response> structure.
Multiplicity: Occurs zero or once within the <response> element.
Description: This element is used to contain the information that describes the response structure of an Item including the nature of the responses.
Multiplicity: Occurs zero or once in the <response_form> element.
Description: This identifies the correct answer to the Item. This takes the form of either the label for the correct choice or a model answer itself.
Multiplicity: Occurs zero or more times within the <response_form> element.
Description: This element is use to support proprietary extensions to the <response_form> structure.
Multiplicity: Occurs zero or once within the <response_form> element.
Description: This is a record of the number of attempts made by the participant to answer the question. An attempt is defined as the number of separate entries into the Item itself from outside of the Item.
Data-type = String (max 4 chars to represent 1-9999).
Multiplicity: Occurs zero or once within the <response_form> element.
Description: This element contains the sequence of answers actually supplied by the participant. The number of responses should match that given in the <response_form> element and the order of the responses should be reflected in the order of the separate instances of the <response_value> element.
Multiplicity: Occurs zero or more times within the <response_form> element.
Description: This element is used to store the actual Item results being recorded. Any number of numeric scores or grades can be recorded.
Multiplicity: Occurs zero or once within the <item_result> element.
Attributes: As per sub-section 3.8.6.
Description: This element is used to describe the type of feedback shown to the participant.
Multiplicity: Occurs zero or more times within the <item_result> element.
entityref (optional). An alternative mechanism for identifying the external reference that contains the feedback description. This allows the file reference to be bound to the XML instance itself.
Data-type = String (max of 256 chars).
Description: This element is use to support proprietary extensions to the <item_result> structure.
Multiplicity: Occurs zero or once within the <item_result> element.
Description: This element contains the comments that are relevant to the host structure as a whole.
Multiplicity: Occurs zero or once within the corresponding host element.
Description: This element stores the appropriate identifiers that are required to uniquely describe the corresponding object. Each identifier is described using it's own instance.
Description: This element is used to identify the type of the corresponding data object.
Description: This element is used to store the actual identifier. This identifier would normally conform to the IMS Persistent Location-independent Resource Identifier. String (1-256 chars).
Description: This element stores the appropriate dates that are relevant to the object. Each date is stored in it's own instance.
Description: This element is used to identify the type of the corresponding data object.
Description: This element is used to store the actual date/time. This takes the form as defined in the ISO 8601 standard i.e. YYYY-MM-DDTHH:MM:SS. String (1-20 chars).
Description: The container for all of the vocabulary based QTI-specific meta-data. The corresponding vocabulary has to be defined.
Description: The vocabulary to be available to the meta-data entries. If no external source file is identified then the actual vocabulary is supplied as a comma-separated list. String 1-2048 chars.
Description: The storage for each of the individual QTI-specific meta-data entries. Each meta-data field is stored in one instance of this element.
Attributes: As per sub-section 3.8.5.
Description: The storage for each of the individual QTI-specific meta-data entries. Each meta-data field is stored in one instance of this element.
Multiplicity: Occurs once or more in the <asi_metadata> element.
Description: The name of the meta-data field.
Multiplicity: Occurs once within the <asi_metadatafield> element.
Data-type = String (1-256 chars).
Description: The data to be entered in the meta-data field.
Multiplicity: Occurs once within the <asi_metadatafield> element.
Data-type = String (1-256 chars).
Description: This element is used to store the results recorded in the score and grade variables. Any number of score and/or grades can be stored.
Description: This element stores the current status of the outcomes. A predefined vocabulary is to be made available (see the QTI Results Reporting Information Model).
Multiplicity: Occurs zero or once within the <outcomes> element.
Attributes: As per sub-section 3.8.7.
Description: This element stores a numerical score from a named variable.
Multiplicity: Occurs zero or more times within the <outcomes> element.
Attributes: As per sub-section 3.8.8.
Description: This element stores the grade variables value. A grade is defined as a member of an enumerated finite list of possible grade values.
Multiplicity: Occurs zero or more times within the <outcomes> element.
Attributes: As per sub-section 3.8.9.
Description: This element stores the status of the corresponding data object. This status describes the current state of the event e.g. 'complete', 'active', etc. A predefined vocabulary is to be made available (see the IMS QTI Results Reporting Information Model).
Description: This element is used to identify the vocabulary source for the status.
Multiplicity: Occurs zero or once within the <status> element.
Description: This element is used to store the actual date/time for when the status is being recorded. This takes the form as defined in the ISO 8601 standard i.e. YYYY-MM-DDTHH:MM:SS. String (1-20 chars).
Description: The actual status of the event taken from the possible vocabulary. String (1-32 chars).
Multiplicity: Occurs once within the <status> element.
Description: This element stores the numerical score from a scoring variable used within the evaluation.
Description: The numerical value that is to be assigned to the named variable.
Data-type=String (1-32 chars).
Multiplicity: Occurs once within the <score> element.
Description: A description that describes the ways in which the score should be interpreted. An example of this is to describe the conversion mapping to a grade.
Data-type=String (1-2048 chars).
Multiplicity: Occurs zero or once within the <score> element.
Description: The minimum value that could be assigned to the named scoring variable. This value is only valid for numeric typed variables.
Data-type=String (1-32 chars).
Multiplicity: Occurs zero or once within the <score> element.
Description: The maximum value that could be assigned to the named scoring variable. This value is only valid for numeric typed variables.
Data-type=String (1-32 chars).
Multiplicity: Occurs zero or once within the <score> element.
Description: The normalized numerical value that is to be assigned to the named variable. This value is only valid for numeric typed variables.
Data-type=String (1-32 chars).
Multiplicity: Occurs once within the <score> element.
Description: The average score that could be assigned to this variable. This is not calculated from the assessment engine but is merely reported.
Data-type=String (1-32 chars).
Multiplicity: Occurs zero or once within the <score> element.
Description: The standard error for the score assigned to this variable. This is not calculated from the assessment engine but is merely reported. This value is only valid for numeric typed variables.
Data-type=String (1-32 chars).
Multiplicity: Occurs zero or once within the <score> element.
Description: A reliability metric used to describe the recorded score. This is not calculated from the assessment engine but is merely reported. This value is only valid for numeric typed variables.
Data-type=String (1-32 chars).
Multiplicity: Occurs zero or once within the <score> element.
Description: The numerical value which if obtained is used to define mastery or to act as a pass mark.
Data-type=String (1-32 chars).
Multiplicity: Occurs zero or once within the <score> element.
Description: This element is use to support proprietary extensions to the <score> structure.
Multiplicity: Occurs zero or once within the <score> element.
Description: This element stores a grade value.
Description: The grade that has been assigned to the named variable.
Data-type=String (1-64 chars).
Multiplicity: Occurs once within the <score> element.
Description: The grade value which if obtained is used to define mastery or to act as a pass mark. This value will be one entry from the list supplied in the members attribute of <grade>.
Data-type=String (1-32 chars).
Multiplicity: Occurs zero or once within the <score> element.
Description: This element is use to support proprietary extensions to the <grade> structure.
Multiplicity: Occurs zero or once within the <grade> element.
The XML Binding has been released as XSDs and a DTD. The DTD realization is a single file. The XSD is implemented a series of files which are linked using the XML XSD 'include' statement. The reasons for this approach are:
In the case where there is any discrepancy between the Information Model document, the XML Binding document and the DTD, then the DTD should be taken as the definitive statement of correctness. Unlike the written documents, the DTD this has been extensively tested using example XML instances.
Each of the following simple examples focuses on one of the core data structures. In each case it is assumed that the full set of information is being supplied.
This is a typical summary report. It gives the score assigned to the full assessment and the corresponding grade that was achieved.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 |
<qti_result_report>
<result>
<context>
<name>Jimmy Olsen</name>
<generic_identifier>
<type_label>SSN</type_label>
<identifier_string>DoL:355926874A</identifier_string>
</generic_identifier>
<date>
<type_label>Exam</type_label>
<datetime>2001-08-06T00:00:00</datetime>
</date>
</context>
<summary_result>
<type_label>Assessment</type_label>
<generic_identifier>
<type_label>Assessment Id</type_label>
<identifier_string>TestCo:84692</identifier_string>
</generic_identifier>
<date>
<type_label>Exam</type_label>
<datetime>2001-08-06T00:00:00</datetime>
</date>
<status>
<status_value>Complete</status_value>
</status>
<duration>P0Y0M0DT1H0M0S</duration>
<score varname = "SCORE" vartype = "Integer">
<score_value>65</score_value>
<score_min>0</score_min>
<score_max>100</score_max>
<score_cut>50</score_cut>
</score>
<grade members="16,15,14,13,12,11,10,9,8,7,6,5,4,3,2,1" varname="GRADE">
<grade_value>13</grade_value>
<grade_cut>10</grade_cut>
</grade>
</summary_result>
</result>
</qti_result_report>
|
The example is for a result report of a single item. The score is based upon the value assigned to the default 'SCORE' variable.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 |
<qti_result_report>
<result>
<context>
<name>Clark Kent</name>
<generic_identifier>
<type_label>Student Number</type_label>
<identifier_string>TestCo:156805D</identifier_string>
</generic_identifier>
<date>
<type_label>Exam</type_label>
<datetime>2001-08-07T14:00:00</datetime>
</date>
</context>
<item_result asi_title="Standard Multiple Choice Item"
ident_ref= "IMS_V01_I_BasicExample002b">
<date>
<type_label>Item Creation Time</type_label>
<datetime>2001-08-07T13:31:00</datetime>
</date>
<duration>P0Y0M0DT0H2M</duration>
<response ident_ref = "MCb_01">
<response_form cardinality="single" render_type="choice"
timing="No" response_type="lid">
<correct_response>B</correct_response>
</response_form>
<num_attempts>1</num_attempts>
<response_value>B</response_value>
</response>
<outcomes>
<score varname = "SCORE" vartype = "Integer">
<score_value>1</score_value>
<score_min>0</score_min>
<score_max>1</score_max>
<score_cut>1</score_cut>
</score>
</outcomes>
<feedback_displayed ident_ref = "Correct">Response</feedback_displayed>
</item_result>
</result>
</qti_result_report>
|
The example is for a result report of a single Section. The score is based upon the value assigned to the variable 'SectionScore'.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 |
<qti_result_report>
<result>
<context>
<name>Clark Kent</name>
<generic_identifier>
<type_label>Student Number</type_label>
<identifier_string>TestCo:156805D</identifier_string>
</generic_identifier>
<date>
<type_label>Exam</type_label>
<datetime>2001-08-07T14:00:00</datetime>
</date>
</context>
<section_result asi_title = "Example Section Title"
ident_ref = "IMS_V01_S_BasicSection001">
<date>
<type_label>Section Creation Time</type_label>
<datetime>2001-08-07T13:40:00</datetime>
</date>
<control hint_switch = "No" solution_switch = "No" feedback_switch = "Yes"/>
<outcomes>
<score varname = "SectionScore" vartype = "Integer">
<score_value>1</score_value>
<score_min>0</score_min>
<score_max>2</score_max>
<score_cut>1</score_cut>
</score>
</outcomes>
<feedback_displayed ident_ref = "Passed">Response</feedback_displayed>
<num_items>2</num_items>
<num_items_presented>2</num_items_presented>
<num_items_attempted>2</num_items_attempted>
<num_sections_presented>1</num_sections_presented>
</section_result>
</result>
</qti_result_report>
|
The example is for a result report of a single Section containing two Items. The score is based upon the value assigned to the variable 'SectionScore'.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
<qti_result_report>
<result>
<context>
<name>Clark Kent</name>
<generic_identifier>
<type_label>Student Number</type_label>
<identifier_string>TestCo:156805D</identifier_string>
</generic_identifier>
<date>
<type_label>Exam</type_label>
<datetime>2001-08-07T14:00:00</datetime>
</date>
</context>
<section_result asi_title = "Example Section Title"
|
15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 |
ident_ref = "IMS_V01_S_BasicSection001">
<date>
<type_label>Section Creation Time</type_label>
<datetime>2001-08-07T13:40:00</datetime>
</date>
<control hint_switch = "No" solution_switch = "No" feedback_switch = "Yes"/>
<outcomes>
<score varname = "SectionScore" vartype = "Integer">
<score_value>1</score_value>
<score_min>0</score_min>
<score_max>2</score_max>
<score_cut>1</score_cut>
</score>
</outcomes>
<feedback_displayed ident_ref = "Passed">Response</feedback_displayed>
<num_items>2</num_items>
<num_items_presented>2</num_items_presented>
<num_items_attempted>2</num_items_attempted>
<num_sections_presented>1</num_sections_presented>
<item_result asi_title = "Standard Multiple Choice Item"
ident_ref = "IMS_V01_I_BasicExample002b">
<date>
<type_label>Item Creation Time</type_label>
<datetime>2001-08-07T13:31:00</datetime>
</date>
<duration>P0Y0M0DT0H2M</duration>
<response ident_ref = "MCb_01">
<response_form cardinality = "single" render_type = "choice"
timing = "No" response_type = "lid">
<correct_response>B</correct_response>
</response_form>
<num_attempts>1</num_attempts>
<response_value>B</response_value>
</response>
<outcomes>
<score varname = "SCORE" vartype = "Integer">
<score_value>1</score_value>
<score_min>0</score_min>
<score_max>1</score_max>
<score_cut>1</score_cut>
</score>
</outcomes>
<feedback_displayed ident_ref = "Correct">Response</feedback_displayed>
</item_result>
<item_result asi_title = "Standard MC with Images Item"
ident_ref = "IMS_V01_I_BasicExample003">
<date>
<type_label>Item Creation Time</type_label>
<datetime>2001-08-07T13:35:00</datetime>
</date>
<duration>P0Y0M0DT0H2M</duration>
<response ident_ref = "MC_02">
<response_form cardinality = "single" render_type = "choice"
timing = "No" response_type = "lid">
<correct_response>C</correct_response>
</response_form>
<num_attempts>1</num_attempts>
<response_value response_time="67" response_status="Valid">A
</response_value>
</response>
|
75 76 77 78 79 80 81 82 83 84 85 86 87 |
<outcomes>
<score varname = "SCORE" vartype = "Integer">
<score_value>0</score_value>
<score_min>0</score_min>
<score_max>1</score_max>
<score_cut>1</score_cut>
</score>
</outcomes>
<feedback_displayed ident_ref="InCorrect">Response</feedback_displayed>
</item_result>
</section_result>
</result>
</qti_result_report>
|
The example is for a result report of a single Assessment only. The score is based upon the value assigned to the grade variable 'Mastery'.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 |
<qti_result_report>
<result>
<context>
<name>Clark Kent</name>
<generic_identifier>
<type_label>Student Number</type_label>
<identifier_string>TestCo:156805D</identifier_string>
</generic_identifier>
<date>
<type_label>Exam</type_label>
<datetime>2001-08-07T14:00:00</datetime>
</date>
</context>
<assessment_result ident_ref = "IMS_V01-A_BasicExample001"
asi_title = "Full Assessment">
<date>
<type_label>Creation</type_label>
<datetime>2001-08-07T13:45:00</datetime>
</date>
<control hint_switch = "No" solution_switch = "No" feedback_switch = "Yes"/>
<outcomes>
<grade varname = "Mastery" members = "Pass, Fail">
<grade_value>Pass</grade_value>
</grade>
</outcomes>
<feedback_displayed ident_ref= "AssessmentPassed">Response
</feedback_displayed>
<num_items>2</num_items>
<num_items_presented>2</num_items_presented>
<num_items_attempted>2</num_items_attempted>
<num_sections_presented>1</num_sections_presented>
</assessment_result>
</result>
</qti_result_report>
|
The example is for a result report of a single Assessment containing a Section. The score is based upon the value assigned to the grade variable 'Mastery'.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 |
<qti_result_report>
<result>
<context>
<name>Clark Kent</name>
<generic_identifier>
<type_label>Student Number</type_label>
<identifier_string>TestCo:156805D</identifier_string>
</generic_identifier>
<date>
<type_label>Exam</type_label>
<datetime>2001-08-07T14:00:00</datetime>
</date>
</context>
<assessment_result ident_ref="IMS_V01-A_BasicExample001"
asi_title="Full Assessment">
<date>
<type_label>Creation</type_label>
<datetime>2001-08-07T13:45:00</datetime>
</date>
<control hint_switch = "No" solution_switch = "No" feedback_switch = "Yes"/>
<outcomes>
<grade varname = "Mastery" members = "Pass, Fail">
<grade_value>Pass</grade_value>
</grade>
</outcomes>
<feedback_displayed ident_ref = "AssessmentPassed">Response
</feedback_displayed>
<num_items>2</num_items>
<num_items_presented>2</num_items_presented>
<num_items_attempted>2</num_items_attempted>
<num_sections_presented>1</num_sections_presented>
<section_result asi_title = "Example Section Title"
ident_ref = "IMS_V01_S_BasicSection001">
<date>
<type_label>Section Creation Time</type_label>
<datetime>2001-08-07T13:40:00</datetime>
</date>
<control hint_switch="No" solution_switch="No" feedback_switch="Yes"/>
<outcomes>
<score varname = "SectionScore" vartype = "Integer">
<score_value>1</score_value>
<score_min>0</score_min>
<score_max>2</score_max>
<score_cut>1</score_cut>
</score>
</outcomes>
<feedback_displayed ident_ref = "Passed">Response</feedback_displayed>
<num_items>2</num_items>
<num_items_presented>2</num_items_presented>
<num_items_attempted>2</num_items_attempted>
<num_sections_presented>1</num_sections_presented>
</section_result>
</assessment_result>
</result>
</qti_result_report>
|
The example is for a result report of a single Assessment containing a Section which itself contains two Items. The score is based upon the value assigned to the grade variable 'Mastery'.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 |
<qti_result_report>
<result>
<context>
<name>Clark Kent</name>
<generic_identifier>
<type_label>Student Number</type_label>
<identifier_string>TestCo:156805D</identifier_string>
</generic_identifier>
<date>
<type_label>Exam</type_label>
<datetime>2001-08-07T14:00:00</datetime>
</date>
</context>
<assessment_result ident_ref = "IMS_V01-A_BasicExample001"
asi_title = "Full Assessment">
<date>
<type_label>Creation</type_label>
<datetime>2001-08-07T13:45:00</datetime>
</date>
<control hint_switch = "No" solution_switch = "No" feedback_switch = "Yes"/>
<outcomes>
<grade varname = "Mastery" members = "Pass, Fail">
<grade_value>Pass</grade_value>
</grade>
</outcomes>
<feedback_displayed ident_ref = "AssessmentPassed">Response
</feedback_displayed>
<num_items>2</num_items>
<num_items_presented>2</num_items_presented>
<num_items_attempted>2</num_items_attempted>
<num_sections_presented>1</num_sections_presented>
<section_result asi_title = "Example Section Title"
ident_ref = "IMS_V01_S_BasicSection001">
<date>
<type_label>Section Creation Time</type_label>
<datetime>2001-08-07T13:40:00</datetime>
</date>
<control hint_switch="No" solution_switch="No" feedback_switch="Yes"/>
<outcomes>
<score varname = "SectionScore" vartype = "Integer">
<score_value>1</score_value>
<score_min>0</score_min>
<score_max>2</score_max>
<score_cut>1</score_cut>
</score>
</outcomes>
<feedback_displayed ident_ref = "Passed">Response</feedback_displayed>
<num_items>2</num_items>
<num_items_presented>2</num_items_presented>
<num_items_attempted>2</num_items_attempted>
<num_sections_presented>1</num_sections_presented>
<item_result asi_title = "Standard Multiple Choice Item"
ident_ref = "IMS_V01_I_BasicExample002b">
<date>
|
56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 |
<type_label>Item Creation Time</type_label>
<datetime>2001-08-07T13:31:00</datetime>
</date>
<duration>P0Y0M0DT0H2M</duration>
<response ident_ref = "MCb_01">
<response_form cardinality = "single" render_type = "choice"
timing = "No" response_type = "lid">
<correct_response>B</correct_response>
</response_form>
<num_attempts>1</num_attempts>
<response_value>B</response_value>
</response>
<outcomes>
<score varname = "SCORE" vartype = "Integer">
<score_value>1</score_value>
<score_min>0</score_min>
<score_max>1</score_max>
<score_cut>1</score_cut>
</score>
</outcomes>
<feedback_displayed ident_ref = "Correct">Response
</feedback_displayed>
</item_result>
<item_result asi_title = "Standard MC with Images Item"
ident_ref = "IMS_V01_I_BasicExample003">
<date>
<type_label>Item Creation Time</type_label>
<datetime>2001-08-07T13:35:00</datetime>
</date>
<duration>P0Y0M0DT0H2M</duration>
<response ident_ref = "MC_02">
<response_form cardinality = "single" render_type = "choice"
timing = "No" response_type = "lid">
<correct_response>C</correct_response>
</response_form>
<num_attempts>1</num_attempts>
<response_value response_time="67" response_status = "Valid">A
</response_value>
</response>
<outcomes>
<score varname = "SCORE" vartype = "Integer">
<score_value>0</score_value>
<score_min>0</score_min>
<score_max>1</score_max>
<score_cut>1</score_cut>
</score>
</outcomes>
<feedback_displayed ident_ref="InCorrect">Response
</feedback_displayed>
</item_result>
</section_result>
</assessment_result>
</result>
</qti_result_report>
|
| Title |
IMS Question & Test Interoperability Results Reporting XML Binding |
| Editors |
Colin Smythe, Lane Brewer, and Steve Lay |
| Version |
1.2 |
| Version Date |
11 February 2002 |
| Status |
Final Specification |
| Summary |
This document presents the IMS QTI Results Reporting XML Binding. This specification describes the representation of the information model in XML. |
| Revision Information |
22 January 2002 |
| Purpose |
Defines the ways in which the QTI Results Reporting should be implemented using XML. |
| Document Location |
http://www.imsglobal.org/question/v1p2/imsqti_res_bindv1p2.html |
The following individuals contributed to the development of this document:
A
ASI 1, 2
Assessment 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
Item 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18
Section 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19
Assessment 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
Assessment_result Elements
assessment_result 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
extension_ assessment_result 1, 2
Attributes
asi_title 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14
cardinality 1, 2, 3, 4
entityref 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
feedback_switch 1, 2, 3, 4, 5, 6, 7, 8
hint_switch 1, 2, 3, 4, 5, 6, 7, 8
ident_ref 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14
members 1, 2, 3, 4, 5, 6
presented 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16
render_type 1, 2, 3, 4
response_status 1, 2, 3
response_time 1, 2, 3
response_type 1, 2, 3, 4
solution_switch 1, 2, 3, 4, 5, 6, 7, 8
source 1, 2, 3, 4, 5, 6, 7
status 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
timing 1, 2, 3, 4
uri 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
varname 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
vartype 1, 2, 3, 4, 5, 6, 7, 8, 9
view 1, 2, 3
xmllang 1, 2
xmlspace 1
C
Common Elements
asi_metadata 1, 2, 3, 4, 5, 6, 7, 8
control 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
date 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21
duration 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
feedback_displayed 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
grade 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
grade_cut 1, 2
grade_value 1, 2, 3, 4, 5
num_items 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
num_items_attempted 1, 2, 3, 4, 5, 6, 7, 8, 9
num_items_presented 1, 2, 3, 4, 5, 6, 7, 8, 9
num_sections 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
num_sections_presented 1, 2, 3, 4, 5, 6, 7, 8, 9
outcomes 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17
qti_comment 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
score 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16
score_average 1, 2
score_cut 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
score_interpretation 1, 2
score_max 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
score_min 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
score_normalized 1, 2
score_reliability 1, 2
score_value 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
status 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
Context Elements
context 1, 2, 3, 4, 5, 6, 7, 8, 9
date 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21
extension_context 1
generic_identifier 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
name 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
E
Elements
asi_description 1, 2, 3, 4, 5
asi_metadata 1, 2, 3, 4, 5, 6, 7, 8
asi_metadatafield 1, 2, 3
assessment_result 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
context 1, 2, 3, 4, 5, 6, 7, 8, 9
control 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
correct_response 1, 2, 3, 4
date 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21
datetime 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
duration 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
extension_assessment_result 1, 2
extension_context 1
extension_grade 1
extension_item_result 1, 2
extension_response 1, 2
extension_responseform 1
extension_result 1, 2
extension_score 1, 2
extension_section_result 1, 2
extension_summary_result 1, 2
feedback_display 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
field_name 1
field_value 1, 2
generic_identifier 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
grade 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
grade_cut 1, 2
grade_value 1, 2, 3, 4, 5
identifier_string 1, 2, 3, 4, 5, 6, 7
item_result 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16
name 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
num_attempts 1, 2, 3, 4, 5
num_items 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
num_items_attempted 1, 2, 3, 4, 5, 6, 7, 8, 9
num_items_presented 1, 2, 3, 4, 5, 6, 7, 8, 9
num_sections_presented 1, 2, 3, 4, 5, 6, 7, 8, 9
objective 1, 2, 3, 4, 5, 6, 7
outcomes 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17
qti_comment 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
qti_result_report 1, 2, 3, 4, 5, 6, 7
response 1, 2, 3, 4, 5, 6, 7, 8
response_form 1, 2, 3, 4, 5, 6
response_value 1, 2, 3, 4, 5
result 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18
score 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16
score_average 1, 2
score_cut 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
score_interpretation 1, 2
score_max 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
score_min 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
score_normalized 1, 2
score_reliability 1, 2
score_std_error 1, 2
score_value 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
section_result 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16
status 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
status_value 1, 2
summary_result 1, 2, 3, 4, 5, 6
type_label 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
vocabulary 1, 2, 3, 4, 5, 6, 7, 8, 9
Extension Elements
extension 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20
extension_assessment_result 1, 2
extension_context 1
extension_grade 1
extension_item_result 1, 2
extension_response 1, 2
extension_responseform 1
extension_result 1, 2
extension_score 1, 2
extension_section_result 1, 2
extension_summary_result 1, 2
I
Item 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18
Item_result Elements
asi_metadata 1, 2, 3, 4, 5, 6, 7, 8
control 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
correct_response 1, 2, 3, 4
date 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21
duration 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
extension_response 1, 2
item_result 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16
num_attempts 1, 2, 3, 4, 5
objective 1, 2, 3, 4, 5, 6, 7
outcomes 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17
qti_comment 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
response 1, 2, 3, 4, 5, 6, 7, 8
response_form 1, 2, 3, 4, 5, 6
response_value 1, 2, 3, 4, 5
M
Meta-data 1, 2, 3, 4, 5, 6, 7
S
Section 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19
Section_result Elements
extension_section_result 1, 2
Summary_result Elements
summary_result 1, 2, 3, 4, 5, 6
X
XML 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23
Schema
IMS Global Learning Consortium, Inc. ("IMS") is publishing the information contained in this IMS Question & Test Interoperability: Results Reporting XML Binding ("Specification") for purposes of scientific, experimental, and scholarly collaboration only.
IMS makes no warranty or representation regarding the accuracy or completeness of the Specification.
This material is provided on an "As Is" and "As Available" basis.
The Specification is at all times subject to change and revision without notice.
It is your sole responsibility to evaluate the usefulness, accuracy, and completeness of the Specification as it relates to you.
IMS would appreciate receiving your comments and suggestions.
Please contact IMS through our website at http://www.imsglobal.org
Please refer to Document Name: IMS Question & Test Interoperability: Results Reporting XML Binding Date: 11 February 2002