Microformats Wiki - User contributions [en]

User:JSalsman

2010-03-05T17:16:19Z

JSalsman: email

working on [[gift]] for [http://strategy.wikimedia.org/wiki/Proposal:Assessment_content assessment content]

jsalsman at talknicer dot com

gift

2010-03-05T17:15:47Z

JSalsman: /* Notes for further work */ clarify

__TOC__

<entry-title>GIFT Format</entry-title>
;short URL
:http://bit.ly/gift-fmt 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format. The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format. The extensions described below should enable easily authorable self-study, learner-adaptive, low-stakes quiz extensions for Wikiversity and other projects.

=== Syntax ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===

Please help sponsor these extensions at http://talknicer.com

==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || Set of questions which help answer this question
|-
| // helped-by: title[,...] || Set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || Sets of relations to other questions by relative difficulty
|-
| // general-help: text || Optional general help
|-
| // specific-help: text || Optional specific help
|-
| \// || Two forward slashes, not a comment
|-
| // review-state: text || Summary of accuracy review status (see below)
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Examples ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // numeric quantity for relative difficulty
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // summary of review status

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

=== Notes for further work ===

The score-based computer adaptive testing process already implemented in Moodle may be much simpler and easier to re-implement than del Soldato and du Boulay's 1995 [[gift-syntax/dsd-tutor-rules|rules]] -- which require assessment of confidence (self-reported), effort (logging), and independence (frequency of help requests) instead of just scoring questions -- and [[gift-syntax/dsd-tutor-schema|this schema]] based on those rules and the ''Journal of Artificial Intelligence in Education'' article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article and [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories.

; Please disregard posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
**[https://bugzilla.wikimedia.org/show_bug.cgi?id=22475 Mediawiki bug (enhancement request) 22475]
*[http://strategy.wikimedia.org/wiki/Proposal:Assessment_content Wikimedia assessment content proposal]
**http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]
**http://en.wikiversity.org/wiki/Category:Quizzes

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-03-05T15:55:31Z

JSalsman: /* Possible choices */ Moodle has learner-adaptivity based on scores, but not confidence, effort, or independence

__TOC__

<entry-title>GIFT Format</entry-title>
;short URL
:http://bit.ly/gift-fmt 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format. The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format. The extensions described below should enable easily authorable self-study, learner-adaptive, low-stakes quiz extensions for Wikiversity and other projects.

=== Syntax ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===

Please help sponsor these extensions at http://talknicer.com

==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || Set of questions which help answer this question
|-
| // helped-by: title[,...] || Set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || Sets of relations to other questions by relative difficulty
|-
| // general-help: text || Optional general help
|-
| // specific-help: text || Optional specific help
|-
| \// || Two forward slashes, not a comment
|-
| // review-state: text || Summary of accuracy review status (see below)
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Examples ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // numeric quantity for relative difficulty
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // summary of review status

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

=== Notes for further work ===

The adaptive assessment format in Moodle may be much simpler and easier to implement than del Soldato and du Boulay's 1995 [[gift-syntax/dsd-tutor-rules|rules]] -- which require assessment of confidence (self-reported), effort (logging), and independence (frequency of help requests) instead of just scoring questions -- and [[gift-syntax/dsd-tutor-schema|this schema]] based on those rules and the ''Journal of Artificial Intelligence in Education'' article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article and [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories.

; Please disregard posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
**[https://bugzilla.wikimedia.org/show_bug.cgi?id=22475 Mediawiki bug (enhancement request) 22475]
*[http://strategy.wikimedia.org/wiki/Proposal:Assessment_content Wikimedia assessment content proposal]
**http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]
**http://en.wikiversity.org/wiki/Category:Quizzes

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift-syntax/dsd-tutor-schema

2010-03-02T22:18:47Z

JSalsman: eliminate piped link to less common nomenclature

; for [[GIFT]] quizes

Based on del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78:

<pre>
Problem:
description: text
initial_steps: SET < answer, step > # enabled by default at problem onset
similarity: LIST < problem, integer > # degree of similarity
# intransitivities can be used for broader/narrower distinctions
difficulty: LIST < problem, success_predictor_tried, success_pred_untried >
# regression coefficients can be guessed apriori or derived from practice
INSTANCE success: untried or [0..1] # partial credit
assessments: SET < minimum_success, text >
# the greatest assessment not exceeding success(problem) shown when needed
Answer:
check: pattern # such as a regular expression describing an answer
# In general, if more than one answer checks, perhaps more input is
# needed to disambiguate. If none is available, then the system
# might just ask for specification.
meaning: [ accomplishment | giveup | help | agree | disagree ]
# I use "agree" and "disagree" instead of "positive" and "negative" here
confidence: integer
# in speech, confidence can be derived from prosody or relative loudness
Step:
repetition_limit: posint
enables: SET < answer, step > # this step is a prereq of these steps
disables: SET step # this step precludes these steps
# steps remain enabled unless they are explicitly disabled, I suppose
success_level: [0..1] # assigned to success(problem)
present_step_help: help
next_step_help: LIST < step, help > # only enabled steps are helped with
surprise_result: help
INSTANCE repetitions: nonnegint
INSTANCE previous: step # this could be a list for tracking cycles
feedback: comment or content_type # custom or stock feedback
# make sure this fits into the rules as designed
Help:
general: text or macro script which may refer to problems or steps
# macros allow referring to another problem only if it has been completed
specific: text or macro script which may refer to problems or steps
# specific help ought to be able to call a (simple) sub-problem
INSTANCE acceptance: integer # the degree to which help was accepted
Comment:
[ content-type: text ] # may be omitted where they can be taken from stock.
# Text here ought to allow variable substitution if not full-fledged macros.
# Comments should also be added to provide reports to human instructors.
# more work needed for surprise_result, text/macro (HTML?), and set specification
</pre>

gift-syntax/dsd-tutor-rules

2010-03-02T22:18:04Z

JSalsman: eliminate redirect

; for [[GIFT]] quizes

Adapted and annotated from figures in del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78:

<pre>
# perfomance modeling - t6p355rP1-2

Rule P1 -- perfomance model successful:
if agreements/completed > perf-threshold
then perf-value = successful
Rule P2 -- perfomance model unsuccessful:
if agreements/completed <= perf-threshold
then perf-value = unsuccessful

# repitition testing - t6p355rP3-4

Rule P3 -- path model lost:
if tries > step-repition-limit (from problem type)
then path-state = lost
Rule P4 -- path model OK:
if tries <= step-repition-limit (from problem type)
then path-state = OK

# confidence modeling - t7p356rC1-2

Rule C1:
if answer was low-confidence (either agree or disagree)
then decrement conf-value
Rule C2:
if answer was high-confidence (either agree or disagree)
then increment conf-value

Rule C3 -- decrease modeled confidence on help request:
if answer was help request
then decrement conf-value

Rule C4:
if problem-state = succeeded
and without help
then increment conf-value by large-conf-inc
Rule C5:
if problem-state = succeeded
and with help
then increment conf-value
Rule C6:
if problem-state = failed
and without help
then decrement conf-value
Rule C7:
if problem-state = failed
and with help
then decrement conf-value by large-conf-dec

# effort modeling - t8p357 (non-rule)

if path-state = lost
then effort-value = "medium" + 1
if problem-state = succeeded
then effort-value += 2
if help was asked for
then effort-value += 1

# independence modelling - t9p358rI1-I4

Rule I1:
if help-state = suggesting
then decrement indep-value

Rule I2:
if help-state = providing
and detail = general
then decrement indep-value

Rule I3:
if help-state = providing
and detail = specific
then decrement indep-value by large-indep-dec

Rule I4:
if help-state = rejected
then increment indep-value by large-indep-inc

# domain-based planner rules - t10p359rD1-D7

Rule D1:
if problem-state = succeeded
then provide right assessment; suggest harder problem
Rule D2:
if problem-state = failed
then provide wrong assessment; suggest same-diff problem
Rule D3:
if problem-state = given-up
then suggest same-diff problem
Rule D4:
if problem-state = rejected
then suggest same-diff problem

Rule D5:
if help-state = requested
then provide help
Rule D6:
if help-state = rejected
then help not-needed

Rule D7:
if path-state = lost
then provide help

# motivational planner rules - t11p360rM1-M20

Rule M1:
if conf-value < conf-threshold
then increase confidence # when and how is this reset?
Rule M2:
if effort-value < "medium"
then increase effort
Rule M3:
if effort-value > "medium"
then maintain effort
Rule M4:
if help-state = rejected
then respect control
Rule M5:
if problem-state = given-up # "above give-up-lim"
then respect control
Rule M6:
if indep-value < indep-threshold
and not increase confidence
then increase control
Rule M7:
if problem-state = succeeded
and increase confidence
then increase experience success
Rule M8:
if problem-state = failed
and increase confidence
then facilitate success
Rule M9:
if problem-state = given-up
and increase effort (M2)
and not increase confidence
and not respect control
then encourage effort
Rule M10:
if problem-state = given-up
and increase confidence
and not respect control
then facilitate success
Rule M11:
if problem-state = succeeded
and increase effort
then stimulate challenge
Rule M12:
if stimulate challence (M11)
and increase confidence (M1)
then emphasise promotion
Rule M13:
if problem-state = failed
and increase effort
and not increase confidence
then stimulate curiosity
Rule M14:
if perf-value = successful
and facilitate success
and increase effort
then remind success
Rule M15:
if path-state = lost
and increase control
then avoid intervention
Rule M16:
if help-state = requested
and increase control
then encourage independence
Rule M17:
if encourage independence
then avoid intervention
Rule M18:
if help-state = rejected
and help-skip-next = no (needs to be fitted to "skip next help" or whatever)
and respect control
then avoid next intervention
Rule M19:
if help-state != rejected
and help-skip-next = yes (ditto)
then avoid intervention
Rule M20:
if help-state != requested
and not increase confidence
and not stimulate curiosity
then share control

# negotiated actions - t12p363-rN1-N7

Rule N1
action: suggest harder problem
tactics: increase success; not stimulate challenge
negotiated: suggest problem, similar difficulty

Rule N2
action: suggest harder problem
tactic: stimulate challenge; not increase confidence
negotiated: suggest much-harder problem

Rule N3
action: suggest harder problem
tactic: emphasise promotion
negotiated: suggest harder problem; provide level-promotion comment

Rule N4
action: provide wrong assessment; suggest same-diff problem
tactic: emphasize promotion
negotiated: suggest harder problem; provide level-promotion comment

Rule N5 -- requires suprise result
action: provide wrong assessment
tactic: stimulate curiosity (M13)
negotiated: provide suprise result help

Rule N6
action: provide right assessment
tactic: maintain effort
negotiated: provide right assessment; provide praise performance comment

Rule N7
action: provide wrong assessment
tactic: maintain effort
negotiated: provide wrong assessment; provide praise performance comment

# negotiated actions (cont) - t12p364rN8-N15

Rule N8
action: suggest problem; not provide assessment
tactic: facilitate success; not respect control
negotiated: provide help

Rule N9
action: suggest problem; not provide assessment
tactic: encourage effort
negotiated: provide trying-harder comment; suggest help

Rule N10
action: ---
tactic: remind successes
negotiated: provide previous-successes comment

Rule N11
action: provide help
tactic: avoid intervention
negotiated: skip help

Rule N12
action: ---
tactic: encourage independence
negotiated: provide encourage-indep comment

Rule N13
action: provide general help
tactic: increase confidence
negotiated: provide specific help

Rule N14
action: provide help
tactic: share control
negotiated: suggest help

Rule N15
action: help not-needed
tactic: avoid next intervention
negotiated: skip next-help
</pre>

GIFT

2010-03-02T22:17:41Z

JSalsman: to make other elimination of redirects work

#redirect [[gift]]

User:JSalsman

2010-03-02T22:16:54Z

JSalsman: rename per "format" common usage

working on [[gift]] for [http://strategy.wikimedia.org/wiki/Proposal:Assessment_content assessment content]

gift

2010-03-02T22:15:26Z

JSalsman: /* Format */ syntax?

__TOC__

<entry-title>GIFT Format</entry-title>
;short URL
:http://bit.ly/gift-fmt 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format. The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format. The extensions described below should enable easily authorable self-study, learner-adaptive, low-stakes quiz extensions for Wikiversity and other projects.

=== Syntax ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===

Please help sponsor these extensions at http://talknicer.com

==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || Set of questions which help answer this question
|-
| // helped-by: title[,...] || Set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || Sets of relations to other questions by relative difficulty
|-
| // general-help: text || Optional general help
|-
| // specific-help: text || Optional specific help
|-
| \// || Two forward slashes, not a comment
|-
| // review-state: text || Summary of accuracy review status (see below)
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // numeric quantity for relative difficulty
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // summary of review status

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [[gift-syntax/dsd-tutor-rules|rules]] and [[gift-syntax/dsd-tutor-schema|this schema]] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
**[https://bugzilla.wikimedia.org/show_bug.cgi?id=22475 Mediawiki bug (enhancement request) 22475]
*[http://strategy.wikimedia.org/wiki/Proposal:Assessment_content Wikimedia assessment content proposal]
**http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]
**http://en.wikiversity.org/wiki/Category:Quizzes

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-03-02T22:15:03Z

JSalsman: retitle

__TOC__

<entry-title>GIFT Format</entry-title>
;short URL
:http://bit.ly/gift-fmt 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format. The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format. The extensions described below should enable easily authorable self-study, learner-adaptive, low-stakes quiz extensions for Wikiversity and other projects.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===

Please help sponsor these extensions at http://talknicer.com

==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || Set of questions which help answer this question
|-
| // helped-by: title[,...] || Set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || Sets of relations to other questions by relative difficulty
|-
| // general-help: text || Optional general help
|-
| // specific-help: text || Optional specific help
|-
| \// || Two forward slashes, not a comment
|-
| // review-state: text || Summary of accuracy review status (see below)
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // numeric quantity for relative difficulty
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // summary of review status

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [[gift-syntax/dsd-tutor-rules|rules]] and [[gift-syntax/dsd-tutor-schema|this schema]] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
**[https://bugzilla.wikimedia.org/show_bug.cgi?id=22475 Mediawiki bug (enhancement request) 22475]
*[http://strategy.wikimedia.org/wiki/Proposal:Assessment_content Wikimedia assessment content proposal]
**http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]
**http://en.wikiversity.org/wiki/Category:Quizzes

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift-syntax

2010-03-02T22:14:27Z

JSalsman: gift-syntax moved to gift over redirect: it's being referred to as a format more than a syntax

#REDIRECT [[gift]]

gift

2010-03-02T22:14:27Z

JSalsman: gift-syntax moved to gift over redirect: it's being referred to as a format more than a syntax

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/gift-fmt 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format. The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format. The extensions described below should enable easily authorable self-study, learner-adaptive, low-stakes quiz extensions for Wikiversity and other projects.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===

Please help sponsor these extensions at http://talknicer.com

==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || Set of questions which help answer this question
|-
| // helped-by: title[,...] || Set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || Sets of relations to other questions by relative difficulty
|-
| // general-help: text || Optional general help
|-
| // specific-help: text || Optional specific help
|-
| \// || Two forward slashes, not a comment
|-
| // review-state: text || Summary of accuracy review status (see below)
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // numeric quantity for relative difficulty
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // summary of review status

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [[gift-syntax/dsd-tutor-rules|rules]] and [[gift-syntax/dsd-tutor-schema|this schema]] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
**[https://bugzilla.wikimedia.org/show_bug.cgi?id=22475 Mediawiki bug (enhancement request) 22475]
*[http://strategy.wikimedia.org/wiki/Proposal:Assessment_content Wikimedia assessment content proposal]
**http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]
**http://en.wikiversity.org/wiki/Category:Quizzes

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-03-02T20:12:50Z

JSalsman: /* Extensions */ open source sponsorship drive

gift

2010-02-23T16:59:18Z

JSalsman: elaborate motivation

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/gift-fmt 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format. The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format. The extensions described below should enable easily authorable self-study, learner-adaptive, low-stakes quiz extensions for Wikiversity and other projects.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || Set of questions which help answer this question
|-
| // helped-by: title[,...] || Set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || Sets of relations to other questions by relative difficulty
|-
| // general-help: text || Optional general help
|-
| // specific-help: text || Optional specific help
|-
| \// || Two forward slashes, not a comment
|-
| // review-state: text || Summary of accuracy review status (see below)
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // numeric quantity for relative difficulty
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // summary of review status

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [[gift-syntax/dsd-tutor-rules|rules]] and [[gift-syntax/dsd-tutor-schema|this schema]] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
**[https://bugzilla.wikimedia.org/show_bug.cgi?id=22475 Mediawiki bug (enhancement request) 22475]
*[http://strategy.wikimedia.org/wiki/Proposal:Assessment_content Wikimedia assessment content proposal]
**http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]
**http://en.wikiversity.org/wiki/Category:Quizzes

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-02-23T16:29:15Z

JSalsman: /* See also */ existing wikiversity quiz content

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/gift-fmt 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || Set of questions which help answer this question
|-
| // helped-by: title[,...] || Set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || Sets of relations to other questions by relative difficulty
|-
| // general-help: text || Optional general help
|-
| // specific-help: text || Optional specific help
|-
| \// || Two forward slashes, not a comment
|-
| // review-state: text || Summary of accuracy review status (see below)
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // numeric quantity for relative difficulty
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // summary of review status

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [[gift-syntax/dsd-tutor-rules|rules]] and [[gift-syntax/dsd-tutor-schema|this schema]] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
**[https://bugzilla.wikimedia.org/show_bug.cgi?id=22475 Mediawiki bug (enhancement request) 22475]
*[http://strategy.wikimedia.org/wiki/Proposal:Assessment_content Wikimedia assessment content proposal]
**http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]
**http://en.wikiversity.org/wiki/Category:Quizzes

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-02-21T18:08:09Z

JSalsman: avoid "gift tax" association

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/gift-fmt 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || Set of questions which help answer this question
|-
| // helped-by: title[,...] || Set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || Sets of relations to other questions by relative difficulty
|-
| // general-help: text || Optional general help
|-
| // specific-help: text || Optional specific help
|-
| \// || Two forward slashes, not a comment
|-
| // review-state: text || Summary of accuracy review status (see below)
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // numeric quantity for relative difficulty
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // summary of review status

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [[gift-syntax/dsd-tutor-rules|rules]] and [[gift-syntax/dsd-tutor-schema|this schema]] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
**[https://bugzilla.wikimedia.org/show_bug.cgi?id=22475 Mediawiki bug (enhancement request) 22475]
*[http://strategy.wikimedia.org/wiki/Proposal:Assessment_content Wikimedia assessment content proposal]
**http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-02-16T05:51:01Z

JSalsman: /* See also */ wikiversity was created to hold assessment and other procedural content

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || Set of questions which help answer this question
|-
| // helped-by: title[,...] || Set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || Sets of relations to other questions by relative difficulty
|-
| // general-help: text || Optional general help
|-
| // specific-help: text || Optional specific help
|-
| \// || Two forward slashes, not a comment
|-
| // review-state: text || Summary of accuracy review status (see below)
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // numeric quantity for relative difficulty
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // summary of review status

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [[gift-syntax/dsd-tutor-rules|rules]] and [[gift-syntax/dsd-tutor-schema|this schema]] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
**[https://bugzilla.wikimedia.org/show_bug.cgi?id=22475 Mediawiki bug (enhancement request) 22475]
*[http://strategy.wikimedia.org/wiki/Proposal:Assessment_content Wikimedia assessment content proposal]
**http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-02-16T05:22:32Z

JSalsman: http://strategy.wikimedia.org/wiki/Proposal:Assessment_content

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || Set of questions which help answer this question
|-
| // helped-by: title[,...] || Set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || Sets of relations to other questions by relative difficulty
|-
| // general-help: text || Optional general help
|-
| // specific-help: text || Optional specific help
|-
| \// || Two forward slashes, not a comment
|-
| // review-state: text || Summary of accuracy review status (see below)
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // numeric quantity for relative difficulty
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // summary of review status

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [[gift-syntax/dsd-tutor-rules|rules]] and [[gift-syntax/dsd-tutor-schema|this schema]] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
**[https://bugzilla.wikimedia.org/show_bug.cgi?id=22475 Mediawiki bug (enhancement request) 22475]
*http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]
**[http://strategy.wikimedia.org/wiki/Proposal:Assessment_content Wikimedia assessment content proposal]

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-02-14T02:11:23Z

JSalsman: /* See also */ mediawiki bug 22475

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || Set of questions which help answer this question
|-
| // helped-by: title[,...] || Set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || Sets of relations to other questions by relative difficulty
|-
| // general-help: text || Optional general help
|-
| // specific-help: text || Optional specific help
|-
| \// || Two forward slashes, not a comment
|-
| // review-state: text || Summary of accuracy review status (see below)
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // numeric quantity for relative difficulty
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // summary of review status

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [[gift-syntax/dsd-tutor-rules|rules]] and [[gift-syntax/dsd-tutor-schema|this schema]] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
**[https://bugzilla.wikimedia.org/show_bug.cgi?id=22475 Mediawiki bug (enhancement request) 22475]
*http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-02-12T21:34:35Z

JSalsman: /* Learner adaptation */ title case

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || Set of questions which help answer this question
|-
| // helped-by: title[,...] || Set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || Sets of relations to other questions by relative difficulty
|-
| // general-help: text || Optional general help
|-
| // specific-help: text || Optional specific help
|-
| \// || Two forward slashes, not a comment
|-
| // review-state: text || Summary of accuracy review status (see below)
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // numeric quantity for relative difficulty
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // summary of review status

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [[gift-syntax/dsd-tutor-rules|rules]] and [[gift-syntax/dsd-tutor-schema|this schema]] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
*http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift-syntax/dsd-tutor-rules

2010-02-12T01:11:15Z

JSalsman: backlink

; for [[gift-syntax|GIFT]] quizes

Adapted and annotated from figures in del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78:

<pre>
# perfomance modeling - t6p355rP1-2

Rule P1 -- perfomance model successful:
if agreements/completed > perf-threshold
then perf-value = successful
Rule P2 -- perfomance model unsuccessful:
if agreements/completed <= perf-threshold
then perf-value = unsuccessful

# repitition testing - t6p355rP3-4

Rule P3 -- path model lost:
if tries > step-repition-limit (from problem type)
then path-state = lost
Rule P4 -- path model OK:
if tries <= step-repition-limit (from problem type)
then path-state = OK

# confidence modeling - t7p356rC1-2

Rule C1:
if answer was low-confidence (either agree or disagree)
then decrement conf-value
Rule C2:
if answer was high-confidence (either agree or disagree)
then increment conf-value

Rule C3 -- decrease modeled confidence on help request:
if answer was help request
then decrement conf-value

Rule C4:
if problem-state = succeeded
and without help
then increment conf-value by large-conf-inc
Rule C5:
if problem-state = succeeded
and with help
then increment conf-value
Rule C6:
if problem-state = failed
and without help
then decrement conf-value
Rule C7:
if problem-state = failed
and with help
then decrement conf-value by large-conf-dec

# effort modeling - t8p357 (non-rule)

if path-state = lost
then effort-value = "medium" + 1
if problem-state = succeeded
then effort-value += 2
if help was asked for
then effort-value += 1

# independence modelling - t9p358rI1-I4

Rule I1:
if help-state = suggesting
then decrement indep-value

Rule I2:
if help-state = providing
and detail = general
then decrement indep-value

Rule I3:
if help-state = providing
and detail = specific
then decrement indep-value by large-indep-dec

Rule I4:
if help-state = rejected
then increment indep-value by large-indep-inc

# domain-based planner rules - t10p359rD1-D7

Rule D1:
if problem-state = succeeded
then provide right assessment; suggest harder problem
Rule D2:
if problem-state = failed
then provide wrong assessment; suggest same-diff problem
Rule D3:
if problem-state = given-up
then suggest same-diff problem
Rule D4:
if problem-state = rejected
then suggest same-diff problem

Rule D5:
if help-state = requested
then provide help
Rule D6:
if help-state = rejected
then help not-needed

Rule D7:
if path-state = lost
then provide help

# motivational planner rules - t11p360rM1-M20

Rule M1:
if conf-value < conf-threshold
then increase confidence # when and how is this reset?
Rule M2:
if effort-value < "medium"
then increase effort
Rule M3:
if effort-value > "medium"
then maintain effort
Rule M4:
if help-state = rejected
then respect control
Rule M5:
if problem-state = given-up # "above give-up-lim"
then respect control
Rule M6:
if indep-value < indep-threshold
and not increase confidence
then increase control
Rule M7:
if problem-state = succeeded
and increase confidence
then increase experience success
Rule M8:
if problem-state = failed
and increase confidence
then facilitate success
Rule M9:
if problem-state = given-up
and increase effort (M2)
and not increase confidence
and not respect control
then encourage effort
Rule M10:
if problem-state = given-up
and increase confidence
and not respect control
then facilitate success
Rule M11:
if problem-state = succeeded
and increase effort
then stimulate challenge
Rule M12:
if stimulate challence (M11)
and increase confidence (M1)
then emphasise promotion
Rule M13:
if problem-state = failed
and increase effort
and not increase confidence
then stimulate curiosity
Rule M14:
if perf-value = successful
and facilitate success
and increase effort
then remind success
Rule M15:
if path-state = lost
and increase control
then avoid intervention
Rule M16:
if help-state = requested
and increase control
then encourage independence
Rule M17:
if encourage independence
then avoid intervention
Rule M18:
if help-state = rejected
and help-skip-next = no (needs to be fitted to "skip next help" or whatever)
and respect control
then avoid next intervention
Rule M19:
if help-state != rejected
and help-skip-next = yes (ditto)
then avoid intervention
Rule M20:
if help-state != requested
and not increase confidence
and not stimulate curiosity
then share control

# negotiated actions - t12p363-rN1-N7

Rule N1
action: suggest harder problem
tactics: increase success; not stimulate challenge
negotiated: suggest problem, similar difficulty

Rule N2
action: suggest harder problem
tactic: stimulate challenge; not increase confidence
negotiated: suggest much-harder problem

Rule N3
action: suggest harder problem
tactic: emphasise promotion
negotiated: suggest harder problem; provide level-promotion comment

Rule N4
action: provide wrong assessment; suggest same-diff problem
tactic: emphasize promotion
negotiated: suggest harder problem; provide level-promotion comment

Rule N5 -- requires suprise result
action: provide wrong assessment
tactic: stimulate curiosity (M13)
negotiated: provide suprise result help

Rule N6
action: provide right assessment
tactic: maintain effort
negotiated: provide right assessment; provide praise performance comment

Rule N7
action: provide wrong assessment
tactic: maintain effort
negotiated: provide wrong assessment; provide praise performance comment

# negotiated actions (cont) - t12p364rN8-N15

Rule N8
action: suggest problem; not provide assessment
tactic: facilitate success; not respect control
negotiated: provide help

Rule N9
action: suggest problem; not provide assessment
tactic: encourage effort
negotiated: provide trying-harder comment; suggest help

Rule N10
action: ---
tactic: remind successes
negotiated: provide previous-successes comment

Rule N11
action: provide help
tactic: avoid intervention
negotiated: skip help

Rule N12
action: ---
tactic: encourage independence
negotiated: provide encourage-indep comment

Rule N13
action: provide general help
tactic: increase confidence
negotiated: provide specific help

Rule N14
action: provide help
tactic: share control
negotiated: suggest help

Rule N15
action: help not-needed
tactic: avoid next intervention
negotiated: skip next-help
</pre>

gift-syntax/dsd-tutor-schema

2010-02-12T01:07:42Z

JSalsman: backlink

; for [[gift-syntax|GIFT]] quizes

Based on del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78:

<pre>
Problem:
description: text
initial_steps: SET < answer, step > # enabled by default at problem onset
similarity: LIST < problem, integer > # degree of similarity
# intransitivities can be used for broader/narrower distinctions
difficulty: LIST < problem, success_predictor_tried, success_pred_untried >
# regression coefficients can be guessed apriori or derived from practice
INSTANCE success: untried or [0..1] # partial credit
assessments: SET < minimum_success, text >
# the greatest assessment not exceeding success(problem) shown when needed
Answer:
check: pattern # such as a regular expression describing an answer
# In general, if more than one answer checks, perhaps more input is
# needed to disambiguate. If none is available, then the system
# might just ask for specification.
meaning: [ accomplishment | giveup | help | agree | disagree ]
# I use "agree" and "disagree" instead of "positive" and "negative" here
confidence: integer
# in speech, confidence can be derived from prosody or relative loudness
Step:
repetition_limit: posint
enables: SET < answer, step > # this step is a prereq of these steps
disables: SET step # this step precludes these steps
# steps remain enabled unless they are explicitly disabled, I suppose
success_level: [0..1] # assigned to success(problem)
present_step_help: help
next_step_help: LIST < step, help > # only enabled steps are helped with
surprise_result: help
INSTANCE repetitions: nonnegint
INSTANCE previous: step # this could be a list for tracking cycles
feedback: comment or content_type # custom or stock feedback
# make sure this fits into the rules as designed
Help:
general: text or macro script which may refer to problems or steps
# macros allow referring to another problem only if it has been completed
specific: text or macro script which may refer to problems or steps
# specific help ought to be able to call a (simple) sub-problem
INSTANCE acceptance: integer # the degree to which help was accepted
Comment:
[ content-type: text ] # may be omitted where they can be taken from stock.
# Text here ought to allow variable substitution if not full-fledged macros.
# Comments should also be added to provide reports to human instructors.
# more work needed for surprise_result, text/macro (HTML?), and set specification
</pre>

gift

2010-02-12T01:03:40Z

JSalsman: /* Possible choices */ archive.org is too slow

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || set of questions which help answer this question
|-
| // helped-by: title[,...] || set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || set of relations to other questions by relative difficulty
|-
| // general-help: text || optional general help
|-
| // specific-help: text || optional specific help
|-
| \// || Two forward slashes
|-
| // review-state: text || summary of accuracy review status
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // numeric quantity for relative difficulty
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // summary of review status

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [[gift-syntax/dsd-tutor-rules|rules]] and [[gift-syntax/dsd-tutor-schema|this schema]] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
*http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift-syntax/dsd-tutor-schema

2010-02-12T01:03:23Z

JSalsman: archive.org is too slow

Based on del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78:

<pre>
Problem:
description: text
initial_steps: SET < answer, step > # enabled by default at problem onset
similarity: LIST < problem, integer > # degree of similarity
# intransitivities can be used for broader/narrower distinctions
difficulty: LIST < problem, success_predictor_tried, success_pred_untried >
# regression coefficients can be guessed apriori or derived from practice
INSTANCE success: untried or [0..1] # partial credit
assessments: SET < minimum_success, text >
# the greatest assessment not exceeding success(problem) shown when needed
Answer:
check: pattern # such as a regular expression describing an answer
# In general, if more than one answer checks, perhaps more input is
# needed to disambiguate. If none is available, then the system
# might just ask for specification.
meaning: [ accomplishment | giveup | help | agree | disagree ]
# I use "agree" and "disagree" instead of "positive" and "negative" here
confidence: integer
# in speech, confidence can be derived from prosody or relative loudness
Step:
repetition_limit: posint
enables: SET < answer, step > # this step is a prereq of these steps
disables: SET step # this step precludes these steps
# steps remain enabled unless they are explicitly disabled, I suppose
success_level: [0..1] # assigned to success(problem)
present_step_help: help
next_step_help: LIST < step, help > # only enabled steps are helped with
surprise_result: help
INSTANCE repetitions: nonnegint
INSTANCE previous: step # this could be a list for tracking cycles
feedback: comment or content_type # custom or stock feedback
# make sure this fits into the rules as designed
Help:
general: text or macro script which may refer to problems or steps
# macros allow referring to another problem only if it has been completed
specific: text or macro script which may refer to problems or steps
# specific help ought to be able to call a (simple) sub-problem
INSTANCE acceptance: integer # the degree to which help was accepted
Comment:
[ content-type: text ] # may be omitted where they can be taken from stock.
# Text here ought to allow variable substitution if not full-fledged macros.
# Comments should also be added to provide reports to human instructors.
# more work needed for surprise_result, text/macro (HTML?), and set specification
</pre>

gift-syntax/dsd-tutor-rules

2010-02-12T01:00:50Z

JSalsman: archive.org is too slow

Adapted and annotated from figures in del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78:

<pre>
# perfomance modeling - t6p355rP1-2

Rule P1 -- perfomance model successful:
if agreements/completed > perf-threshold
then perf-value = successful
Rule P2 -- perfomance model unsuccessful:
if agreements/completed <= perf-threshold
then perf-value = unsuccessful

# repitition testing - t6p355rP3-4

Rule P3 -- path model lost:
if tries > step-repition-limit (from problem type)
then path-state = lost
Rule P4 -- path model OK:
if tries <= step-repition-limit (from problem type)
then path-state = OK

# confidence modeling - t7p356rC1-2

Rule C1:
if answer was low-confidence (either agree or disagree)
then decrement conf-value
Rule C2:
if answer was high-confidence (either agree or disagree)
then increment conf-value

Rule C3 -- decrease modeled confidence on help request:
if answer was help request
then decrement conf-value

Rule C4:
if problem-state = succeeded
and without help
then increment conf-value by large-conf-inc
Rule C5:
if problem-state = succeeded
and with help
then increment conf-value
Rule C6:
if problem-state = failed
and without help
then decrement conf-value
Rule C7:
if problem-state = failed
and with help
then decrement conf-value by large-conf-dec

# effort modeling - t8p357 (non-rule)

if path-state = lost
then effort-value = "medium" + 1
if problem-state = succeeded
then effort-value += 2
if help was asked for
then effort-value += 1

# independence modelling - t9p358rI1-I4

Rule I1:
if help-state = suggesting
then decrement indep-value

Rule I2:
if help-state = providing
and detail = general
then decrement indep-value

Rule I3:
if help-state = providing
and detail = specific
then decrement indep-value by large-indep-dec

Rule I4:
if help-state = rejected
then increment indep-value by large-indep-inc

# domain-based planner rules - t10p359rD1-D7

Rule D1:
if problem-state = succeeded
then provide right assessment; suggest harder problem
Rule D2:
if problem-state = failed
then provide wrong assessment; suggest same-diff problem
Rule D3:
if problem-state = given-up
then suggest same-diff problem
Rule D4:
if problem-state = rejected
then suggest same-diff problem

Rule D5:
if help-state = requested
then provide help
Rule D6:
if help-state = rejected
then help not-needed

Rule D7:
if path-state = lost
then provide help

# motivational planner rules - t11p360rM1-M20

Rule M1:
if conf-value < conf-threshold
then increase confidence # when and how is this reset?
Rule M2:
if effort-value < "medium"
then increase effort
Rule M3:
if effort-value > "medium"
then maintain effort
Rule M4:
if help-state = rejected
then respect control
Rule M5:
if problem-state = given-up # "above give-up-lim"
then respect control
Rule M6:
if indep-value < indep-threshold
and not increase confidence
then increase control
Rule M7:
if problem-state = succeeded
and increase confidence
then increase experience success
Rule M8:
if problem-state = failed
and increase confidence
then facilitate success
Rule M9:
if problem-state = given-up
and increase effort (M2)
and not increase confidence
and not respect control
then encourage effort
Rule M10:
if problem-state = given-up
and increase confidence
and not respect control
then facilitate success
Rule M11:
if problem-state = succeeded
and increase effort
then stimulate challenge
Rule M12:
if stimulate challence (M11)
and increase confidence (M1)
then emphasise promotion
Rule M13:
if problem-state = failed
and increase effort
and not increase confidence
then stimulate curiosity
Rule M14:
if perf-value = successful
and facilitate success
and increase effort
then remind success
Rule M15:
if path-state = lost
and increase control
then avoid intervention
Rule M16:
if help-state = requested
and increase control
then encourage independence
Rule M17:
if encourage independence
then avoid intervention
Rule M18:
if help-state = rejected
and help-skip-next = no (needs to be fitted to "skip next help" or whatever)
and respect control
then avoid next intervention
Rule M19:
if help-state != rejected
and help-skip-next = yes (ditto)
then avoid intervention
Rule M20:
if help-state != requested
and not increase confidence
and not stimulate curiosity
then share control

# negotiated actions - t12p363-rN1-N7

Rule N1
action: suggest harder problem
tactics: increase success; not stimulate challenge
negotiated: suggest problem, similar difficulty

Rule N2
action: suggest harder problem
tactic: stimulate challenge; not increase confidence
negotiated: suggest much-harder problem

Rule N3
action: suggest harder problem
tactic: emphasise promotion
negotiated: suggest harder problem; provide level-promotion comment

Rule N4
action: provide wrong assessment; suggest same-diff problem
tactic: emphasize promotion
negotiated: suggest harder problem; provide level-promotion comment

Rule N5 -- requires suprise result
action: provide wrong assessment
tactic: stimulate curiosity (M13)
negotiated: provide suprise result help

Rule N6
action: provide right assessment
tactic: maintain effort
negotiated: provide right assessment; provide praise performance comment

Rule N7
action: provide wrong assessment
tactic: maintain effort
negotiated: provide wrong assessment; provide praise performance comment

# negotiated actions (cont) - t12p364rN8-N15

Rule N8
action: suggest problem; not provide assessment
tactic: facilitate success; not respect control
negotiated: provide help

Rule N9
action: suggest problem; not provide assessment
tactic: encourage effort
negotiated: provide trying-harder comment; suggest help

Rule N10
action: ---
tactic: remind successes
negotiated: provide previous-successes comment

Rule N11
action: provide help
tactic: avoid intervention
negotiated: skip help

Rule N12
action: ---
tactic: encourage independence
negotiated: provide encourage-indep comment

Rule N13
action: provide general help
tactic: increase confidence
negotiated: provide specific help

Rule N14
action: provide help
tactic: share control
negotiated: suggest help

Rule N15
action: help not-needed
tactic: avoid next intervention
negotiated: skip next-help
</pre>

gift

2010-02-12T00:42:45Z

JSalsman: /* Possible choices */ unwrap

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || set of questions which help answer this question
|-
| // helped-by: title[,...] || set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || set of relations to other questions by relative difficulty
|-
| // general-help: text || optional general help
|-
| // specific-help: text || optional specific help
|-
| \// || Two forward slashes
|-
| // review-state: text || summary of accuracy review status
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // numeric quantity for relative difficulty
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // summary of review status

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [http://web.archive.org/web/20050220153210/www.bovik.org/idas/dsd-tutor-rules.txt rules] and [http://web.archive.org/web/20060517223928/bovik.org/idas/dsd-tutor-schema.txt this schema] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
*http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-02-12T00:42:03Z

JSalsman: yeah

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || set of questions which help answer this question
|-
| // helped-by: title[,...] || set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || set of relations to other questions by relative difficulty
|-
| // general-help: text || optional general help
|-
| // specific-help: text || optional specific help
|-
| \// || Two forward slashes
|-
| // review-state: text || summary of accuracy review status
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // summary of review status

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [http://web.archive.org/web/20050220153210/www.bovik.org/idas/dsd-tutor-rules.txt rules] and [http://web.archive.org/web/20060517223928/bovik.org/idas/dsd-tutor-schema.txt this schema] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
*http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-02-11T18:39:59Z

JSalsman: /* Possible choices */

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || set of questions which help answer this question
|-
| // helped-by: title[,...] || set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || set of relations to other questions by relative difficulty
|-
| // general-help: text || optional general help
|-
| // specific-help: text || optional specific help
|-
| \// || Two forward slashes
|-
| // review-state: text || summary of accuracy review status
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // summary of review status

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [http://web.archive.org/web/20050220153210/www.bovik.org/idas/dsd-tutor-rules.txt rules] and [http://web.archive.org/web/20060517223928/bovik.org/idas/dsd-tutor-schema.txt this schema] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
*http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-02-11T18:39:40Z

JSalsman: /* Possible choices */ interspersal example

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || set of questions which help answer this question
|-
| // helped-by: title[,...] || set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || set of relations to other questions by relative difficulty
|-
| // general-help: text || optional general help
|-
| // specific-help: text || optional specific help
|-
| \// || Two forward slashes
|-
| // review-state: text || summary of accuracy review status
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this to answer that
::milk-color // title; not sure if comment ok here
// easier-than: sky-color, // this question is easier than those two
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [http://web.archive.org/web/20050220153210/www.bovik.org/idas/dsd-tutor-rules.txt rules] and [http://web.archive.org/web/20060517223928/bovik.org/idas/dsd-tutor-schema.txt this schema] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
*http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-02-11T18:35:38Z

JSalsman: /* Learner adaptation */ table

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for [http://en.wikipedia.org/wiki/Computerized_adaptive_testing computerized adaptive testing] (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

{|
! Symbols !! Use
|-
| // helps-answer: title[, title...] || set of questions which help answer this question
|-
| // helped-by: title[,...] || set of questions which answering this question helps answer
|-
| // easier-than: title[%n%][,...] // harder-than: title[%n%][,...] || set of relations to other questions by relative difficulty
|-
| // general-help: text || optional general help
|-
| // specific-help: text || optional specific help
|-
| \// || Two forward slashes
|-
| // review-state: text || summary of accuracy review status
|}

Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this
// easier-than: sky-color, // this question is easier
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

These field keywords and formats can be used:

// helps-answer: title[, title...]
// helped-by: title[,...]
// easier-than: title[%n%][,...]
// harder-than: title[%n%][,...]
// general-help: text // already generalfeedback?
// specific-help: text
// review-state: text

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [http://web.archive.org/web/20050220153210/www.bovik.org/idas/dsd-tutor-rules.txt rules] and [http://web.archive.org/web/20060517223928/bovik.org/idas/dsd-tutor-schema.txt this schema] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
*http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-02-11T18:29:03Z

JSalsman: comment

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax 

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this
// easier-than: sky-color, // this question is easier
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

These field keywords and formats can be used:

// helps-answer: title[, title...]
// helped-by: title[,...]
// easier-than: title[%n%][,...]
// harder-than: title[%n%][,...]
// general-help: text // already generalfeedback?
// specific-help: text
// review-state: text

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [http://web.archive.org/web/20050220153210/www.bovik.org/idas/dsd-tutor-rules.txt rules] and [http://web.archive.org/web/20060517223928/bovik.org/idas/dsd-tutor-schema.txt this schema] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
*http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-02-11T17:06:26Z

JSalsman: bit.ly/giftex

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax (this page) or http://bit.ly/giftex (extension proposals)

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this
// easier-than: sky-color, // this question is easier
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

These field keywords and formats can be used:

// helps-answer: title[, title...]
// helped-by: title[,...]
// easier-than: title[%n%][,...]
// harder-than: title[%n%][,...]
// general-help: text // already generalfeedback?
// specific-help: text
// review-state: text

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [http://web.archive.org/web/20050220153210/www.bovik.org/idas/dsd-tutor-rules.txt rules] and [http://web.archive.org/web/20060517223928/bovik.org/idas/dsd-tutor-schema.txt this schema] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
*http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-02-11T02:30:40Z

JSalsman: /* Possible choices */ unbunch links

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this
// easier-than: sky-color, // this question is easier
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

These field keywords and formats can be used:

// helps-answer: title[, title...]
// helped-by: title[,...]
// easier-than: title[%n%][,...]
// harder-than: title[%n%][,...]
// general-help: text // already generalfeedback?
// specific-help: text
// review-state: text

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect"] Wikipedia article, [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [http://web.archive.org/web/20050220153210/www.bovik.org/idas/dsd-tutor-rules.txt rules] and [http://web.archive.org/web/20060517223928/bovik.org/idas/dsd-tutor-schema.txt this schema] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
*http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-02-11T01:52:24Z

JSalsman: /* See also */ sort

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this
// easier-than: sky-color, // this question is easier
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

These field keywords and formats can be used:

// helps-answer: title[, title...]
// helped-by: title[,...]
// easier-than: title[%n%][,...]
// harder-than: title[%n%][,...]
// general-help: text // already generalfeedback?
// specific-help: text
// review-state: text

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect" Wikipedia article,] [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [http://web.archive.org/web/20050220153210/www.bovik.org/idas/dsd-tutor-rules.txt rules] and [http://web.archive.org/web/20060517223928/bovik.org/idas/dsd-tutor-schema.txt this schema] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===

*http://www.mediawiki.org/wiki/Extension:Quiz
**[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki Quiz extension talk: GIFT format and Quiz tables?]
*http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]

*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)

*[[picoformats]]

gift

2010-02-11T01:25:41Z

JSalsman: /* See also */ +2

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this
// easier-than: sky-color, // this question is easier
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

These field keywords and formats can be used:

// helps-answer: title[, title...]
// helped-by: title[,...]
// easier-than: title[%n%][,...]
// harder-than: title[%n%][,...]
// general-help: text // already generalfeedback?
// specific-help: text
// review-state: text

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect" Wikipedia article,] [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [http://web.archive.org/web/20050220153210/www.bovik.org/idas/dsd-tutor-rules.txt rules] and [http://web.archive.org/web/20060517223928/bovik.org/idas/dsd-tutor-schema.txt this schema] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]
*[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki:Extension talk:Quiz#GIFT format and Quiz tables?]
*http://en.wikiversity.org/wiki/Help:Quiz
**[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]
*http://www.mediawiki.org/wiki/Extension:Quiz

gift

2010-02-11T01:23:30Z

JSalsman: /* Possible choices */ seperated by blank lines

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions as long as blank lines don't intervene. For example:

// helps-answer: latte-color // helps if you know this
// easier-than: sky-color, // this question is easier
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

These field keywords and formats can be used:

// helps-answer: title[, title...]
// helped-by: title[,...]
// easier-than: title[%n%][,...]
// harder-than: title[%n%][,...]
// general-help: text // already generalfeedback?
// specific-help: text
// review-state: text

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect" Wikipedia article,] [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [http://web.archive.org/web/20050220153210/www.bovik.org/idas/dsd-tutor-rules.txt rules] and [http://web.archive.org/web/20060517223928/bovik.org/idas/dsd-tutor-schema.txt this schema] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]
*[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki:Extension talk:Quiz#GIFT format and Quiz tables?]
*[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]

gift

2010-02-11T01:21:52Z

JSalsman: /* See also */ Moodle is more high-stakes

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions. For example:

// helps-answer: latte-color // helps if you know this
// easier-than: sky-color, // this question is easier
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

These field keywords and formats can be used:

// helps-answer: title[, title...]
// helped-by: title[,...]
// easier-than: title[%n%][,...]
// harder-than: title[%n%][,...]
// general-help: text // already generalfeedback?
// specific-help: text
// review-state: text

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect" Wikipedia article,] [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [http://web.archive.org/web/20050220153210/www.bovik.org/idas/dsd-tutor-rules.txt rules] and [http://web.archive.org/web/20060517223928/bovik.org/idas/dsd-tutor-schema.txt this schema] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]
*[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki:Extension talk:Quiz#GIFT format and Quiz tables?]
*[http://en.wikiversity.org/wiki/Help:Quiz/Wikiversity_compared_to_Moodle Wikiversity compared to Moodle]

gift

2010-02-11T01:04:51Z

JSalsman: /* See also */ fix link

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions. For example:

// helps-answer: latte-color // helps if you know this
// easier-than: sky-color, // this question is easier
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

These field keywords and formats can be used:

// helps-answer: title[, title...]
// helped-by: title[,...]
// easier-than: title[%n%][,...]
// harder-than: title[%n%][,...]
// general-help: text // already generalfeedback?
// specific-help: text
// review-state: text

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect" Wikipedia article,] [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [http://web.archive.org/web/20050220153210/www.bovik.org/idas/dsd-tutor-rules.txt rules] and [http://web.archive.org/web/20060517223928/bovik.org/idas/dsd-tutor-schema.txt this schema] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]
*[http://www.mediawiki.org/wiki/Extension_talk:Quiz#GIFT_format_and_Quiz_tables.3F Mediawiki:Extension talk:Quiz#GIFT format and Quiz tables?]

gift

2010-02-11T01:03:52Z

JSalsman: /* See also */ ok?

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions. For example:

// helps-answer: latte-color // helps if you know this
// easier-than: sky-color, // this question is easier
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

These field keywords and formats can be used:

// helps-answer: title[, title...]
// helped-by: title[,...]
// easier-than: title[%n%][,...]
// harder-than: title[%n%][,...]
// general-help: text // already generalfeedback?
// specific-help: text
// review-state: text

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect" Wikipedia article,] [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [http://web.archive.org/web/20050220153210/www.bovik.org/idas/dsd-tutor-rules.txt rules] and [http://web.archive.org/web/20060517223928/bovik.org/idas/dsd-tutor-schema.txt this schema] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]
*[[mw:Extension talk:Quiz#GIFT format and Quiz tables?]]

gift

2010-02-10T22:27:53Z

JSalsman: /* Possible choices */

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special hyphenated keywords with colons can be used preceding or following the questions. For example:

// helps-answer: latte-color // helps if you know this
// easier-than: sky-color, // this question is easier
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

These field keywords and formats can be used:

// helps-answer: title[, title...]
// helped-by: title[,...]
// easier-than: title[%n%][,...]
// harder-than: title[%n%][,...]
// general-help: text // already generalfeedback?
// specific-help: text
// review-state: text

That would apparently cover the stated extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

There is more we may want to accomplish noted in the [http://en.wikipedia.org/wiki/Spacing_effect "Spacing effect" Wikipedia article,] [http://en.wikipedia.org/wiki/Bloom%27s_Taxonomy#Cognitive "Bloom's cognitive taxonomy,"] suggesting sub-categories, and del Soldato and du Boulay's original [http://web.archive.org/web/20050220153210/www.bovik.org/idas/dsd-tutor-rules.txt rules] and [http://web.archive.org/web/20060517223928/bovik.org/idas/dsd-tutor-schema.txt this schema] based on them and the article they appeared in. But the primary goals listed here are likely satisfied with the detail shown above.

; Please don't worry about posting character counts here

I asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 22:27, 10 February 2010 (UTC)

===See also===
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]

gift

2010-02-10T22:19:18Z

JSalsman: /* Possible choices */ really no question about it at this point

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Comments with special keywords can be used following the questions. For example:

// helps-answer: latte-color // helps if you know this
// easier-than: sky-color, // this question is easier
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

Placing comments before or after should be fine, as long as there are no intervening blank lines. We could use these field keywords:

// helps-answer: title[, title...]
// helped-by: title[,...]
// easier-than: title[%n%][,...]
// harder-than: title[%n%][,...]
// general-help: text // already generalfeedback?
// specific-help: text
// review-state: text

That would apparently cover all the extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

; Please don't worry about posting character counts here

I've asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 05:23, 9 February 2010 (UTC)

===See also===
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]

gift

2010-02-10T22:18:54Z

JSalsman: /* Possible choices */ before or after should be fine, as long as no blank lines are intervening

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Perhaps comments with special keywords can be used following the questions. For example:

// helps-answer: latte-color // helps if you know this
// easier-than: sky-color, // this question is easier
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
}
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

Placing comments before or after should be fine, as long as there are no intervening blank lines. We could use these field keywords:

// helps-answer: title[, title...]
// helped-by: title[,...]
// easier-than: title[%n%][,...]
// harder-than: title[%n%][,...]
// general-help: text // already generalfeedback?
// specific-help: text
// review-state: text

That would apparently cover all the extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

; Please don't worry about posting character counts here

I've asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 05:23, 9 February 2010 (UTC)

===See also===
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]

gift

2010-02-10T22:17:22Z

JSalsman: /* Case insensitive */ even in general chemistry case sensitivity might be a bad idea, but there are some ambiguities somewhere

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in some chemical formulae like proteins) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Perhaps comments with special keywords can be used following the questions. For example:

::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
}
// helps-answer: latte-color // helps if you know this
// easier-than: sky-color, // this question is easier
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

We could use these field keywords:

// helps-answer: title[, title...]
// helped-by: title[,...]
// easier-than: title[%n%][,...]
// harder-than: title[%n%][,...]
// general-help: text // already generalfeedback?
// specific-help: text
// review-state: text

That would apparently cover all the extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

; Please don't worry about posting character counts here

I've asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 05:23, 9 February 2010 (UTC)

===See also===
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]

gift

2010-02-09T05:32:50Z

JSalsman: /* Please post character counts here */

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in chemistry formulae) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Perhaps comments with special keywords can be used following the questions. For example:

::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
}
// helps-answer: latte-color // helps if you know this
// easier-than: sky-color, // this question is easier
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

We could use these field keywords:

// helps-answer: title[, title...]
// helped-by: title[,...]
// easier-than: title[%n%][,...]
// harder-than: title[%n%][,...]
// general-help: text // already generalfeedback?
// specific-help: text
// review-state: text

That would apparently cover all the extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

; Please don't worry about posting character counts here

I've asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 05:23, 9 February 2010 (UTC)

===See also===
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]

gift

2010-02-09T05:23:42Z

JSalsman: /* Possible choices */

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in chemistry formulae) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Perhaps comments with special keywords can be used following the questions. For example:

::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
}
// helps-answer: latte-color // helps if you know this
// easier-than: sky-color, // this question is easier
// shroedinger-eqn%1% // need a numeric quantity for relative difficulty -- syntax ok?
// general-help: Think about full milk bottles. // general help
// specific-help: It's the same color as chalk. // specific help
// review-state: proposed // not sure about this ($proposed or *...?)

We could use these field keywords:

// helps-answer: title[, title...]
// helped-by: title[,...]
// easier-than: title[%n%][,...]
// harder-than: title[%n%][,...]
// general-help: text // already generalfeedback?
// specific-help: text
// review-state: text

That would apparently cover all the extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice, because some of the metadata grows every time a question is answered.

===== Please post character counts here =====

I've asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please never mind. Thanks anyway! [[User:JSalsman|JSalsman]] 05:23, 9 February 2010 (UTC)

===See also===
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]

gift

2010-02-06T15:43:48Z

JSalsman: /* = Learner adaptation */ =

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in chemistry formulae) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ====

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Perhaps more special symbols ("control characters" in some GIFT specifications) can be used inside {}s. For example:

::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
@helps-answer: latte-color // helps if you know this
@easier-than: sky-color, // this question is easier
shroedinger-eqn%1% // need a numeric quantity for relative difficulty
? Think about full milk bottles. // general help (maybe @help: ...?)
?? It's the same color as chalk. // specific help (@specific-help: ...?)
@state: proposed // not sure about this ($proposed or *...?)
}

That would have a possible advantage of being tightly syntacticly bound to the answer, but the disadvantage that it would introduce additional special characters in the answer. That would probably be a lot better than introducing them in the question text. There is a backward-compatibility advantage to only introducing one new special "control" character, such as @, because characters such as ?, $, and * are already possibly in answer codes somewhere the format is being used. So we could have:

@helps-answer: title[, title...]
@helped-by: title[,...]
@easier-than: title[%n%][,...]
@harder-than: title[%n%][,...]
@help: text
@specific-help: text
@state: text

That would apparently cover all the extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice.

Any instance of the chosen character not followed by a recognized keyword should be treated as if it were not a special character.

===== Please post character counts here =====

I've asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please edit this section and list your counts below. Thank you! [[User:JSalsman|JSalsman]] 14:22, 6 February 2010 (UTC)

===See also===
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]

gift

2010-02-06T15:43:25Z

JSalsman: /* Extensions for learner adaptation */ subhead

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in chemistry formulae) with:

<code>
$question->usecase = 1;
</code>

=== Extensions ===
==== Learner adaptation ===

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Perhaps more special symbols ("control characters" in some GIFT specifications) can be used inside {}s. For example:

::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
@helps-answer: latte-color // helps if you know this
@easier-than: sky-color, // this question is easier
shroedinger-eqn%1% // need a numeric quantity for relative difficulty
? Think about full milk bottles. // general help (maybe @help: ...?)
?? It's the same color as chalk. // specific help (@specific-help: ...?)
@state: proposed // not sure about this ($proposed or *...?)
}

That would have a possible advantage of being tightly syntacticly bound to the answer, but the disadvantage that it would introduce additional special characters in the answer. That would probably be a lot better than introducing them in the question text. There is a backward-compatibility advantage to only introducing one new special "control" character, such as @, because characters such as ?, $, and * are already possibly in answer codes somewhere the format is being used. So we could have:

@helps-answer: title[, title...]
@helped-by: title[,...]
@easier-than: title[%n%][,...]
@harder-than: title[%n%][,...]
@help: text
@specific-help: text
@state: text

That would apparently cover all the extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice.

Any instance of the chosen character not followed by a recognized keyword should be treated as if it were not a special character.

===== Please post character counts here =====

I've asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please edit this section and list your counts below. Thank you! [[User:JSalsman|JSalsman]] 14:22, 6 February 2010 (UTC)

===See also===
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]

gift

2010-02-06T15:37:05Z

JSalsman: /* Please post character counts here */

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in chemistry formulae) with:

<code>
$question->usecase = 1;
</code>

=== Extensions for learner adaptation ===

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Perhaps more special symbols ("control characters" in some GIFT specifications) can be used inside {}s. For example:

::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
@helps-answer: latte-color // helps if you know this
@easier-than: sky-color, // this question is easier
shroedinger-eqn%1% // need a numeric quantity for relative difficulty
? Think about full milk bottles. // general help (maybe @help: ...?)
?? It's the same color as chalk. // specific help (@specific-help: ...?)
@state: proposed // not sure about this ($proposed or *...?)
}

That would have a possible advantage of being tightly syntacticly bound to the answer, but the disadvantage that it would introduce additional special characters in the answer. That would probably be a lot better than introducing them in the question text. There is a backward-compatibility advantage to only introducing one new special "control" character, such as @, because characters such as ?, $, and * are already possibly in answer codes somewhere the format is being used. So we could have:

@helps-answer: title[, title...]
@helped-by: title[,...]
@easier-than: title[%n%][,...]
@harder-than: title[%n%][,...]
@help: text
@specific-help: text
@state: text

That would apparently cover all the extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice.

Any instance of the chosen character not followed by a recognized keyword should be treated as if it were not a special character.

===== Please post character counts here =====

I've asked for a count of the characters @, !, $, *, ;, and _ in {answer specifications} at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please edit this section and list your counts below. Thank you! [[User:JSalsman|JSalsman]] 14:22, 6 February 2010 (UTC)

===See also===
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]

gift

2010-02-06T14:24:14Z

JSalsman: /* See also */

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in chemistry formulae) with:

<code>
$question->usecase = 1;
</code>

=== Extensions for learner adaptation ===

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Perhaps more special symbols ("control characters" in some GIFT specifications) can be used inside {}s. For example:

::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
@helps-answer: latte-color // helps if you know this
@easier-than: sky-color, // this question is easier
shroedinger-eqn%1% // need a numeric quantity for relative difficulty
? Think about full milk bottles. // general help (maybe @help: ...?)
?? It's the same color as chalk. // specific help (@specific-help: ...?)
@state: proposed // not sure about this ($proposed or *...?)
}

That would have a possible advantage of being tightly syntacticly bound to the answer, but the disadvantage that it would introduce additional special characters in the answer. That would probably be a lot better than introducing them in the question text. There is a backward-compatibility advantage to only introducing one new special "control" character, such as @, because characters such as ?, $, and * are already possibly in answer codes somewhere the format is being used. So we could have:

@helps-answer: title[, title...]
@helped-by: title[,...]
@easier-than: title[%n%][,...]
@harder-than: title[%n%][,...]
@help: text
@specific-help: text
@state: text

That would apparently cover all the extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice.

Any instance of the chosen character not followed by a recognized keyword should be treated as if it were not a special character.

===== Please post character counts here =====

I've asked for a count of @, !, $, *, ;, and _ at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please edit this section and list your counts below. Thank you! [[User:JSalsman|JSalsman]] 14:22, 6 February 2010 (UTC)

===See also===
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]

gift

2010-02-06T14:22:33Z

JSalsman: /* Possible choices */

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in chemistry formulae) with:

<code>
$question->usecase = 1;
</code>

=== Extensions for learner adaptation ===

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Perhaps more special symbols ("control characters" in some GIFT specifications) can be used inside {}s. For example:

::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
@helps-answer: latte-color // helps if you know this
@easier-than: sky-color, // this question is easier
shroedinger-eqn%1% // need a numeric quantity for relative difficulty
? Think about full milk bottles. // general help (maybe @help: ...?)
?? It's the same color as chalk. // specific help (@specific-help: ...?)
@state: proposed // not sure about this ($proposed or *...?)
}

That would have a possible advantage of being tightly syntacticly bound to the answer, but the disadvantage that it would introduce additional special characters in the answer. That would probably be a lot better than introducing them in the question text. There is a backward-compatibility advantage to only introducing one new special "control" character, such as @, because characters such as ?, $, and * are already possibly in answer codes somewhere the format is being used. So we could have:

@helps-answer: title[, title...]
@helped-by: title[,...]
@easier-than: title[%n%][,...]
@harder-than: title[%n%][,...]
@help: text
@specific-help: text
@state: text

That would apparently cover all the extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified. Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. Maybe that should be specified but discouraged in practice.

Any instance of the chosen character not followed by a recognized keyword should be treated as if it were not a special character.

===== Please post character counts here =====

I've asked for a count of @, !, $, *, ;, and _ at http://moodle.org/mod/forum/discuss.php?d=143213 -- if you are responding, please edit this section and list your counts below. Thank you! [[User:JSalsman|JSalsman]] 14:22, 6 February 2010 (UTC)

==See also==
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]

gift

2010-02-06T14:21:12Z

JSalsman: /* Possible choices */

__TOC__

<entry-title>GIFT Syntax</entry-title>
;short URL
:http://bit.ly/giftax

The [http://docs.moodle.org/en/GIFT_format GIFT picoformat] allows writing multiple-choice, true-false, fill-in-the-blank (also called short answer or missing word), matching, and numerical quiz questions in a simple text format.

The GPLed [http://moodle.org/ Moodle] Course/Learning Management System can import and export questions in the GIFT format.

=== Format ===

GIFT quiz questions must be encoded in utf-8 characters, and are delimited by blank lines. A question may be preceded by a title inside a pair of double colons and must include or be followed by an answer specification in curly braces. Examples are shown below.

{|
! Symbols !! Use
|-
| // text || Comment until end of line (optional)
|-
| ::title:: || Question title (optional)
|-
| text || Question text (becomes title if no title specified)
|-
| { || Start answer(s) -- without any answers, text is a description of following questions
|-
| {T} or {F} || True or False answer; also {TRUE} and {FALSE}
|-
| { ... =right ... } || Correct answer for multiple choice, (multiple answer?) or fill-in-the-blank
|-
| { ... ~wrong ... } || Incorrect answer for multiple choice or multiple answer
|-
| { ... =item -> match ... } || Answer for matching questions
|-
| #feedback text || Answer feedback for preceding multiple, fill-in-the-blank, or numeric answers
|-
| {# || Start numeric answer(s)
|-
| answer:tolerance || Numeric answer accepted within ± tolerance range
|-
| low..high || Lower and upper range values of accepted numeric answer
|-
| =%n%answer:tolerance || n percent credit for one of multiple numeric ranges within tolerance from answer
|-
| } || End answer(s); additional text may follow for fill-in-the-blank
|-
| \character || Backslash escapes the special meaning of ~, =, #, {, }, and :
|-
| \n || Places a newline in question text -- blank lines delimit questions
|}

==== Examples ====

// true-false
::Q1:: 1+1=2 {T} // not sure if comments are okay here

// multiple choice with specific feedback
::Q2:: What's between orange and green in the spectrum?
{=yellow # correct! ~red # wrong, it's yellow ~blue # wrong, it's yellow}

// fill-in-the-blank
::Q3:: Two plus {=two =2} equals four.

// matching
::Q4:: Which animal eats which food? { =cat -> cat food =dog -> dog food }

// math range question -- note: {#1..5} is the same range
::Q5:: What is a number from 1 to 5? {#3:2}

// multiple numeric answers with partial credit and feedback
::Q7:: When was Ulysses S. Grant born? {#
=1822:0 # Correct! You get full credit.
=%50%1822:2 # He was born in 1822. You get half credit for being close.
}

// essay
::Q8:: How are you? {}

// alternate layout
::Title
:: Question {
=Correct answer 1
=Correct answer 2
~Wrong answer 1
#Response to wrong answer 1
~Wrong answer 2
#Response to wrong answer 2
}

:''Note: the table and examples above were adapted from and then migrated back to the GPL-licensed Moodle site, not copied from there.''

=== Categories ===

Question categories may be specified by preceding them with

<code>
$CATEGORY: path/name
</code>

with a blank line before and after. That sets the following questions' category name or pathname.

=== Case insensitive ===

Alphabetic case-sensitive comparison is off by default, but may be enabled for short answer (fill-in-the-blank) questions that need them (usually a very unlikely occurrence, except, e.g., in chemistry formulae) with:

<code>
$question->usecase = 1;
</code>

=== Extensions for learner adaptation ===

Still to be done to extend the format for learner adaptivity (per, for example, del Soldato, T. & du Boulay, B. (1995) "Implementation of Motivational Tactics in Tutoring Systems," ''Journal of Artificial Intelligence in Education,'' '''6'''(4): 337-78) is to add optional prerequisite and relative difficulty links to other questions (titles can be used) and optional question help text at two levels of specificity:

* relations to other questions
** set of questions which help answer this question
** set of questions which answering this question helps answer
(Can some of the directed graph of which questions assist in the answering of other questions be derived from categorization or must it be stored completely explicitly?)
* set of relations to other questions by relative difficulty; for each:
** another question
** more or less difficult, and how much
* general help (optional)
* specific help (optional)

==== Accuracy review ====

It would also help to be able to specify the state of the question in a [http://strategy.wikimedia.org/wiki/Proposal:Develop_systems_for_accuracy_review review system]:

* incomplete
** (ungrammatical, ambiguous, non-sequitur, implies false assumption, circular, dependent on future circumstance or decision, etc.)
* open
** hypothetical (also open -- but less so?)
** answered ("proposed"?)
*** reviewed
**** complete (passed review)
***** asked
****** scored
******* challenged
******** assessed
**** rejected (failed review or assessment)

[http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content (source)]

==== Possible choices ====

Perhaps more special symbols ("control characters" in some GIFT specifications) can be used inside {}s. For example:

::milk-color // title; not sure if comment ok here
:: What color is milk? { // question
=white // answer
@helps-answer: latte-color // helps if you know this
@easier-than: sky-color, // this question is easier
shroedinger-eqn%1% // need a numeric quantity for relative difficulty
? Think about full milk bottles. // general help (maybe @help: ...?)
?? It's the same color as chalk. // specific help (@specific-help: ...?)
@state: proposed // not sure about this ($proposed or *...?)
}

That would have a possible advantage of being tightly syntacticly bound to the answer, but the disadvantage that it would introduce additional special characters in the answer. That would probably be a lot better than introducing them in the question text.

There is a backward-compatibility advantage to only introducing one new special "control" character, such as @, because characters such as ?, $, and * are already possibly in answer codes somewhere the format is being used. So we could have:

@helps-answer: title[, title...]
@helped-by: title[,...]
@easier-than: title[%n%][,...]
@harder-than: title[%n%][,...]
@help: text
@specific-help: text
@state: text

That would apparently cover all the extension requirements. The reflexive links (helps/helped, easier/harder) can be implicit where they aren't specified.

Not sure whether it's a good idea to specify [http://strategy.wikimedia.org/wiki/Proposal_talk:Assessment_content#assessment_item_fields summary statistics from question fields] as they might exist in a database. But if most of the database needs to be serialized in human-readable format, why not? One reason why not is that doing so could detract from the readability, especially since the answer statistics grow each time the question is answered. Maybe that should be specified but discouraged in practice?

I've asked for a count of @, !, $, *, ;, and _ at http://moodle.org/mod/forum/discuss.php?d=143213 Any instance of the chosen character not followed by a recognized keyword should be treated as if it were not a special character.

===== Please post character counts here =====

==See also==
*[http://buypct.com/gift_reference.pdf 5-page reference] (PDF)
*[[picoformats]]