XSD Data File Information ========================= Author: Colin Smythe (IMS Global, UK) and Mark McKell (IMS Global, USA) Date: 1st September, 2015 Version: 2.2 Status: Final Release Description: This is the Platform Specific Model of the Assessment Result object in the IMS QTIv2.2 Specification Information Model. It is this representation that is used to produce the XSD binding for the AssessmentResult IMS QTI v2.2. History: This version supercedes the full IMS QTI v2.1 specification. License: IPR and Distribution Notices This machine readable file is derived from IMS Global specification IMS Question and Test Interoperability (QTI) Version 2.2 found at http://www.imsglobal.org/question and the original IMS Global schema binding or code base http://www.imsglobal.org/question. 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 procedures with respect to rights in IMS specifications can be found at the IMS Global Intellectual Property Rights web page: http://www.imsglobal.org/ipr/imsipr_policyFinal.pdf. Copyright (c) IMS Global Learning Consortium 1999-2015. All Rights Reserved. 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. Permission is granted to all parties to use excerpts from this document as needed in producing requests for proposals. 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 IMPLEMENTERS 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. Source UML File Information =========================== The source file information must be supplied as an XMI file (without diagram layout information). The supported UML authoring tools are: (a) Poseidon - v6 (and later) (b) Papyrus - v0.10.2 (and later) Source XSLT File Information ============================ XSL Generator: Specificationv1p0_GenerationToolv1.xsl XSLT Processor: Saxon-PE-9.5.0.2 Release: 1.0 Date: 31st July, 2014 Autogen Engineer: Colin Smythe (IMS Global, UK) Autogen Date: 2015-12-14 IMS Global Auto-generation Binding Tool-kit (I-BAT) =================================================== This file was auto-generated using the IMS Global Binding Auto-generation Tool-kit (I-BAT). While every attempt has been made to ensure that this tool auto-generates the files correctly, users should be aware that this is an experimental tool. Permission is given to make use of this tool. IMS Global makes no claim on the materials created by third party users of this tool. Details on how to use this tool are contained in the IMS Global "I-BAT" documentation available at the IMS Global web-site: http://www.imsglobal.org. Tool Copyright: 2012-2015 (c) IMS Global Learning Consortium Inc. All Rights Reserved. This is the root class to contain the assessment result data. An Assessment Result is used to report the results of a candidate's interaction with a test and/or one or more items a- ttempted. Information about the test is optional, in some systems it may be possible to i- nteract with items that are not organized into a test at all. For example, items that are organized with learning resources and presented individually in a formative context. The response given by the candidate. This is the context for the 'assessmentResult'. It provides the corresponding set of iden- tifiers. The correct response may be output as part of the report if desired. Systems are not limi- ted to reporting correct responses declared in responseDeclarations. For example, a corre- ct response may be set by a templateRule or may simply have been suppressed from the decl- aration passed to the delivery engine e.g. for security. The result of an item session is reported with an itemResult. A report may contain multip- le results for the same instance of an item representing multiple attempts, progression t- hrough an adaptive item or even more detailed tracking. In these cases, each item result must have a different datestamp. The session status is used to keep track of the status of the item variables in an item s- ession. The Item result information related to an 'Outcome Variable'. An expression or itemVariable can either be single-valued or multi-valued. A multi-valued expression (or variable) is called a container. A container contains a list of values, th- is list may be empty in which case it is treated as NULL. All the values in a multiple or ordered container are drawn from the same value set, however, containers may contain mult- iple occurrences of the same value. In other words, [A,B,B,C] is an acceptable value for a container. A container with cardinality multiple and value [A,B,C] is equivalent to a sim- ilar one with value [C,B,A] whereas these two values would be considered distinct for con- tainers with cardinality ordered. When used as the value of a response variable this dist- inction is typified by the difference between selecting choices in a multi-response multi- -choice task and ranking choices in an order objects task. In the language of [ISO 11404] a container with multiple cardinality is a "bag-type", a container with ordered cardinali- ty is a "sequence-type" and a container with record cardinality is a "record-type". The r- ecord container type is a special container that contains a set of independent values each identified by its own identifier and having its own base-type. This specification does not make use of the record type directly however it is provided to enable customInteractions to manipulate more complex responses and customOperators to return more complex values, in addition to the use for detailed information about numeric responses described in the str- ingInteraction abstract class. A base-type is simply a description of a set of atomic values (atomic to this specificati- on). Note that several of the baseTypes used to define the runtime data model have identi- cal definitions to those of the basic data types used to define the values for attributes in the specification itself. The use of an enumeration to define the set of baseTypes used in the runtime model, as opposed to the use of classes with similar names, is designed to help distinguish between these two distinct levels of modelling. The Item result information related to a 'Response Variable'. An expression or itemVariable can either be single-valued or multi-valued. A multi-valued expression (or variable) is called a container. A container contains a list of values, th- is list may be empty in which case it is treated as NULL. All the values in a multiple or ordered container are drawn from the same value set, however, containers may contain mult- iple occurrences of the same value. In other words, [A,B,B,C] is an acceptable value for a container. A container with cardinality multiple and value [A,B,C] is equivalent to a sim- ilar one with value [C,B,A] whereas these two values would be considered distinct for con- tainers with cardinality ordered. When used as the value of a response variable this dist- inction is typified by the difference between selecting choices in a multi-response multi- -choice task and ranking choices in an order objects task. In the language of [ISO 11404] a container with multiple cardinality is a "bag-type", a container with ordered cardinali- ty is a "sequence-type" and a container with record cardinality is a "record-type". The r- ecord container type is a special container that contains a set of independent values each identified by its own identifier and having its own base-type. This specification does not make use of the record type directly however it is provided to enable customInteractions to manipulate more complex responses and customOperators to return more complex values, in addition to the use for detailed information about numeric responses described in the str- ingInteraction abstract class. A base-type is simply a description of a set of atomic values (atomic to this specificati- on). Note that several of the baseTypes used to define the runtime data model have identi- cal definitions to those of the basic data types used to define the values for attributes in the specification itself. The use of an enumeration to define the set of baseTypes used in the runtime model, as opposed to the use of classes with similar names, is designed to help distinguish between these two distinct levels of modelling. The Item result information related to a 'Template Variable'. An expression or itemVariable can either be single-valued or multi-valued. A multi-valued expression (or variable) is called a container. A container contains a list of values, th- is list may be empty in which case it is treated as NULL. All the values in a multiple or ordered container are drawn from the same value set, however, containers may contain mult- iple occurrences of the same value. In other words, [A,B,B,C] is an acceptable value for a container. A container with cardinality multiple and value [A,B,C] is equivalent to a sim- ilar one with value [C,B,A] whereas these two values would be considered distinct for con- tainers with cardinality ordered. When used as the value of a response variable this dist- inction is typified by the difference between selecting choices in a multi-response multi- -choice task and ranking choices in an order objects task. In the language of [ISO 11404] a container with multiple cardinality is a "bag-type", a container with ordered cardinali- ty is a "sequence-type" and a container with record cardinality is a "record-type". The r- ecord container type is a special container that contains a set of independent values each identified by its own identifier and having its own base-type. This specification does not make use of the record type directly however it is provided to enable customInteractions to manipulate more complex responses and customOperators to return more complex values, in addition to the use for detailed information about numeric responses described in the str- ingInteraction abstract class. A base-type is simply a description of a set of atomic values (atomic to this specificati- on). Note that several of the baseTypes used to define the runtime data model have identi- cal definitions to those of the basic data types used to define the values for attributes in the specification itself. The use of an enumeration to define the set of baseTypes used in the runtime model, as opposed to the use of classes with similar names, is designed to help distinguish between these two distinct levels of modelling. The container for the Test result. When a test result is given the following item results must relate only to items that were selected for presentation as part of the corresponding test session. Furthermore, all items selected for presentation should be reported with a corresponding itemResult. The system that creates the result (for example, the test delivery system) should assign a session identifier that it can use to identify the session. A class that can represent a single value of any baseType in variable declarations and re- sult reports. The base-type is defined by the baseType attribute of the declaration except in the case of variables with record cardinality. A base-type is simply a description of a set of atomic values (atomic to this specificati- on). Note that several of the baseTypes used to define the runtime data model have identi- cal definitions to those of the basic data types used to define the values for attributes in the specification itself. The use of an enumeration to define the set of baseTypes used in the runtime model, as opposed to the use of classes with similar names, is designed to help distinguish between these two distinct levels of modelling.