<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 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="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Re: English CV version<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">A CV should have ideally all available languages in one document. The language is only applied to the description part. The code and the official English definition
is the core of the CV. (Adding more languages to one document should result in a new (possibly minor) version of the document).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Therefore I’m not sure why there should be multiple CV documents (for each language each).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">SKOS, which is used for this, is able – as any RDF document – to express multiple languages for descriptions in one RDF document.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Even, if one thinks theoretically on multiple resources (one for each language), there is a an acknowledged way in the web to deal with this. It is called HTTP
content negotiation. The idea is that a resource (with all available versions) has one identifier. The request should express by a HTTP header which version is desired. The server can deliver the specific version if available otherwise a generic version.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Further information available at:
<a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Language">
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Language</a>, <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Language">
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Language</a>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Achim<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> ddi-srg-bounces@icpsr.umich.edu [mailto:ddi-srg-bounces@icpsr.umich.edu]
<b>On Behalf Of </b>Wendy Thomas<br>
<b>Sent:</b> Mittwoch, 13. März 2019 16:10<br>
<b>To:</b> DDI Structural Reform Working Group.; Taina Jääskeläinen (TAU); Sanda Ionescu<br>
<b>Subject:</b> [DDI-SRG] TC: Agenda for Thursday with CV<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">NOTE TIME: Due to North America going on DST before Europe<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">8:00 US Pacific<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">10:00 US Central<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">11:00 US Easter<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">15:00 UK<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">16:00 Central Europe<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">17:00 Eastern Europe<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Sorry for not getting this out sooner...I've been down with cold. Taina and I hope Sanda will be joining us to discuss what needs to be done in TC to support CV work. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Taina has provided the following list of topics:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">- Does the DDI Alliance want to publish the translations of the CVs as well as the source CVs? That would require changes in the website. If not, I think there should be a reference to the CESSDA Vocabulary Service CV which has the translations.
And even if yes, a reference anyway?<br>
<br>
- On the DDI Alliance website, the different location URIs of different vocabulary formats take too much space. Can this be amended, for example, by presenting a button for each format?<br>
<br>
- URN: at present the ‘Canonical URI of this version’ element (=urn of the version) does not have a language tag. The IT people for the CESSDA tool say they would like also the source vocabulary have a language tag. This would mean that the urn of the English
CV version would be: <br>
urn:ddi:int.ddi.cv:TypeOfInstrument:2.0-en.<br>
Is this OK?<br>
<br>
- The tool produces a citation which does not exist in CVs now published on the DDI Alliance website. What to do with this in data transfer?<br>
<br>
- Usage information may be presented differently, can the publication pipeline just publish whatever is there in the CVs in the CESSDA tool? Module/attribute/element names will be there with a link to the specification, as well as element numbers for DDI2
but no definitions of the element as now in DDI website.<br>
<br>
- The tool will automatically assign the publication year as the copyright year. For all CVs published from the CESSDA tool, it will be the current year, be the CV old or new.<br>
<br>
- Urn resolver planned for DDI?<o:p></o:p></p>
</div>
<p class="MsoNormal"><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>
</div>
</body>
</html>