<div dir="ltr"><div>If this is just the issue of CESSDA's approach to language it may be something that is out of scope for TC. We called this meeting to address what TC needed to do to facilitate the use of the output of the CV management system (SKOS to various formats published for DDI). We have a full schedule for next week so today's meeting will take place as scheduled and we will try to clarify those issues that need to be addressed with CESSDA in addition to dealing with those related to production.</div><div><br></div><div>Wenndy</div></div><br><div class="gmail_quote"><div class="gmail_attr" dir="ltr">On Thu, Mar 14, 2019 at 9:10 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="EN-US">
<div class="gmail-m_-2899420055023379923WordSection1">
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">Hi Taina,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">In this sense, it might be best that Carsten, Claus-Peter, TC people including myself, and you and Sanda are meeting to discuss all CV related issues. Otherwise,
there could be the risk that a perspective is missing.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">Today, I have no time.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">Wendy:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">Could the next week’s TC meeting used for this?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span 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 style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p>
<div>
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentColor currentColor;padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span lang="DE" style="font-family:"Tahoma","sans-serif";font-size:10pt">From:</span></b><span lang="DE" style="font-family:"Tahoma","sans-serif";font-size:10pt"> Taina Jääskeläinen (TAU) [mailto:<a href="mailto:taina.jaaskelainen@tuni.fi" target="_blank">taina.jaaskelainen@tuni.fi</a>]
<br>
<b>Sent:</b> Mittwoch, 13. </span><span style="font-family:"Tahoma","sans-serif";font-size:10pt">März 2019 18:24<br>
<b>To:</b> Wackerow, Joachim; Wendy Thomas<br>
<b>Cc:</b> DDI Structural Reform Working Group.; Sanda Ionescu<br>
<b>Subject:</b> Re: [DDI-SRG] TC: Agenda for Thursday with CV<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div id="gmail-m_-2899420055023379923divtagdefaultwrapper">
<p><span style="color:black;font-family:"Calibri","sans-serif"">Hi Achim,<u></u><u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif"">would you be able to attend the TC meeting tomorrow? It would be really good to have this straightened out.<u></u><u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif"">It may be my mistake that I could not explain why the language tags in urns are not a good idea. CESSDA does not have any desire to for individual policy in this. <u></u><u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif"">The language versions are all in the same document. See<u></u><u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif""><a id="gmail-m_-2899420055023379923LPlnk880333" href="https://cv-dev.cessda.eu/cvmanager/#!detail/TypeOfInstrument?url=http%3A%2F%2Fwww.ddialliance.org%2FSpecification%2FDDI-CV%2FTypeOfInstrument%2Fen%2F2.2" target="_blank">https://cv-dev.cessda.eu/cvmanager/#!detail/TypeOfInstrument?url=http%3A%2F%2Fwww.ddialliance.org%2FSpecification%2FDDI-CV%2FTypeOfInstrument%2Fen%2F2.2</a><u></u><u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif"">cessda<u></u><u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif"">CESSDA2018<u></u><u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif"">- You need to make an exception to enter.<u></u><u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif"">The canonical URI is the same for all languages, see Identity and general tab.<u></u><u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif"">The question concerned the Canonical uri of the version, which can be seen in citation. Its production is not yet machine-produced, this is why Canonical uri of the version is as yet missing from
the Identity and general tab. In this urn the developer wished to have a language tag there, and I did not know what to answer. <u></u><u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif"">We also need to finalise machine-produced citation in the tool (can be manually edited as well). The user group asked the non-language specific urn of the version to be used in citation in all
languages, as previously discussed. Therefore it seemed to me that we are going to run into trouble if we have language tags in it.<u></u><u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif"">I would be good for tech people discuss this among themselves, just as long as you tell the user group the conclusion and we can write the User Guide accordingly.<u></u><u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif"">All the best, Taina<u></u><u></u></span></p>
<p><span style="color:black;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
</div>
<div align="center" class="MsoNormal" style="text-align:center">
<hr width="98%" size="3" align="center">
</div>
<div id="gmail-m_-2899420055023379923divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black;font-family:"Calibri","sans-serif";font-size:11pt">From:</span></b><span style="color:black;font-family:"Calibri","sans-serif";font-size:11pt"> Wackerow, Joachim <<a href="mailto:Joachim.Wackerow@gesis.org" target="_blank">Joachim.Wackerow@gesis.org</a>><br>
<b>Sent:</b> 13 March 2019 18:23:20<br>
<b>To:</b> Wendy Thomas<br>
<b>Cc:</b> DDI Structural Reform Working Group.; Sanda Ionescu; Taina Jääskeläinen (TAU)<br>
<b>Subject:</b> RE: [DDI-SRG] TC: Agenda for Thursday with CV</span> <u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">Taina,</span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"> </span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">I recommend that some technical person from CESSDA should look at this. It doesn’t really make sense that CESSDA wants to go another way as what is common
practice in the Web and the Semantic Web.</span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"> </span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">I think Carsten Thiel and Claus-Peter Klas are the appropriate people for this. I’m happy to talk to them in case they have questions.</span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"> </span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">Achim</span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"> </span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"> </span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><b><span style="font-family:"Tahoma","sans-serif";font-size:10pt">From:</span></b><span style="font-family:"Tahoma","sans-serif";font-size:10pt"> <a href="mailto:ddi-srg-bounces@icpsr.umich.edu" target="_blank">ddi-srg-bounces@icpsr.umich.edu</a> [mailto:<a href="mailto:ddi-srg-bounces@icpsr.umich.edu" target="_blank">ddi-srg-bounces@icpsr.umich.edu</a>]
<b>On Behalf Of </b>Wendy Thomas<br>
<b>Sent:</b> Mittwoch, 13. März 2019 17:01<br>
<b>To:</b> Wackerow, Joachim<br>
<b>Cc:</b> DDI Structural Reform Working Group.; Sanda Ionescu; Taina Jääskeläinen (TAU)<br>
<b>Subject:</b> Re: [DDI-SRG] TC: Agenda for Thursday with CV</span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"> <u></u><u></u></p>
<div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">Achim,<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal"> <u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">Thanks for the back ground information on this. It is what has been agreed in the original production of CVs and was also noted in the work done in Dagstuhl. I realize that CESSDA views this differently but what you've stated is absolutely
correct. There is a CV with terms and then descriptions/labels in multiple languages which can be selected during negotiation during resolution.<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal"> <u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">Wendy<u></u><u></u></p>
</div>
</div>
<p class="gmail-m_-2899420055023379923xmsonormal"> <u></u><u></u></p>
<div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">On Wed, Mar 13, 2019 at 10:45 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);margin:5pt 0cm 5pt 4.8pt;padding:0cm 0cm 0cm 6pt">
<div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">Re: English CV version</span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"> </span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">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).</span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">Therefore I’m not sure why there should be multiple CV documents (for each language each).</span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">SKOS, which is used for this, is able – as any RDF document – to express multiple languages for descriptions in one RDF document.</span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"> </span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">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.</span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">Further information available at:
<a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Language" target="_blank">
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" target="_blank">
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Language</a>.</span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"> </span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">Achim</span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"> </span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"><b><span style="font-family:"Tahoma","sans-serif";font-size:10pt">From:</span></b><span style="font-family:"Tahoma","sans-serif";font-size:10pt">
<a href="mailto:ddi-srg-bounces@icpsr.umich.edu" target="_blank">ddi-srg-bounces@icpsr.umich.edu</a> [mailto:<a href="mailto:ddi-srg-bounces@icpsr.umich.edu" target="_blank">ddi-srg-bounces@icpsr.umich.edu</a>]
<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</span><u></u><u></u></p>
<p class="gmail-m_-2899420055023379923xmsonormal"> <u></u><u></u></p>
<div>
<div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">NOTE TIME: Due to North America going on DST before Europe<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">8:00 US Pacific<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">10:00 US Central<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">11:00 US Easter<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">15:00 UK<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">16:00 Central Europe<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">17:00 Eastern Europe<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal"> <u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">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. <u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal"> <u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">Taina has provided the following list of topics:<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">- 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?<u></u><u></u></p>
</div>
<p class="gmail-m_-2899420055023379923xmsonormal"><br>
-- <u></u><u></u></p>
<div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">Wendy L. Thomas Phone: +1 612.624.4389<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">Data Access Core Director Fax: +1 612.626.8375<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">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="gmail-m_-2899420055023379923xmsonormal">University of Minnesota<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">50 Willey Hall<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">225 19th Avenue South<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">Minneapolis, MN 55455<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="gmail-m_-2899420055023379923xmsonormal"><br clear="all">
<br>
-- <u></u><u></u></p>
<div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">Wendy L. Thomas Phone: +1 612.624.4389<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">Data Access Core Director Fax: +1 612.626.8375<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">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="gmail-m_-2899420055023379923xmsonormal">University of Minnesota<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">50 Willey Hall<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">225 19th Avenue South<u></u><u></u></p>
</div>
<div>
<p class="gmail-m_-2899420055023379923xmsonormal">Minneapolis, MN 55455<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</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>