<div dir="ltr">If you allow structure in all the international strings it will be lost if you then move it to a Lifecycle field that does not support structure. However, this may not be a concern for you.</div><br><div class="gmail_quote"><div class="gmail_attr" dir="ltr">On Mon, Feb 3, 2020 at 11:21 AM Wackerow, Joachim <<a href="mailto:Joachim.Wackerow@gesis.org">Joachim.Wackerow@gesis.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
<div lang="DE">
<div class="gmail-m_8823045419982324518WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">Where exactly do you see interoperability issues with the suggested approach and Lifecycle and Codebook? I was not aware of any.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">Cannot any DDI 4 string attribute be mapped to the appropriate items in the other specs?<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">Achim<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-family:"Tahoma","sans-serif";font-size:10pt">From:</span></b><span lang="EN-US" style="font-family:"Tahoma","sans-serif";font-size:10pt"> Wendy Thomas [mailto:<a href="mailto:wlt@umn.edu" target="_blank">wlt@umn.edu</a>]
<br>
<b>Sent:</b> Monday, February 3, 2020 18:05<br>
<b>To:</b> Wackerow, Joachim<br>
<b>Cc:</b> DDI - Structural Reform Group<br>
<b>Subject:</b> Re: [DDI-SRG] [MRT] Model cleanup: string definitions<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">As a general question...particularly in terms of string content and date is there any concern for interoperability with Lifecycle and Codebook? There were reasons certain fields were not allowed to use structure. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Mon, Feb 3, 2020 at 6:40 AM Wackerow, Joachim <<a href="mailto:Joachim.Wackerow@gesis.org" target="_blank">Joachim.Wackerow@gesis.org</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-width:medium medium medium 1pt;border-style:none none none solid;border-color:currentColor currentColor currentColor rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-right:0cm;margin-left:4.8pt">
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">The current approach of string types seems to be too complicated. The structured string types could be folded into the regular ones. Furthermore, there are some
inconsistencies.</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">Diagrams on the current approach and the suggested approach are attached. Side note: XSD data type “date” is now used instead of a special DDI data type for date.</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">Please review the proposal and comment.</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">Achim</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
DDI-SRG mailing list<br>
<a href="mailto:DDI-SRG@icpsr.umich.edu" target="_blank">DDI-SRG@icpsr.umich.edu</a><br>
<a href="http://lists.icpsr.umich.edu/mailman/listinfo/ddi-srg" target="_blank">http://lists.icpsr.umich.edu/mailman/listinfo/ddi-srg</a><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<br>
-- <u></u><u></u></p>
<div>
<div>
<p class="MsoNormal">Wendy L. Thomas Phone: +1 612.624.4389<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Data Access Core Director Fax: +1 612.626.8375<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Minnesota Population Center Email: <a href="mailto:wlt@umn.edu" target="_blank">
wlt@umn.edu</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">University of Minnesota<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">50 Willey Hall<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">225 19th Avenue South<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Minneapolis, MN 55455<u></u><u></u></p>
</div>
</div>
</div>
</div>
_______________________________________________<br>
DDI-SRG mailing list<br>
<a href="mailto:DDI-SRG@icpsr.umich.edu" target="_blank">DDI-SRG@icpsr.umich.edu</a><br>
<a href="http://lists.icpsr.umich.edu/mailman/listinfo/ddi-srg" target="_blank" rel="noreferrer">http://lists.icpsr.umich.edu/mailman/listinfo/ddi-srg</a><br>
</blockquote></div><br clear="all"><br>-- <br><div class="gmail_signature" dir="ltr"><div>Wendy L. Thomas Phone: +1 612.624.4389</div><div>Data Access Core Director Fax: +1 612.626.8375</div><div>Minnesota Population Center Email: <a href="mailto:wlt@umn.edu" target="_blank">wlt@umn.edu</a></div><div>University of Minnesota</div><div>50 Willey Hall</div><div>225 19th Avenue South</div><div>Minneapolis, MN 55455</div></div>