XSD Data File Information
=========================
Author: Colin Smythe (IMS Global, UK)
Date: 31st March, 2014
Version: Final 1.0
Status: Final Release
Description: This is the Platform Specific Model of the APIPv1.0 profile of the IMS QTI v2.2 Information Model.
This is the Entry Level Profile for APIPv1.0 QTIv2.2 Sections.
History: This is the first version of the APIPv1.0 QTIv2.2 Section Profile.
PROFILE: This is the "APIP-Section (Entry)". THIS IS A PROFILE OF THE BASE SPECIFICATION.
The changes to the base specification are:
* The schema namespace has been changed to "http://www.imsglobal.org/xsd/apip/apipv1p0/qtisection/imsqti_v2p2".
* The schema version has been changed to "IMS APIP 1.0 QTI 2.2 SECTION".
* The "AnyN" class/complexType and set of XML attributes have been deleted;
* The "AreaMapEntry" class/complexType and set of XML attributes have been deleted;
* The "AreaMapping" class/complexType and set of XML attributes have been deleted;
* The "AssessmentItem" class/complexType and set of XML attributes have been deleted;
* The "AssessmentSectionSelection" class/complexType and set of XML attributes have been deleted;
* The "AssessmentStimulus" class/complexType and set of XML attributes have been deleted;
* The "AssessmentStimulusRef" class/complexType and set of XML attributes have been deleted;
* The "AssessmentTest" class/complexType and set of XML attributes have been deleted;
* The "AssociableHotspot" class/complexType and set of XML attributes have been deleted;
* The "AssociateInteraction" class/complexType and set of XML attributes have been deleted;
* The "BaseValue" class/complexType and set of XML attributes have been deleted;
* The "BranchRule" class/complexType and set of XML attributes have been deleted;
* The "ChoiceInteraction" class/complexType and set of XML attributes have been deleted;
* The "Correct" class/complexType and set of XML attributes have been deleted;
* The "CorrectResponse" class/complexType and set of XML attributes have been deleted;
* The "CustomInteraction" class/complexType and set of XML attributes have been deleted;
* The "CustomOperator" class/complexType and set of XML attributes have been deleted;
* The "Date" class/complexType and set of XML attributes have been deleted;
* The "DateTime" class/complexType and set of XML attributes have been deleted;
* The "Default" class/complexType and set of XML attributes have been deleted;
* The "DefaultValue" class/complexType and set of XML attributes have been deleted;
* The "DrawingInteraction" class/complexType and set of XML attributes have been deleted;
* The "EndAttemptInteraction" class/complexType and set of XML attributes have been deleted;
* The "Equal" class/complexType and set of XML attributes have been deleted;
* The "EqualRounded" class/complexType and set of XML attributes have been deleted;
* The "ExpressionGroup" class/complexType and set of XML attributes have been deleted;
* The "ExtendedTextInteraction" class/complexType and set of XML attributes have been deleted;
* The "FeedbackBlock" class/complexType and set of XML attributes have been deleted;
* The "FeedbackInline" class/complexType and set of XML attributes have been deleted;
* The "FieldValue" class/complexType and set of XML attributes have been deleted;
* The "Gap" class/complexType and set of XML attributes have been deleted;
* The "GapChoice" class/complexType and set of XML attributes have been deleted;
* The "GapImg" class/complexType and set of XML attributes have been deleted;
* The "GapMatchInteraction" class/complexType and set of XML attributes have been deleted;
* The "GapText" class/complexType and set of XML attributes have been deleted;
* The "GraphicAssociateInteraction" class/complexType and set of XML attributes have been deleted;
* The "GraphicGapMatchInteraction" class/complexType and set of XML attributes have been deleted;
* The "GraphicOrderInteraction" class/complexType and set of XML attributes have been deleted;
* The "HotspotChoice" class/complexType and set of XML attributes have been deleted;
* The "HotspotInteraction" class/complexType and set of XML attributes have been deleted;
* The "HotText" class/complexType and set of XML attributes have been deleted;
* The "HotTextInteraction" class/complexType and set of XML attributes have been deleted;
* The "Index" class/complexType and set of XML attributes have been deleted;
* The "InfoControl" class/complexType and set of XML attributes have been deleted;
* The "InlineChoice" class/complexType and set of XML attributes have been deleted;
* The "InlineChoiceInteraction" class/complexType and set of XML attributes have been deleted;
* The "Inside" class/complexType and set of XML attributes have been deleted;
* The "InterpolationTable" class/complexType and set of XML attributes have been deleted;
* The "InterpolationTableEntry" class/complexType and set of XML attributes have been deleted;
* The "ItemBody" class/complexType and set of XML attributes have been deleted;
* The "ItemSessionControl" class/complexType and set of XML attributes have been deleted;
* The "Label" class/complexType and set of XML attributes have been deleted;
* The "Logic0toMany" class/complexType and set of XML attributes have been deleted;
* The "Logic1toMany" class/complexType and set of XML attributes have been deleted;
* The "LogicPair" class/complexType and set of XML attributes have been deleted;
* The "LogicSingle" class/complexType and set of XML attributes have been deleted;
* The "LookupOutcomeValue" class/complexType and set of XML attributes have been deleted;
* The "MapEntry" class/complexType and set of XML attributes have been deleted;
* The "Mapping" class/complexType and set of XML attributes have been deleted;
* The "MapResponse" class/complexType and set of XML attributes have been deleted;
* The "MatchInteraction" class/complexType and set of XML attributes have been deleted;
* The "MatchTable" class/complexType and set of XML attributes have been deleted;
* The "MatchTableEntry" class/complexType and set of XML attributes have been deleted;
* The "MathConstant" class/complexType and set of XML attributes have been deleted;
* The "MathOperator" class/complexType and set of XML attributes have been deleted;
* The "MediaInteraction" class/complexType and set of XML attributes have been deleted;
* The "ModalFeedback" class/complexType and set of XML attributes have been deleted;
* The "Number" class/complexType and set of XML attributes have been deleted;
* The "NumericExpressionGroup" class/complexType and set of XML attributes have been deleted;
* The "NumericLogic1toMany" class/complexType and set of XML attributes have been deleted;
* The "ObjectFlowGroup" class/complexType and set of XML attributes have been deleted;
* The "Ordering" class/complexType and set of XML attributes have been deleted;
* The "OrderInteraction" class/complexType and set of XML attributes have been deleted;
* The "OutcomeCondition" class/complexType and set of XML attributes have been deleted;
* The "OutcomeDeclaration" class/complexType and set of XML attributes have been deleted;
* The "OutcomeElse" class/complexType and set of XML attributes have been deleted;
* The "OutcomeIf" class/complexType and set of XML attributes have been deleted;
* The "OutcomeMinMax" class/complexType and set of XML attributes have been deleted;
* The "OutcomeProcessing" class/complexType and set of XML attributes have been deleted;
* The "OutcomeProcessingFragment" class/complexType and set of XML attributes have been deleted;
* The "OutcomeRule" class/complexType and set of XML attributes have been deleted;
* The "Param" class/complexType and set of XML attributes have been deleted;
* The "PatternMatch" class/complexType and set of XML attributes have been deleted;
* The "PositionObjectInteraction" class/complexType and set of XML attributes have been deleted;
* The "PositionObjectStage" class/complexType and set of XML attributes have been deleted;
* The "PrintedVariable" class/complexType and set of XML attributes have been deleted;
* The "Prompt" class/complexType and set of XML attributes have been deleted;
* The "RandomFloat" class/complexType and set of XML attributes have been deleted;
* The "RandomInteger" class/complexType and set of XML attributes have been deleted;
* The "Repeat" class/complexType and set of XML attributes have been deleted;
* The "ResponseCondition" class/complexType and set of XML attributes have been deleted;
* The "ResponseDeclaration" class/complexType and set of XML attributes have been deleted;
* The "ResponseElse" class/complexType and set of XML attributes have been deleted;
* The "ResponseIf" class/complexType and set of XML attributes have been deleted;
* The "ResponseProcessing" class/complexType and set of XML attributes have been deleted;
* The "ResponseProcessingFragment" class/complexType and set of XML attributes have been deleted;
* The "ResponseRuleGroup" class/complexType and set of XML attributes have been deleted;
* The "RoundTo" class/complexType and set of XML attributes have been deleted;
* The "RubricBlockTemplateBlock" class/complexType and set of XML attributes have been deleted;
* The "RubricBlockTemplateInline" class/complexType and set of XML attributes have been deleted;
* The "Selection" class/complexType and set of XML attributes have been deleted;
* The "SelectPointInteraction" class/complexType and set of XML attributes have been deleted;
* The "SetValue" class/complexType and set of XML attributes have been deleted;
* The "SimpleAssociableChoice" class/complexType and set of XML attributes have been deleted;
* The "SimpleChoice" class/complexType and set of XML attributes have been deleted;
* The "SimpleMatchSet" class/complexType and set of XML attributes have been deleted;
* The "SliderInteraction" class/complexType and set of XML attributes have been deleted;
* The "StatsOperator" class/complexType and set of XML attributes have been deleted;
* The "StimulusBody" class/complexType and set of XML attributes have been deleted;
* The "StringMatch" class/complexType and set of XML attributes have been deleted;
* The "Substring" class/complexType and set of XML attributes have been deleted;
* The "TemplateBlock" class/complexType and set of XML attributes have been deleted;
* The "TemplateBlockFeedbackBlock" class/complexType and set of XML attributes have been deleted;
* The "TemplateCondition" class/complexType and set of XML attributes have been deleted;
* The "TemplateConstraint" class/complexType and set of XML attributes have been deleted;
* The "TemplateDeclaration" class/complexType and set of XML attributes have been deleted;
* The "TemplateElse" class/complexType and set of XML attributes have been deleted;
* The "TemplateIf" class/complexType and set of XML attributes have been deleted;
* The "TemplateInline" class/complexType and set of XML attributes have been deleted;
* The "TemplateProcessing" class/complexType and set of XML attributes have been deleted;
* The "TemplateRuleGroup" class/complexType and set of XML attributes have been deleted;
* The "TestFeedback" class/complexType and set of XML attributes have been deleted;
* The "TestPart" class/complexType and set of XML attributes have been deleted;
* The "TestVariables" class/complexType and set of XML attributes have been deleted;
* The "TextEntryInteraction" class/complexType and set of XML attributes have been deleted;
* The "UploadInteraction" class/complexType and set of XML attributes have been deleted;
* The "Value" class/complexType and set of XML attributes have been deleted;
* The "Variable" class/complexType and set of XML attributes have been deleted;
* The "VariableString" class/complexType and set of XML attributes have been deleted;
* The "RubricBlock.Attr" class/complexType has been modified by:-
- The "use" attribute class type has been changed to the class "UseType";
* The "SectionPart" class/complexType has been modified by:-
- The "include" attribute has been prohibited;
- The "assessmentSection" attribute has been prohibited;
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/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-PE-9.5.0.2
Release: 1.0
Date: 31st March, 2013
Autogen Engineer: Colin Smythe (IMS Global, UK)
Autogen Date: 2014-05-15
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, UK)
Date: 31st March, 2014
Version: 1.0
Status: Final Release
Description: This is the set of Schematron Rules to further enforce the QTIv2.2 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_INTERACTION-RELATED_1] Enforce the correct use the GapText attributes.
[RULE_SET_INTERACTION-RELATED_2] Enforce the correct use the GapImg attributes.
[RULE_SET_INTERACTION-RELATED_3] Enforce the correct use the AssociableHotspot attributes.
[RULE_SET_INTERACTION-RELATED_4] Enforce the correct use the SimpleAssociableChoice attributes.
[RULE_SET_INTERACTION_01] Enforce the correct use the TextEntryInteraction attributes.
[RULE_SET_INTERACTION_02] Enforce the correct use the ChoiceInteraction attributes.
[RULE_SET_INTERACTION_03] Enforce the correct use the ExtendedTextInteraction attributes.
[RULE_SET_INTERACTION_04] Enforce the correct use the HotspotInteraction attributes.
[RULE_SET_INTERACTION_05] Enforce the correct use the GraphicOrderInteraction attributes.
[RULE_SET_INTERACTION_06] Enforce the correct use the PositionObjectInteraction attributes.
[RULE_SET_INTERACTION_07] Enforce the correct use the SelectPointInteraction attributes.
[RULE_SET_INTERACTION_08] Enforce the correct use the OrderInteraction attributes.
[RULE_SET_INTERACTION_09] Enforce the correct use the HotTextInteraction attributes.
[RULE_SET_INTERACTION_10] Enforce the correct use the GraphicAssociateInteraction attributes.
[RULE_SET_INTERACTION_11] Enforce the correct use the MatchInteraction attributes.
[RULE_SET_INTERACTION_12] Enforce the correct use the AssociateInteraction attributes.
[RULE_SET_INTERACTION_13] Enforce the correct use the MediaInteraction attributes.
[RULE_SET_INTERACTION_14] Enforce the correct use the SliderInteraction attributes.
[RULE_SET_INTERACTION_15] Enforce the correct use the DrawingInteraction attributes.
[RULE_SET_INTERACTION_16] Enforce the correct use the UploadInteraction attributes.
[RULE_SET_INTERACTION_17] Enforce the correct use the EndAttemptInteraction attributes.
[RULE_SET_INTERACTION_18] Enforce the correct use the GapMatchInteraction attributes.
[RULE_SET_INTERACTION_19] Enforce the correct use the GraphicGapMatchInteraction attributes.
[RULE_SET_SPECIFIC_CLASS_1] Enforce the correct use the OutcomeDeclaration attributes.
[RULE_SET_SPECIFIC_CLASS_2] Enforce the correct use the TimeLimits 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_INTERACTION-RELATED_1: Enforce the correct use the GapText attributes. The set of rules are:-
* RULE INTERACTION-RELATED 1a-Assertion 1 :- The MatchMax attribute value must not be less than the MatchMin value.
RULE_SET_INTERACTION-RELATED_2: Enforce the correct use the GapImg attributes. The set of rules are:-
* RULE INTERACTION-RELATED 2a-Assertion 1 :- The MatchMax attribute value must not be less than the MatchMin value.
RULE_SET_INTERACTION-RELATED_3: Enforce the correct use the AssociableHotspot attributes. The set of rules are:-
* RULE INTERACTION-RELATED 3a-Assertion 1 :- The MatchMax attribute value must not be less than the MatchMin value.
RULE_SET_INTERACTION-RELATED_4: Enforce the correct use the SimpleAssociableChoice attributes. The set of rules are:-
* RULE INTERACTION-RELATED 4a-Assertion 1 :- The MatchMax attribute value must not be less than the MatchMin value.
RULE_SET_INTERACTION_01: 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_02: 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_03: 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_04: 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_05: 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_06: 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_07: 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_08: 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_09: 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.
RULE_SET_INTERACTION_10: Enforce the correct use the GraphicAssociateInteraction attributes. The set of rules are:-
* RULE INTERACTION 10a-Assertion 1 :- The MaxAssociations attribute value must not be less than the MinAssociations value.
RULE_SET_INTERACTION_11: Enforce the correct use the MatchInteraction attributes. The set of rules are:-
* RULE INTERACTION 11a-Assertion 1 :- The MaxAssociations attribute value must not be less than the MinAssociations value.
RULE_SET_INTERACTION_12: Enforce the correct use the AssociateInteraction attributes. The set of rules are:-
* RULE INTERACTION 12a-Assertion 1 :- The MaxAssociations attribute value must not be less than the MinAssociations value.
RULE_SET_INTERACTION_13: Enforce the correct use the MediaInteraction attributes. The set of rules are:-
* RULE INTERACTION 13a-Assertion 1 :- The MaxPlays attribute value must not be less than the MinPlays value.
RULE_SET_INTERACTION_14: Enforce the correct use the SliderInteraction attributes. The set of rules are:-
* RULE INTERACTION 14a-Assertion 1 :- The UpperBound attribute value must not be less than the LowerBound value.
RULE_SET_INTERACTION_15: Enforce the correct use the DrawingInteraction attributes. The set of rules are:-
* RULE INTERACTION 15a-Assertion 1 :- The baseType must have a value of file.
RULE_SET_INTERACTION_16: Enforce the correct use the UploadInteraction attributes. The set of rules are:-
* RULE INTERACTION 16a-Assertion 1 :- The baseType must have a value of file.
RULE_SET_INTERACTION_17: Enforce the correct use the EndAttemptInteraction attributes. The set of rules are:-
* RULE INTERACTION 17a-Assertion 1 :- The baseType must have a value of boolean.
RULE_SET_INTERACTION_18: Enforce the correct use the GapMatchInteraction attributes. The set of rules are:-
* RULE INTERACTION 18a-Assertion 1 :- The baseType must have a value of directedPair.
RULE_SET_INTERACTION_19: Enforce the correct use the GraphicGapMatchInteraction attributes. The set of rules are:-
* RULE INTERACTION 19a-Assertion 1 :- The baseType must have a value of directedPair.
RULE_SET_SPECIFIC_CLASS_1: Enforce the correct use the OutcomeDeclaration attributes. The set of rules are:-
* RULE SPECIFIC CLASS 1a-Assertion 1 :- The MasteryValue attribute value must not be less than the NormalMinimum value.
* RULE SPECIFIC CLASS 1a-Assertion 2 :- The MasteryValue attribute value must not be greater than the NormalMaximum value.
RULE_SET_SPECIFIC_CLASS_2: Enforce the correct use the TimeLimits attributes. The set of rules are:-
* RULE SPECIFIC CLASS 2a-Assertion 1 :- The MaxTime attribute value must not be less than the MinTime value.
History: Version 1.0: The first set of schematron rules for the IMS Global QTIv2.2 specification.
Schematron Validation Rules for QTI Specification v2.2.
Ensure that certain expressions are NOT used for Response Processing.
Ensure that the Item, Section, Test and TestPart identifiers are unique.
Enforce the correct use the GapText attributes.
Enforce the correct use the GapImg attributes.
Enforce the correct use the AssociableHotspot attributes.
Enforce the correct use the SimpleAssociableChoice attributes.
Enforce the correct use the TextEntryInteraction attributes.
Enforce the correct use the ChoiceInteraction attributes.
Enforce the correct use the ExtendedTextInteraction attributes.
Enforce the correct use the HotspotInteraction attributes.
Enforce the correct use the GraphicOrderInteraction attributes.
Enforce the correct use the PositionObjectInteraction attributes.
Enforce the correct use the SelectPointInteraction attributes.
Enforce the correct use the OrderInteraction attributes.
Enforce the correct use the HotTextInteraction attributes.
Enforce the correct use the GraphicAssociateInteraction attributes.
Enforce the correct use the MatchInteraction attributes.
Enforce the correct use the AssociateInteraction attributes.
Enforce the correct use the MediaInteraction attributes.
Enforce the correct use the SliderInteraction attributes.
Enforce the correct use the DrawingInteraction attributes.
Enforce the correct use the UploadInteraction attributes.
Enforce the correct use the EndAttemptInteraction attributes.
Enforce the correct use the GapMatchInteraction attributes.
Enforce the correct use the GraphicGapMatchInteraction attributes.
Enforce the correct use the OutcomeDeclaration attributes.
Enforce the correct use the TimeLimits attributes.
[RULE SPECIFIC CLASS 2a: Assertion 1] The MaxTime attribute value must not be less than the MinTime value.
The 'A' complexType is the container for content that is equivalent to the HTML 'a' markup.
This is the container for referential link to the externally stored AssessmentItem (each such Item is stored in its own XML instance file). The identifier attribute should be used to identify the actual Item. The details for the Item provided at this point enable the associated Test/Section to determine if the Item fulfills any prerequisites.
A Test consists of one or more Sections. An 'assessmentSection' is the binding form of a Section. More significantly, a Section is an aggregation of assessmentItems i.e. a set of Items that are used to achieve some co-ordnated assessment activity. An assessmentSection contains the rules that should be used to select and order the set of associated Sections and/or Items. Furthermore, the associated rubricBlock is used to present content that is relevant to all of the contained Sections and/or Items.
The 'BlockQuote' complexType is the container for content that is equivalent to the HTML 'blockquote' markup.
The 'Caption' complexType is the container for content that is equivalent to the HTML 'caption' markup.
The 'ColGroup' complexType is the container for set of columns defined within a table. The content is the set of 'col' HTML markup.
The 'DD' complexType is the container for term definitions as per the HTML 'dd' markup.
The 'Div' complexType is the container for content that is equivalent to the HTML 'div' markup.
The 'DL' complexType is the container for list definitions as per the HTML 'dl' markup. This can contain any combination of 'dd' and 'dt' HTML elements.
The 'DT' complexType is the container for term definitions as per the HTML 'dt' markup.
The complexType for the set of HTML text elements i.e. h1, h2, h3, h4, h5, h6, p, pre and address.
The 'LI' complexType is the container for the definition of lists as per the HTML 'li' markup.
The Object complexType is the container for the objects used with the associated content i.e. positionObjectStage, graphicInteraction, positionObjectInteraction, mediaInteraction, drawingInteraction and gapImg.
The 'OUL' complexType is the container for ordered and unordered lists as per the HTML 'ul' and 'ol' markup.
The 'Q' complexType is the container for content that is equivalent to the HTML 'q' markup.
A rubric block identifies instructions to one or more of the actors that view the item or set of items (as per a section). Although rubric blocks are defined as simpleBlocks they must not contain interactions. The visibility of nested bodyElements or rubricBlocks is determined by the outermost element. In other words, if an element is determined to be hidden then all of its content is hidden including conditionally visible elements for which the conditions are satisfied and that therefore would otherwise be visible.
[APIP-Section (Entry)] Profile - the changes to the XML attribute list are:
* The "use" attribute class type has been changed to the class "UseType";
The 'Table' complexType is the container for content that is equivalent to the HTML 'table' markup.
The TablePart complexType is the container for set of table row content that is used to the support content within a table.
The 'TDH' complexType is the container for content that is equivalent to the HTML 'td' and 'th' markup within a table.
The information in a TemplateDefault complexType is used to alter the default value of a template variable declared by the item based on an expression evaluated at test-level. The default value of a template variable in an item can be overridden based on the test context in which the template is instantiated. The value is obtained by evaluating an expression defined within the reference to the item at test level and which may therefore depend on the values of variables taken from other items in the test or from outcomes defined at test level itself.
The 'TR' complexType is the container for content that is equivalent to the HTML 'tr' markup.
This is the container for referential link to an externally stored AssessmentSection (each such Section is stored in its own XML instance file). The identifier attribute should be used to identify the actual Section.
The 'BR' complexType is the container for content that is equivalent to the HTML 'br' markup.This ComplexType is intentionally empty.
The 'Col' complexType is the container for content that is equivalent to the HTML 'col' markup.This ComplexType is intentionally empty.
The 'HR' complexType is the container for content that is equivalent to the HTML 'hr' markup.This complexType is intentionally empty.
The 'Img' complexType is the container for content that is equivalent to the HTML 'img' markup.This ComplexType is intentionally empty.
This is used to associate an external stylesheet (it is assumed that this takes the form of a CSS file but other formats are permitted).
In the context of a specific assessmentTest an item, or group of items, may be subject to a time constraint. The QTI specification supports both minimum and maximum time constraints. The controlled time for a single item is simply the duration of the item session as defined by the builtin response variable duration. For assessmentSections, testParts and whole assessmentTests the time limits relate to the durations of all the item sessions plus any other time spent navigating that part of the test. In other words, the time includes time spent in states where no item is being interacted with, such as dedicated navigation screens. This complexType is intentionally empty.
The VariableMapping complexType is the contains the variable mappings that allow outcome variables declared with the name sourceIdentifier in the corresponding item to be treated as if they were declared with the name targetIdentifier during outcomeProcessing. Use of variable mappings allows more control over the way outcomes are aggregated when using testVariables.
The Weight complexType stores the weighting information. The contribution of an individual item score to an overall test score typically varies from test to test. The score of the item is said to be weighted. Weights are defined as part of each reference to an item (assessmentItemRef) within a test.