<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
span.EmailStyle18
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:70.85pt 70.85pt 56.7pt 70.85pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Issue 1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">In DDI4 we used an approach from iso11404 to describe the datatype of a missing value enumerated and/or described. As the comments on the issue note, sometimes missing values cannot be described with a list (e.g.
a number greater than 9, or a negative number – both would be infinite lists). Some missing value domains can really be a mixture (e.g. 9 or <0). The description could be verbal or actionable (e.g. a regular expression or a mathematical expression like <0).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Both the description and the enumeration could be extensions of a Concept. What seems to be unclear in concept.png is the explicit use of a description.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Issue 2<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Again looking at what we did in DDI4, what distinguishes a ConceptualVariable from a Concept is the ability to tie together a Concept, a UnitType, and conceptual domains for the measure and sentinel (e.g. missing)
values. The latter might be the difference between the concept of gender and the concept of gender(of people) with only two categories – male and female.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Of course you might say that “dichotomous person gender” is a concept. We have political fights over what gender means that include the conceptual value domain. Describing it with a text string might be more
difficult for software to discover if you were searching for data on persons only.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> ddi-srg-bounces@icpsr.umich.edu <ddi-srg-bounces@icpsr.umich.edu>
<b>On Behalf Of </b>Wackerow, Joachim<br>
<b>Sent:</b> Thursday, March 14, 2019 7:29 AM<br>
<b>To:</b> DDI Structural Reform Working Group. <ddi-srg@icpsr.umich.edu><br>
<b>Cc:</b> Zapilko, Benjamin <Benjamin.Zapilko@gesis.org><br>
<b>Subject:</b> [DDI-SRG] [disco] issues on missing values for numeric response domain and on conceptual variable<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Benjamin Zapilko and I are currently reviewing the open issues of Disco. The goal is to resolve the issues and to prepare Disco finally for publication.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Now I have questions on two issues:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">--<o:p></o:p></p>
<p class="MsoNormal">There is an issue on how to describe missing values for a numeric response domain.<o:p></o:p></p>
<p class="MsoNormal">Details and my comment see at <a href="https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flinked-statistics%2Fdisco-spec%2Fissues%2F130&data=02%7C01%7Clarryhoyle%40ku.edu%7Cbe118e8811aa411a926508d6a878a199%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C1%7C636881633398959083&sdata=nxidinxWSPl9osNol4JuRXznq7Cjmd2TsVkMw0Lypo8%3D&reserved=0">
https://github.com/linked-statistics/disco-spec/issues/130</a>. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">My question:<o:p></o:p></p>
<p class="MsoNormal">Is there really missing something in Disco? I don’t have the impression. But maybe I misunderstood something.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">--<o:p></o:p></p>
<p class="MsoNormal">The other issue is that the conceptual variable of DDI 3.2 does not exist in Disco.
<o:p></o:p></p>
<p class="MsoNormal">The hierarchy is only Variable, RepresentedVariable, skos:Concept.<o:p></o:p></p>
<p class="MsoNormal">Details and my comment see at <a href="https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flinked-statistics%2Fdisco-spec%2Fissues%2F226&data=02%7C01%7Clarryhoyle%40ku.edu%7Cbe118e8811aa411a926508d6a878a199%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C1%7C636881633398969088&sdata=H%2FSrM%2By%2Fo9RSMpzjoxWi6QSz1tf5ruKzgheIXEBmJC4%3D&reserved=0">
https://github.com/linked-statistics/disco-spec/issues/226</a>. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The whole approach of Disco is to focus on a simple subset of DDI Codebook and DDI Lifecycle for Discovery purposes. It is not a 1:1 representation.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">My question:<o:p></o:p></p>
<p class="MsoNormal">Is it really important to be able to search for the ConceptualVariable in addition to Variable, RepresentedVariable, and Concept.<o:p></o:p></p>
<p class="MsoNormal">Is this addition really worth it? This might result in some work for Disco.<o:p></o:p></p>
<p class="MsoNormal">Any thoughts would be helpful.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks<o:p></o:p></p>
<p class="MsoNormal">Achim<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>