Differences

This shows you the differences between two versions of the page.

--- ch:ia:question-info [2026-02-01 09:10] – created - external edit 127.0.0.1
+++ ch:ia:question-info [2026-02-12 15:05] (current) – asimong
@@ Line 2: / Line 2: @@
   * [[ch:ia:]] information architecture
   * [[ch:qs:]] question structuring
+  * [[ch:cr:]] criteria questions
 ====== Question information structure ======
@@ Line 10: / Line 11: @@
 ===== Specification common to all question structures =====
-  * [[ch:fields:QID]] mandatory global question ID: could e.g. be a 32-bit (or longer) integer
+  * [[ch:fields:QID]] mandatory global question ID: could e.g. be a 32-bit (or longer) integer. There could be some attempt to put some meaning into this ID, but it is probably easier simply to assign a random number to it, only ensuring that there are no duplicates.
-  * List of enabling answers, optional.\\ The point here is that some questions only make sense given certain prior answers. Here we need to specify just what those answers are, which will not be language-dependent.
+  * Optional list of enabling question answers. The point here is that some questions only make sense given certain prior answers to particular enabling questions. Here we need to specify just what those questions and answers are, in a way that is not language-dependent. FIXME
-  * [[ch:fields:Language]]-dependent fields: for each language formulated for this question:
+    * Enabling [[ch:fields:QID]]
-    * [[ch:fields:Lang]]: the natural language (1st listed is the default)
+    * Which answers to that one enable this question. How this is coded remains to be defined; but it will not be the same for each kind of question.
-    * [[ch:fields:QTitle]] mandatory question title:\\ a short text field, probably not exceeding 80 characters, that can be transformed into a requirement by prefixing something like “I accept these responses for …” and into an answer by prefixing something like “This is the response I most closely identify with for …”
-    * [[ch:fields:QDesc]] optional question description:\\ a longer text field aiming at explaining any vague terms and clarifying any ambiguity (optional)
   * [[ch:fields:QRelB]]: Boolean, mandatory, whether or not the question is [[ch:t:relational]] or a [[ch:t:property]].
-  * [[ch:fields:QnI]] number of items: for itemised questions, integer between 2 and 10; for non-itemised question = 0 (default)
+  * [[ch:fields:Qni]] number of items: for itemised questions, integer between 2 and 10; for non-itemised question = 0 (default)
-  * [[ch:fields:QStruct]]: mandatory; one of the structures listed on the [[ch:qs:]] page.
+  * [[ch:fields:QStruct]]: mandatory 5-letter code; one of the structures listed on the [[ch:qs:]] page.
-  * [[ch:fields:QLearn]]: link to a page explaining anything here in more detail, with further links to learning resources as may be needed.
+  * [[ch:fields:QLearn]]: (URL) link to a page explaining anything here in more detail, with further links to learning resources as may be needed.
+  * [[ch:fields:QTitle]]: @lang: mandatory question title:\\ a short text field, probably not exceeding 80 characters, that can be transformed into a requirement by prefixing something like “I accept these responses for …” and into an answer by prefixing something like “This is the response I most closely identify with for …”
+  * [[ch:fields:QDesc]]: @lang: optional question description:\\ a longer text field aiming at explaining any vague terms and clarifying any ambiguity (optional)
+  * [[ch:fields:QDetails]]: depending on which structure it is.
-  * [[ch:fields:QDetails]] depend on which structure it is.
+All [[ch:fields:language]]-dependent fields, here marked with "@lang", are held as an array of entries, each one with:
+  * the natural language code;
+  * the field value written in that natural language.
+It is clearly desirable that the languages used in each question should be the same across all fields in that question; though this is not enforced, to allow translation of some fields. This can be checked along with other checks for validity of a question — if the languages are inconsistent, this will throw up a warning.
 ===== Two special cases: place and time =====
 Space / place and time are the two factors that hold a special place of neutrality in science, and they deserve special treatment here.
@@ Line 46: / Line 51: @@
       * in Italy: comune
     * In Europe, we could use [[wp>Nomenclature of Territorial Units for Statistics]] (“NUTS”).
-  * In some cases, people identify with, and like to use, outdated, traditional or old political entities.
+  * In some cases, people identify with, and like to use, outdated, traditional or old political entities. I'm not clear how we should handle these. One option would be to have bespoke place definitions, added to on demand — as there is no way that we could hope to document all of them in advance.
   * Hexagons:
@@ Line 70: / Line 75: @@
 This could be, for instance, derived from a recognisable event that implies a place and a time, e.g.
   * a music festival
-  * any other public event with physical presence
+  * any other public gathering with physical presence
   * a timetabled journey using some public or open transport — that would allow people to have interesting conversations while travelling, with the (moving) place and times being specified by the relevant transport timetable.