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 Tests.
History: This is the first version of the APIPv1.0 QTIv2.2 Test Profile.
PROFILE: This is the "APIP-Test (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/qtitest/imsqti_v2p2".
* The schema version has been changed to "IMS APIP 1.0 QTI 2.2 TEST".
* 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 "AssessmentItemRef" class/complexType and set of XML attributes have been deleted;
* The "AssessmentSection" 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 "AssociableHotspot" class/complexType and set of XML attributes have been deleted;
* The "AssociateInteraction" 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 "CorrectResponse" class/complexType and set of XML attributes have been deleted;
* The "CustomInteraction" 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 "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 "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 "InlineChoice" class/complexType and set of XML attributes have been deleted;
* The "InlineChoiceInteraction" class/complexType and set of XML attributes have been deleted;
* The "ItemBody" class/complexType and set of XML attributes have been deleted;
* The "Label" class/complexType and set of XML attributes have been deleted;
* The "LookupOutcomeValue" 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 "MediaInteraction" class/complexType and set of XML attributes have been deleted;
* The "ModalFeedback" 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 "OutcomeProcessingFragment" class/complexType and set of XML attributes have been deleted;
* The "Param" 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 "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 "RubricBlock" 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 "SectionPart" 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 "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 "StimulusBody" 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 "TemplateDefault" 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 "TextEntryInteraction" class/complexType and set of XML attributes have been deleted;
* The "UploadInteraction" class/complexType and set of XML attributes have been deleted;
* The "VariableMapping" class/complexType and set of XML attributes have been deleted;
* The "Weight" class/complexType and set of XML attributes have been deleted;
* The "TestPart" class/complexType has been modified by:-
- The "preCondition" attribute has been prohibited;
- The "testFeedback" 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.
[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.
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.
[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.
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.
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.
The 'A' complexType is the container for content that is equivalent to the HTML 'a' markup.
The anyN operator takes one or more sub-expressions each with a base-type of boolean and single cardinality. The result is a single boolean which is true if at least min of the sub-expressions are true and at most max of the sub-expressions are true. If more than n - min sub-expressions are false (where n is the total number of sub-expressions) or more than max sub-expressions are true then the result is false. If one or more sub-expressions are NULL then it is possible that neither of these conditions is satisfied, in which case the operator results in NULL. For example, if min is 3 and max is 4 and the sub-expressions have values {true,true,false,NULL} then the operator results in NULL whereas {true,false,false,NULL} results in false and {true,true,true,NULL} results in true. The result NULL indicates that the correct value for the operator cannot be determined.
This is the container for the information about a Test. An 'assessmentTest' is the binding form of a Test. Each Test is composed of one or more TestParts (with each part consisting of at least one Section). Outcomes processing and feedback at the test level may be available.
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 custom operator provides a namespaced extension mechanism for defining operations not currently supported by this specification.
The 'DD' complexType is the container for term definitions as per the HTML 'dd' markup.
This is the container for the permitted set of default values. A human readable interpretation of the default value is also supplied using the 'interpretation' attribute.
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 equal operator takes two sub-expressions which must both have single cardinality and have a numerical base-type. The result is a single boolean with a value of true if the two expressions are numerically equal and false if they are not. If either sub-expression is NULL then the operator results in NULL.
The equalRounded operator takes two sub-expressions which must both have single cardinality and have a numerical base-type. The result is a single boolean with a value of true if the two expressions are numerically equal after rounding and false if they are not. If either sub-expression is NULL then the operator results in NULL.
The field-value operator takes a sub-expression with a record container value. The result is the value of the field with the specified fieldIdentifier. If there is no field with that identifier then the result of the operator is NULL.
The complexType for the set of HTML text elements i.e. h1, h2, h3, h4, h5, h6, p, pre and address.
The index operator takes a sub-expression with an ordered container value and any base-type. The result is the nth value of the container. The result has the same base-type as the sub-expression but single cardinality. The first value of a container has index 1, the second 2 and so on. n must be a positive integer. If n exceeds the number of values in the container (or the sub-expression is NULL) then the result of the index operator is NULL. If n is an identifier, it is the value of n at runtime that is used.
The 'InfoControl' complexType is the container to provide the candidate with extra information about the item when s/he chooses to trigger the control. The extra information can be a hint, but could also be additional tools such as a ruler or a (javaScript) calculator.
The inside operator takes a single sub-expression which must have a baseType of point. The result is a single boolean with a value of true if the given point is inside the area defined by shape and coords. If the sub-expression is a container the result is true if any of the points are inside the area. If either sub-expression is NULL then the operator results in NULL.
The InterpolationTable complexType is the container for interpolation information. An interpolationTable transforms a source float (or integer) by finding the first interpolationTableEntry with a sourceValue that is less than or equal to (subject to includeBoundary) the source value. For example, an interpolation table can be used to map a raw numeric score onto an identifier representing a grade. It may also be used to implement numeric transformations such as those from a simple raw score to a value on a calibrated scale.
The 'LI' complexType is the container for the definition of lists as per the HTML 'li' markup.
Provides the ability to use a multi variable operator e.g. an 'and' of the set of variables.
Provides the ability to use a multi variable operator e.g. an 'and' of the set of variables.
Provides the ability to use a two variable operator e.g. greater than.
Provides the ability to use a single variable operator e.g. a 'not'.
A special class used to create a mapping from a source set of any baseType (except file and duration) to a single float. Note that mappings from values of base type float should be avoided due to the difficulty of matching floating point values, see the match operator for more details. When mapping containers the result is the sum of the mapped values from the target set. See mapResponse for details.
The mathOperator operator takes 1 or more sub-expressions which all have single cardinality and have numerical base-types. The trigonometric functions, sin, cos and tan, take one argument in radians, which evaluates to a single float. Other functions take one numerical argument. Further functions might take more than one numerical argument, e.g. atan2 (two argument arc tan). The result is a single float, except for the functions signum, floor and ceil, which return a single integer. If any of the sub-expressions is NULL, the result is NULL. If any of the sub-expressions falls outside the natural domain of the function called by mathOperator, e.g. log(0) or asin(2), then the result is NULL.
Provides the ability to use a multi variable numeric-based operator e.g. a 'sum' of the set of variables.
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 OutcomeCondition complexType is the container for the sequence of outcome conditions to be applied. The condition is structured as an 'If..ElseIf..ElseIf..Else' sequence. Each clause as its own outcome rule construct.
The OutcomeDeclaration complexType is the container for the declaration of outcome variables. Outcome variables are declared by outcome declarations. Their value is set either from a default given in the declaration itself or by a 'responseRule' during 'responseProcessing'.
The OutcomeElse complexType is the container for 'Else' processing. An outcomeElse part consists of an expression which must have an effective baseType of boolean and single cardinality. For more information about the runtime data model employed see Expressions. It also contains a set of sub-rules. If the expression is true then the sub-rules are processed.
The OutcomeIf complexType is the container for 'If' processing. An outcomeIf part consists of an expression which must have an effective baseType of boolean and single cardinality. For more information about the runtime data model employed see Expressions. It also contains a set of sub-rules. If the expression is true then the sub-rules are processed, otherwise they are skipped (including if the expression is NULL) and the following outcomeElseIf or outcomeElse parts (if any) are considered instead.
The OutcomeProcessing complexType is the container for the outcome processing instructions. Outcome processing takes place each time the candidate submits the responses for an item (when in individual submission mode) or a group of items (when in simultaneous submission mode). It happens after any (item level) response processing triggered by the submission. The values of the test's outcome variables are always reset to their defaults prior to carrying out the instructions described by the outcomeRules. Because outcome processing happend each time the candidate submits responses the resulting values of the test-level outcomes may be used to activate test-level feedback during the test or to control the behaviour of subsequent parts through the use of preConditions and branchRules.
The patternMatch operator takes a sub-expression which must have single cardinality and a base-type of string. The result is a single boolean with a value of true if the sub-expression matches the regular expression given by pattern and false if it doesn't. If the sub-expression is NULL then the operator results in NULL.
The 'Q' complexType is the container for content that is equivalent to the HTML 'q' markup.
The repeat operator allows the filling of an ordered container. The result of a repeat operator is an ordered set of values calculated from the expressions. Values will be set in the associated container by a setTemplateValue expression. Each expression is calculated as many times as it is queried by numberRepeats.
The roundTo operator takes one sub-expression which must have single cardinality and a numerical base-type. The result is a single float with the value nearest to that of the expression's value such that when converted to a decimal string it represents the expression rounded by the specified rounding method to the specified precision. If the sub-expression is NULL, then the result is NULL. If the sub-expression is INF, then the result is INF. If the sub-expression is -INF, then the result is -INF. If the argument is NaN, then the result is NULL. When rounding to n significant figures, the deciding digit is the (n+1)th digit counting from the first non-zero digit from the left in the number. If the deciding digit is 5 or greater, the nth digit is increased by 1 and all digits to its right are discarded; if the deciding digit is less than 5, all digits to the right of the nth digit are discarded. When rounding to n decimal places, the deciding digit is the (n+1)th digit counting to the right from the decimal point. If the deciding digit is 5 or greater, the nth digit is increased by 1 and all digits to its right are discarded; if the deciding digit is less than 5, all digits to the right of the nth digit are discarded.
The SetValue complexType is the container for the value set for the associated element (the element is identified using the 'identifier' attribute).
The statsOperator operator takes 1 sub-expression which is a container of multiple or ordered cardinality and has a numerical base-type. The result is a single float. If the sub-expression or any value contained therein is NULL, the result is NULL. If any value contained in the sub-expression is not a numerical value, then the result is NULL.
The stringMatch operator takes two sub-expressions which must have single and a base-type of string. The result is a single boolean with a value of true if the two strings match according to the comparison rules defined by the attributes below and false if they don't. If either sub-expression is NULL then the operator results in NULL.
The substring operator takes two sub-expressions which must both have an effective base-type of string and single cardinality. The result is a single boolean with a value of true if the first expression is a substring of the second expression and false if it isn't. If either sub-expression is NULL then the result of the operator is NULL.
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 TestFeedback complexType is the container for the test feedback to be presented to the candidate. Test feedback is shown to the candidate either directly following outcome processing (during the test) or at the end of the testPart or assessmentTest as appropriate (referred to as atEnd). The value of an outcome variable is used in conjunction with the showHide and identifier attributes to determine whether or not the feedback is actually shown.
A Test is composed of one or more Test Parts. Each Test Part is used to control the presentation of a part of the Test - this allows a Test to be undertaken in several related but separated stages. A TestPart conatins one or more assessmentSections (either included or through external reference).
[APIP-Test (Entry)] Profile - the changes to the XML element list are:
* The "preCondition" element has been prohibited;
* The "testFeedback" element has been prohibited;
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 simplest expression returns a single value from the set defined by the given baseType.
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.
This expression looks up the declaration of a response variable and returns the associated correctResponse or NULL if no correct value was declared. When used in outcomes processing item identifier prefixing (see variable) may be used to obtain the correct response from an individual item. This is intentionally empty.
This expression looks up the declaration of an itemVariable and returns the associated defaultValue or NULL if no default value was declared. When used in outcomes processing item identifier prefixing (see variable) may be used to obtain the default value from an individual item. This 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.
The InterpolationTableEntry complexType is the container for an entry in the corresponding interpolationTable. This complexType is intentionally empty.
When items are referenced as part of a test, the test may impose constraints on how many attempts, and which states are allowed. These constraints can be specified for individual items, for whole sections or for an entire testPart. By default, a setting at testPart level affects all items in that part unless the setting is overridden at the assessmentSection level or ultimately at the individual assessmentItemRef. The defaults given below are used only in the absence of any applicable constraint. This complexType is intentionally empty.
The map is defined by a set of mapEntries, each of which maps a single value from the source set onto a single float.
This expression looks up the value of a response variable and then transforms it using the associated mapping, which must have been declared. The result is a single float. If the response variable has single cardinality then the value returned is simply the mapped target value from the map. If the response variable has multiple or ordered cardinality then the value returned is the sum of the mapped target values. This expression cannot be applied to variables of record cardinality. This is intentionally empty.
The result is a mathematical constant returned as a single float, e.g. pi and e.
Provides an operator that returns the number of values that confrm to the associated constraints e.g. 'numberCorrect'.
This expression, which can only be used in outcomes processing, simultaneously looks up the normal Maximum/Minimum value of an outcome variable in a sub-set of the items referred to in a test. Only variables with single cardinality are considered. If any of the items within the given subset have no declared maximum the result is NULL, otherwise the result has cardinality multiple and base-type float. This is intentionally empty.
Selects a random float from the specified range [min,max]. This is intentionally empty.
Selects a random integer from the specified range [min,max] satisfying min + step * n for some integer n. For example, with min=2, max=11 and step=3 the values {2,5,8,11} are possible.
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).
This expression, which can only be used in outcomes processing, simultaneously looks up the value of an itemVariable in a sub-set of the items referred to in a test. Only variables with single cardinality are considered, all NULL values are ignored. The result has cardinality multiple and base-type as specified below. This is intentionally empty.
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.
A class that can represent a single value of any baseType in variable declarations and result reports. The base-type is defined by the baseType attribute of the declaration except in the case of variables with record cardinality.
This expression looks up the value of an itemVariable that has been declared in a corresponding variableDeclaration or is one of the built-in variables. The result has the base-type and cardinality declared for the variable subject to the type promotion of weighted outcomes. This is intentionally empty.