<div dir="ltr"><div>I am interested in the features of DDI Codebook that make it attractive for use. Some issues could be:</div><div><br></div><div>--optional use of ID's </div><div>--lack of requirements for resolution systems</div><div>--focus on documentation for the end-user (content is intended to be read by a human)</div><div><br></div><div>I'm interested in all the reasons for using DDI-Codebook as a preferred standard. I'd especially like to hear from the producers and users of NESSTAR and the IHSN Microdata Toolkit.</div><div><br></div><div>Why you ask? I'm personally exploring how DDI can keep Codebook alive and relevant to your needs. I need your input. Respond to the list or directly to me. </div><div><br></div><div>I really appreciate your time in thinking about and responding to this inquiry.</div><div><br></div><div>Wendy Thomas</div><div>Chair, Technical Committee<br clear="all"><br>-- <br></div><div class="gmail_signature" data-smartmail="gmail_signature"><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>
</div>