 |
 |
Discussions on the list in July 2005 - http://lists.ucles.org.uk/public/ims-qti/2005-July/thread.html Feedback June's query about providing different feedback for different attempts at an item was answered with this suggested solution: http://tinyurl.com/aerng. Cloze question Also from June, a cloze exercise (multiple fill-in-the-blank) solution was suggested: http://tinyurl.com/d9owc. Conformance testing There is no 'official' compliance test for QTI, but IMS have recently launched their compliancy programme supporting all their specifications: http://www.imsglobal.org/pressreleases/pro50711.cfm. Developers can also check their exported XML against validating parsers and test against other tools, for example at the CETIS CodeBashes (http://www.cetis.ac.uk/members/codebash3). The QTI project team are always keen to hear developers' experiences. Open source implementations of QTI Resources suggested included: APIS: http://sourceforge.net/projects/apis Samigo: http://www.sakaiproject.org/ Garret Wilson: http://globalmentor.com/software/com.garretwilson/doc/com/garretwilson/a ssess/qti/QTI.html. Clarification on which parts of QTI v1.2 are still current Information clarifying which parts of QTI v1.2 have been replaced in v2.0, and which are still current until the release of 2.1, is available at http://www.imsglobal.org/question/qti_v2p0/imsqti_oviewv2p0.html#section 10006. Response processing If an item uses both an externally defined response processing template and rules within a responseProcessing element, the internal rules take precedence, although it wasn't anticipated that the two methods would be combined. It's not a use case included in v2.0, but has been added to the issues list for 2.1. It's a nice idea, but could be too complex for implementors to have to deal with. The template system was introduced to remove a potential barrier to adoption of the specification, the need to develop an evaluation system: templates allow delivery engines to limit response processing to a restricted set of templates. Multiple items on a single page One method for combining multiple QTI items on a single page can be found at http://ti3.sri.com/qrender/qti/qti.jsf. However, this example would be understood as a single assessmentItem with a number of interactions within QTI. A version of the item as a single assessment item can be found at http://lists.ucles.org.uk/public/ims-qti/2005-July/001008.html. Layout As layout is outside QTI, it is appropriate to use cascading stylesheets to define how an item appears on the screen. Alternatively, developers could use a class attribute on the interaction itself and copy to the appropriate element when rendering in XHTML. It might be wise to prefix tags with "QTI_" to aid portability. RandomInteger parameters <randomInteger> generates an integer within values specified by the <min> and <max> attributes. The querent's specific use case requires that the <min> attribute is determined as a proportion of the value specified in <max>, which is not possible under v2.0 but which has been added to the issues list for possible inclusion in v2.1 - a useful reminder to raise your wishlist with the project team :-) To unsubscribe or change subscription options or search the list archives, visit http://www.jiscmail.ac.uk/lists/cetis-qti-sig.html.