XSD Data File Information ========================= Author: Colin Smythe (IMS Global) Date: 31st July, 2013 Version: 2.1.1 Status: Final Release Description: This is the Platform Specific Model of the IMS QTI v2.1 Specification Information Model. It is this representation that is used to produce the XSD binding for IMS QTI v2.1. History: Version 2.1.0: Supercedes the full IMS QTI v1.2 and QTIv2.0 specifications; Version 2.1.1: The changes in this release are:- (a) ChoiceInteraction, GraphicOrderInteraction, HotspotInteraction, PositionObjectInteraction, SelectPointInteraction, OrderInteraction, HotTextInteraction - minChoices and maxChoices attributes datatype made 'nonNegativeInteger' (b) AssociableHotspot, GapText, GapImg, SimpleAssociableInteraction - matchMin and matchMax attributes datatype made 'nonNegativeInteger' (c) GraphicAssociateInteraction, MatchInteraction, AssociateInteractions - minAssociations and maxAssociations attributes datatype made 'nonNegativeInteger' (d) MediaInteraction - minPlays and maxPlays attributes datatype made 'nonNegativeInteger' (e) SliderInteraction - lowerBound, upperBound and step attributes datatype made 'NonNegativeDouble' (f) ExtendedTextInteraction - minStrings, maxStrings, expectedLength and expectedLines attributes datatype made 'nonNegativeInteger' (g) TimeLimits - minTime and maxTime attributes datatype made 'NonNegativeDouble' License: IPR and Distribution Notices This machine readable file is derived from IMS Global specification IMS Question and Test Interoperability (QTI) Version 2.1 found at http://www.imsglobal.org/qti and the original IMS Global schema binding or code base http://www.imsglobal.org/qti. 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 © IMS Global Learning Consortium 1999-2013. 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.9.2 (and later) Source XSLT File Information ============================ XSL Generator: Specificationv1p0_GenerationToolv1.xsl XSLT Processor: Saxon-HE-9.4.0.4 Release: 1.0 Date: 31st March, 2013 Autogen Engineer: Colin Smythe (IMS Global, UK) Autogen Date: 2013-07-22 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-2013 (c) IMS Global Learning Consortium Inc. All Rights Reserved. Definition of Schematron Validation Rules ========================================= Author: Colin Smythe (IMS Global) Date: 31st July, 2013 Version: 1.0 Status: Final Release Description: This is the set of Schematron Rules to further enforce the QTIv2.1 Information Model. The rule sets that have been defined are: [RULE SET GENERAL 1] Ensure that certain expressions are NOT used for Response Processing. [RULE SET GENERAL 2] Ensure that the Item, Section, Test and TestPart identifiers are unique. [RULE SET GENERAL 3] Ensure that AssessmentItem Response Declarations are correct. [RULE SET INTERACTION 1] Enforce the correct use the TextEntryInteraction attributes. [RULE SET INTERACTION 2] Enforce the correct use the ChoiceInteraction attributes. [RULE SET INTERACTION 3] Enforce the correct use the ExtendedTextInteraction attributes. [RULE SET INTERACTION 4] Enforce the correct use the HotspotInteraction attributes. [RULE SET INTERACTION 5] Enforce the correct use the GraphicOrderInteraction attributes. [RULE SET INTERACTION 6] Enforce the correct use the PositionObjectInteraction attributes. [RULE SET INTERACTION 7] Enforce the correct use the SelectPointInteraction attributes. [RULE SET INTERACTION 8] Enforce the correct use the OrderInteraction attributes. [RULE SET INTERACTION 9] Enforce the correct use the HotTextInteraction attributes. RULE SET GENERAL 1: Ensure that certain expressions are NOT used for Response Processing. The set of rules are:- * RULE GENERAL 1a-Assertion 1 :- The expression numberCorrect must NOT be used in Response Processing. * RULE GENERAL 1a-Assertion 2 :- The expression numberIncorrect must NOT be used in Response Processing. * RULE GENERAL 1a-Assertion 3 :- The expression numberPresented must NOT be used in Response Processing. * RULE GENERAL 1a-Assertion 4 :- The expression numberResponded must NOT be used in Response Processing. * RULE GENERAL 1a-Assertion 5 :- The expression numberSelected must NOT be used in Response Processing. * RULE GENERAL 1a-Assertion 6 :- The expression outcomeMinimum must NOT be used in Response Processing. * RULE GENERAL 1a-Assertion 7 :- The expression outcomeMaximum must NOT be used in Response Processing. * RULE GENERAL 1a-Assertion 8 :- The expression testVariables must NOT be used in Response Processing. RULE SET GENERAL 2: Ensure that the Item, Section, Test and TestPart identifiers are unique. The set of rules are:- * RULE GENERAL 2a-Assertion 1 :- The AssessmentTest and a TestPart must not have the same unique identifier. * RULE GENERAL 2a-Assertion 2 :- The AssessmentTest and an AssessmentSection must not have the same unique identifier. * RULE GENERAL 2a-Assertion 3 :- The AssessmentTest and a direct child AssessmentSectionRef must not have the same unique identifier. * RULE GENERAL 2a-Assertion 4 :- The AssessmentTest and a descendant AssessmentSectionRef must not have the same unique identifier. * RULE GENERAL 2a-Assertion 5 :- The AssessmentTest and a descendant AssessmentItemRef must not have the same unique identifier. * RULE GENERAL 2b-Assertion 1 :- Two TestParts must not have the same unique identifier. * RULE GENERAL 2b-Assertion 2 :- The TestPart and an AssessmentSection must not have the same unique identifier. * RULE GENERAL 2b-Assertion 3 :- The TestPart and a direct child AssessmentSectionRef must not have the same unique identifier. * RULE GENERAL 2b-Assertion 4 :- The TestPart and a descendant AssessmentSectionRef must not have the same unique identifier. * RULE GENERAL 2b-Assertion 5 :- The TestPart and a descendant AssessmentItemRef must not have the same unique identifier. * RULE GENERAL 2c-Assertion 1 :- Two AssessmentSection children of a TestPart must not have the same unique identifier. * RULE GENERAL 2c-Assertion 2 :- The AssessmentSection and a descendant AssessmentSection must not have the same unique identifier. * RULE GENERAL 2c-Assertion 3 :- The AssessmentSection and a descendant AssessmentSectionRef must not have the same unique identifier. * RULE GENERAL 2c-Assertion 4 :- The AssessmentSection and a descendant AssessmentItemRef must not have the same unique identifier. RULE SET GENERAL 3: Ensure that AssessmentItem Response Declarations are correct. The set of rules are:- * RULE GENERAL 3a-Assertion 1 :- ***To be completed***.. RULE SET INTERACTION 1: Enforce the correct use the TextEntryInteraction attributes. The set of rules are:- * RULE INTERACTION 1a-Assertion 1 :- The StringIdentifier and ResponseIdentifier attribute values must not be the same. * RULE INTERACTION 1b-Assertion 1 :- The baseType must have a value of either string or float or integer. RULE SET INTERACTION 2: Enforce the correct use the ChoiceInteraction attributes. The set of rules are:- * RULE INTERACTION 2a-Assertion 1 :- The MaxChoices attribute value must not be less than the MinChoices value. RULE SET INTERACTION 3: Enforce the correct use the ExtendedTextInteraction attributes. The set of rules are:- * RULE INTERACTION 3a-Assertion 1 :- The StringIdentifier and ResponseIdentifier attribute values must not be the same. RULE SET INTERACTION 4: Enforce the correct use the HotspotInteraction attributes. The set of rules are:- * RULE INTERACTION 4a-Assertion 1 :- The MaxChoices attribute value must not be less than the MinChoices value. RULE SET INTERACTION 5: Enforce the correct use the GraphicOrderInteraction attributes. The set of rules are:- * RULE INTERACTION 5a-Assertion 1 :- The MaxChoices attribute value must not be less than the MinChoices value. RULE SET INTERACTION 6: Enforce the correct use the PositionObjectInteraction attributes. The set of rules are:- * RULE INTERACTION 6a-Assertion 1 :- The MaxChoices attribute value must not be less than the MinChoices value. RULE SET INTERACTION 7: Enforce the correct use the SelectPointInteraction attributes. The set of rules are:- * RULE INTERACTION 7a-Assertion 1 :- The MaxChoices attribute value must not be less than the MinChoices value. RULE SET INTERACTION 8: Enforce the correct use the OrderInteraction attributes. The set of rules are:- * RULE INTERACTION 8a-Assertion 1 :- The MaxChoices attribute value must not be less than the MinChoices value. RULE SET INTERACTION 9: Enforce the correct use the HotTextInteraction attributes. The set of rules are:- * RULE INTERACTION 9a-Assertion 1 :- The MaxChoices attribute value must not be less than the MinChoices value. History: Version 1.0: The first set of schematron rules for the IMS Global QTIv2.1 specification. Schematron Validation Rules for QTI Specification v2.1. Ensure that certain expressions are NOT used for Response Processing. [RULE GENERAL 1a: Assertion 1] The expression numberCorrect must NOT be used in Response Processing. [RULE GENERAL 1a: Assertion 2] The expression numberIncorrect must NOT be used in Response Processing. [RULE GENERAL 1a: Assertion 3] The expression numberPresented must NOT be used in Response Processing. [RULE GENERAL 1a: Assertion 4] The expression numberResponded must NOT be used in Response Processing. [RULE GENERAL 1a: Assertion 5] The expression numberSelected must NOT be used in Response Processing. [RULE GENERAL 1a: Assertion 6] The expression outcomeMinimum must NOT be used in Response Processing. [RULE GENERAL 1a: Assertion 7] The expression outcomeMaximum must NOT be used in Response Processing. [RULE GENERAL 1a: Assertion 8] The expression testVariables must NOT be used in Response Processing. Ensure that the Item, Section, Test and TestPart identifiers are unique. [RULE GENERAL 2a: Assertion 1] The AssessmentTest and a TestPart must not have the same unique identifier. [RULE GENERAL 2a: Assertion 2] The AssessmentTest and an AssessmentSection must not have the same unique identifier. [RULE GENERAL 2a: Assertion 3] The AssessmentTest and a direct child AssessmentSectionRef must not have the same unique identifier. [RULE GENERAL 2a: Assertion 4] The AssessmentTest and a descendant AssessmentSectionRef must not have the same unique identifier. [RULE GENERAL 2a: Assertion 5] The AssessmentTest and a descendant AssessmentItemRef must not have the same unique identifier. [RULE GENERAL 2b: Assertion 1] Two TestParts must not have the same unique identifier. [RULE GENERAL 2b: Assertion 2] The TestPart and an AssessmentSection must not have the same unique identifier. [RULE GENERAL 2b: Assertion 3] The TestPart and a direct child AssessmentSectionRef must not have the same unique identifier. [RULE GENERAL 2b: Assertion 4] The TestPart and a descendant AssessmentSectionRef must not have the same unique identifier. [RULE GENERAL 2b: Assertion 5] The TestPart and a descendant AssessmentItemRef must not have the same unique identifier. [RULE GENERAL 2c: Assertion 1] Two AssessmentSection children of a TestPart must not have the same unique identifier. [RULE GENERAL 2c: Assertion 2] The AssessmentSection and a descendant AssessmentSection must not have the same unique identifier. [RULE GENERAL 2c: Assertion 3] The AssessmentSection and a descendant AssessmentSectionRef must not have the same unique identifier. [RULE GENERAL 2c: Assertion 4] The AssessmentSection and a descendant AssessmentItemRef must not have the same unique identifier. Enforce the correct use the TextEntryInteraction attributes. [RULE INTERACTION 1a: Assertion 1] The StringIdentifier and ResponseIdentifier attribute values must not be the same. [RULE INTERACTION 1b: Assertion 1] The baseType must have a value of either string or float or integer. Enforce the correct use the ChoiceInteraction attributes. [RULE INTERACTION 2a: Assertion 1] The MaxChoices attribute value must not be less than the MinChoices value. Enforce the correct use the ExtendedTextInteraction attributes. [RULE INTERACTION 3a: Assertion 1] The StringIdentifier and ResponseIdentifier attribute values must not be the same. Enforce the correct use the HotspotInteraction attributes. [RULE INTERACTION 4a: Assertion 1] The MaxChoices attribute value must not be less than the MinChoices value. Enforce the correct use the GraphicOrderInteraction attributes. [RULE INTERACTION 5a: Assertion 1] The MaxChoices attribute value must not be less than the MinChoices value. Enforce the correct use the PositionObjectInteraction attributes. [RULE INTERACTION 6a: Assertion 1] The MaxChoices attribute value must not be less than the MinChoices value. Enforce the correct use the SelectPointInteraction attributes. [RULE INTERACTION 7a: Assertion 1] The MaxChoices attribute value must not be less than the MinChoices value. Enforce the correct use the OrderInteraction attributes. [RULE INTERACTION 8a: Assertion 1] The MaxChoices attribute value must not be less than the MinChoices value. Enforce the correct use the HotTextInteraction attributes. [RULE INTERACTION 9a: Assertion 1] The MaxChoices attribute value must not be less than the MinChoices value. Any namespaced element from any namespace may be included within an "any" element. The namespace for the imported element must be defined in the instance, and the schema must be imported. The extension has a definition of "lax" i.e. they can reuse elements from the target namespace.