Changes between Version 25 and Version 26 of OnyxExportOntology

Timestamp:

01/31/11 11:31:46 (13 years ago)

Author:

jeff.lusted

Comment:

--

OnyxExportOntology

@@ -361 +361 @@
 === Some Principles Discovered ===
 This may be stating the obvious, but perhaps worth actually putting into words.[[BR]]
-We have variables which are question related and variables which are not question related. This is evident from the comments above. I suggest these are fairly good guiding principles:
+We have variables which are question related and variables which are not question related. This is evident from the comments above. I suggest these are two fairly good guiding principles:
 
    1. Variables (bottom leaf ones) which are not question related should be understandable by reading upwards from the bottom leaf until you encounter its top parent variable element. That one branch should contain all the information required to make sense of the variable. You should '''''not''''' have to read adjacent variables to gain critical information.
    1. Variables (bottom leaf ones) which are question related should be understandable by reading upwards from the bottom leaf until you encounter its top question element. That one branch should contain all the information required to make sense of the variable. You should '''''not''''' have to read adjacent variables '''''or''''' questions to gain critical information.
 
-Of course, context information is held above these "top" parents (eg: which questionnaire is being focused upon), but this information applies to everything within one file in any case.[[BR]]
-If we can manage to implement these principles, I suggest we have a reasonable looking ontology tree that would be derivable by machine. The alternative means some human intervention (case by case judgement). There may need to be an element of this, but hopefully minimal at this stage.
+Of course, context information is held above these "top" parents (eg: which questionnaire is being focused upon, or which section etc), but this information applies to a bunch of things within the one file.[[BR]]
+If we can manage to implement these principles, I suggest we will have a reasonable looking onyx ontology tree that would be derivable by machine. The alternative means some human intervention (case by case judgement). There may need to be an element of this, but hopefully minimal at this stage.
 
 === Some Omissions Discovered ===
@@ -521 +521 @@
 In my opinion that is a fairly major omission. As it stands, the information could only be retrieved by looking at an adjacent branch within the onotology.[[BR]]
 
-
+I think we need to structure questions! That is, if a question is described as a "parentQuestion", then it should nest its children. That way any meaningful semantics attached to the label of the parent would be retained in a more reasonable place. At present, these table like questions are the only ones, and that means questions are never more than two deep, which is a relief.[[BR]]
+
+There is a technical problem. There is nothing formally that states this variable - belonging to this question - also has a parent question. As I say, the designer has informally used a structured name (in most instances) to make the connection more explicit. They also happen to immediately follow the parent question in the variables file. I can cobble together a number of self checking ways of detecting this, with an exception report to detail the decisions.[[BR]]
+
+I can implement the above with a couple of hours' work, and then emit examples to show the results. The current set of examples in the attached zip file is ''''not'''' at this level.