<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=utf-8">
<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:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.gmail-m2212265882224371101msolistparagraph, li.gmail-m2212265882224371101msolistparagraph, div.gmail-m2212265882224371101msolistparagraph
{mso-style-name:gmail-m_2212265882224371101msolistparagraph;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:193662835;
mso-list-template-ids:-1436126112;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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="FI" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Thanks for the responses, Wendy.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">It would be helpful for users if DDI Alliance would not need a different kind of version number system from the way DDI
CVG has envisioned the versioning (two-digit for source language CV, three-digit for the target languages where first two digits are the source version number). The separate versioning for languages was based on explicitly expressed user needs. For example,
a language version of a CV might be used in self-report software where depositors of data can describe their studies for the data archive.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">So I wonder if the whole package versioning be managed with some kind of date + internal log combination you mentioned?
Oliver? <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">The change log information for each language can be taken from the elements Version changes and Version notes (if any)
for published CVs, and new added or withdrawn languages from publish or withdraw functions?
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">BTW, would it be possible for users to glean changes only in one or two language versions from the whole package, based
on the language code?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">But there may be user needs or technical issues involved that I cannot envision…. And cannot say how any APIs work.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">The urn recorded for DDI vocabularies in the CESSDA tool in Canonical URIs and Canonical URIs of the version is naturally
the DDI urn. So for citation in DDI Alliance website, Canonical URIs need no changes but URL would be to DDI Alliance website.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">All the best, Taina<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">---<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Taina Jääskeläinen<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">FSD Finnish Social Science Data Archive<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Tampere University, FINLAND<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">e-mail:
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><a href="mailto:taina.jaaskelainen@tuni.fi"><span lang="EN-US" style="color:#0563C1">taina.jaaskelainen@tuni.fi</span></a></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">
| tel: +358 40 190 1444 </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><a href="http://www.fsd.uta.fi/"><span lang="EN-US" style="color:#0563C1">http://www.fsd.uta.fi</span></a></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Wendy Thomas <wlt@umn.edu>
<br>
<b>Sent:</b> 15. maaliskuuta 2019 16:25<br>
<b>To:</b> Taina Jääskeläinen (TAU) <taina.jaaskelainen@tuni.fi><br>
<b>Cc:</b> Sanda Ionescu <sandai@umich.edu>; Wackerow, Joachim <Joachim.Wackerow@gesis.org>; oliver.hopt@gesis.org; DDI Structural Reform Working Group. <ddi-srg@icpsr.umich.edu><br>
<b>Subject:</b> Re: TC: Minutes postes<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">Taina,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Basically we will publish a SKOS instance that contains all languages and therefore have a single version number. How the version number is defined can be up to us. So yes we could say that the major version doesn't change unless the terms
change or there is a significant correction in the intellectual content of a definition. The reference could be to the major version and the user would get the most recent sub-version of that. Some people do sub-versions simply using dates and internal change
log with a date, change, and reason for change. For example: 2019-03-15, Term X definition (en) Aggregaetion changed to Aggregation, Corrected misspelling OR 2019-03-15 Added labels and definitions in German (de), added translation option. In short, it is
up to us to determine the versioning rules and make them clear to users. In making a decision on this the primary issue should be user needs. What changes actually have an impact on the user and the value of stability in the version numbers. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The primary concerns of the call with TC was to make sure we had identified all the technical things that needed to be decided and completed. In particular to identify interaction points with the CESSDA tool, the production pipeline, CV/TC,
and ICPSR/Web page. I will add a line to the minutes that the UNESCO link was simply and example<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If I understood Oliver correctly we could get a merged language output in SKOS from the CESSDA tool. If not it is simply an additional step in the production pipeline to create a merged version from the individual language versions prior
to transformation to other formats and publication. Oliver should have this in his workflow.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I will add a note in the minutes about the UNESCO link being an example of presenting multiple languages.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regarding citation, yes, the DDI publication will provide DDI URN and URL (probably to the SKOS version as the source)...that can be decided. It should line up with the target of the resolved URN. Actually, since we have multiple formats
we will need to consider just WHAT the URN is landing on. This may result in reorganization of the web content. I will note this in the minutes.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks for these clarifications.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Wendy<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Fri, Mar 15, 2019 at 6:13 AM Taina Jääskeläinen (TAU) <<a href="mailto:taina.jaaskelainen@tuni.fi">taina.jaaskelainen@tuni.fi</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hi Wendy,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Reading the minutes, a couple of clarifications, though please note that I may have misunderstood.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Versioning:
</span><o:p></o:p></p>
<p class="gmail-m2212265882224371101msolistparagraph"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-</span><span lang="EN-US" style="font-size:7.0pt;color:#1F497D">
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">If I understood correctly, DDI Alliance will want to version the whole package with all language versions? If there is change in any language versions, the whole
package version changes. I can see this is useful if, for example, the CV is used as a multilingual filter in a search interface.</span><o:p></o:p></p>
<p class="gmail-m2212265882224371101msolistparagraph"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-</span><span lang="EN-US" style="font-size:7.0pt;color:#1F497D">
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The CESSDA tool versions each language separately, though the translations have a three-digit version number linked to the source as the first two digits are the
source version number (i.e. 2.0.2 means the second TL version of the source version 2.0). This is useful for users who are using the CV in their metadata. They are only interested in when and what has been changed in their language version to see what needs
to be changed in their legacy metadata and in their systems where the CV is implemented.
</span><o:p></o:p></p>
<p class="gmail-m2212265882224371101msolistparagraph"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-</span><span lang="EN-US" style="font-size:7.0pt;color:#1F497D">
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The issue maybe to discuss is how to produce the whole package versioning, in the merged SKOS of the CESSDA tool, or in the DDI publication pipeline? But this
is technical, so out of my expertise.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The link to the Unesco vocabularies was just an example of the one typical html display
of multilingual vocabularies. Based on open source publication platform skosmos. It displays the whole language version on the left and term-specific display on the right. In term-specific display all language versions of a specific term are displayed. What
is lacking, I think, is the possibility to click on any language term on the right and change language that way.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Regarding the citation, the citation in the CESSDA tool has both URN and URL. Did we conclude
that in CESSDA tool the citation URL is to that tool, and in DDI Alliance website the URL in citation is to the DDI Alliance webpage? That would need to be taken into account in the DDI publication pipeline.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">All the best, Taina</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">---</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Taina Jääskeläinen</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">FSD Finnish Social Science Data Archive</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Tampere University, FINLAND</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">e-mail:
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><a href="mailto:taina.jaaskelainen@tuni.fi" target="_blank"><span lang="EN-US" style="color:#0563C1">taina.jaaskelainen@tuni.fi</span></a></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">
| tel: +358 40 190 1444 </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><a href="http://www.fsd.uta.fi/" target="_blank"><span lang="EN-US" style="color:#0563C1">http://www.fsd.uta.fi</span></a></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Wendy
Thomas <<a href="mailto:wlt@umn.edu" target="_blank">wlt@umn.edu</a>> <br>
<b>Sent:</b> 14. maaliskuuta 2019 18:55<br>
<b>To:</b> Taina Jääskeläinen (TAU) <<a href="mailto:taina.jaaskelainen@tuni.fi" target="_blank">taina.jaaskelainen@tuni.fi</a>>; Sanda Ionescu <<a href="mailto:sandai@umich.edu" target="_blank">sandai@umich.edu</a>><br>
<b>Subject:</b> Fwd: TC: Minutes postes</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">---------- Forwarded message ---------<br>
From: <strong>Wendy Thomas</strong> <<a href="mailto:wlt@umn.edu" target="_blank">wlt@umn.edu</a>><br>
Date: Thu, Mar 14, 2019 at 11:39 AM<br>
Subject: TC: Minutes postes<br>
To: DDI Structural Reform Working Group. <<a href="mailto:ddi-srg@icpsr.umich.edu" target="_blank">ddi-srg@icpsr.umich.edu</a>><o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"> <o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Today's meeting focused on CVs and the new production pipelines for publication. Taina and Sanda joined the meeting. Minutes are at <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a href="https://ddi-alliance.atlassian.net/wiki/spaces/DDI4/pages/491551/TC+Meeting+Minutes" target="_blank">https://ddi-alliance.atlassian.net/wiki/spaces/DDI4/pages/491551/TC+Meeting+Minutes</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Action items coming out of this meeting:<o:p></o:p></p>
</div>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
TC needs to survey DDI users and determine who is using Genericode structures currently and whether this structure should be persisted given other options that will be made available for CVs<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
CVG needs to provide summary of desired functionality for the CV web pages so that priorities can be determined for changes<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
TC and CVG need to write up new production process from creation of content using CESSDA tool and export of SKOS file, through production and review, to publication and announcement. This must be completed for presentation at the Scientific Board meeting.<o:p></o:p></li></ol>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Many thanks to Taina and Sanda for joining the TC meeting!<o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br>
-- <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Wendy L. Thomas Phone: +1 612.624.4389<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Data Access Core Director Fax: +1 612.626.8375<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Minnesota Population Center Email:
<a href="mailto:wlt@umn.edu" target="_blank">wlt@umn.edu</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">University of Minnesota<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">50 Willey Hall<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">225 19th Avenue South<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Minneapolis, MN 55455<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br clear="all">
<br>
-- <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Wendy L. Thomas Phone: +1 612.624.4389<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Data Access Core Director Fax: +1 612.626.8375<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Minnesota Population Center Email:
<a href="mailto:wlt@umn.edu" target="_blank">wlt@umn.edu</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">University of Minnesota<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">50 Willey Hall<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">225 19th Avenue South<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Minneapolis, MN 55455<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<br>
-- <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">Wendy L. Thomas Phone: +1 612.624.4389<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Data Access Core Director Fax: +1 612.626.8375<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Minnesota Population Center Email: <a href="mailto:wlt@umn.edu" target="_blank">
wlt@umn.edu</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">University of Minnesota<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">50 Willey Hall<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">225 19th Avenue South<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Minneapolis, MN 55455<o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>