JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for CETIS-QTI-SIG Archives


CETIS-QTI-SIG Archives

CETIS-QTI-SIG Archives


CETIS-QTI-SIG@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CETIS-QTI-SIG Home

CETIS-QTI-SIG Home

CETIS-QTI-SIG  2001

CETIS-QTI-SIG 2001

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

QTI Update

From:

Steve Lay <[log in to unmask]>

Reply-To:

Steve Lay <[log in to unmask]>

Date:

Thu, 12 Jul 2001 15:28:22 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (38 lines)

QTI-SIG People,

Following the meeting in Loughborough of the QTI working group the
following two issues which were discussed in Leeds were raised:

Min/Max in response processing.

The issue raised was what happens if multi-response multi-choice response
processing results in a number beyond the range of the min/max declared in
the associated decvar.  The position was clarified that outcome variables
must be constrained to their min/max values by implementations.  In other
words, if score is declared with min=0 and, during response processing, an
implementation attempts to subtract 1 from score when its current value is
0 its value will not change.  This discussion was not minuted though it was
agreed that we would examine the wording in the 1.1 spec to see if we can
help clarify this point in 1.2

Where is the stem?

We had some discussion about this as it was considered to be related to the
concept of section (or even assessment) level material which we have agreed
to support.  The upshot is that scenarios where you have some common
material followed by a set of questions each comprising stem and response
which you would like to manipulate individually will probably best be
implemented by placing the common material in the section and treating each
stem/response pair as an item.  The material for the stem is therefore the
material which sits in the item's presentation (but outside the response_*
tag) and can be distinguished.

This differs from the alternative approach which was to squeeze the stem
material between the response_* tag and the render_* tag and leave the
common material in the space between the item and the start of the response
and then manipulate the response_* tags.

Hope that makes sense.

Steve

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2014
March 2014
October 2013
June 2013
April 2013
March 2013
November 2012
August 2012
May 2012
February 2012
January 2012
November 2011
October 2011
September 2011
August 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager