Wikisoba project/JSON specification for version 2: Difference between revisions
(start page on JSON code) |
(fmt) |
||
| Line 20: | Line 20: | ||
<pre>[S(1), S(2), ..., S(N + 1)]</pre> | <pre>[S(1), S(2), ..., S(N + 1)]</pre> | ||
and the S(i) will be strings, | and the S(i) will be strings, possibly null, subject to JSON constraints<ref>I.e. can be Unicode, but with certain characters escaped</ref> and the constraint that S(N + 1) is either null or ends in a terminating punctuation mark.<ref>I.e. ends in . or ? or !.</ref> | ||
==Notes== | ==Notes== | ||
{{reflist}} | {{reflist}} | ||
Revision as of 12:32, 4 November 2014
|
This page is still a draft. Feel free to edit it, and use the talk page to discuss ideas and changes. Remember to add categories and tell people where the page is so others can find it and chip in. |
This is the working page for designing the JSON specification for Wikisoba Mark II.
Working assumption
The JSON for any one "slide" (adopting the term in Mark I) reads as
[configuration array, data array]
The configuration array starts by giving the "slide type", which would be 1 for questions, out of about five types in all, the other types being ways of including supporting material. The array will have about a dozen items, including some the legacy of Moodle export as in the JSON-GIFT sample.
Choice-cloze type
This is to be a versatile question type, including a number of typical multiple choice and missing text (cloze) formats. Its data array will look like
[S-array, T-array]
Here the S-array will be
[S(1), S(2), ..., S(N + 1)]
and the S(i) will be strings, possibly null, subject to JSON constraints[1] and the constraint that S(N + 1) is either null or ends in a terminating punctuation mark.[2]