<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=us-ascii">
<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:11.0pt;
font-family:"Calibri","sans-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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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="color:#1F497D">I assumed that the RDF (as well as the other representations) can hold data also (not just metadata). SPARQL can retrieve from this whatever the query defines.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">It is in my understanding still within a broad definition of discovery. Maybe this is too narrow. In a traditional sense RDF could be the basis of search and retrieval.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Anyway, the mentioned three main purposes – exchange/preservation, discovery, program libraries – could be described more detailed in a document which lays out the purpose and reasoning of the representations
of the new DDI.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><br>
Achim<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<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-users-bounces@icpsr.umich.edu [mailto:ddi-users-bounces@icpsr.umich.edu]
<b>On Behalf Of </b>Hoyle, Larry<br>
<b>Sent:</b> Donnerstag, 17. Dezember 2015 15:46<br>
<b>To:</b> Data Documentation Initiative Users Group<br>
<b>Subject:</b> Re: [DDI-users] [MT] Implementable representations / roundtrip of DDI data/metadata<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Is there another purpose to the RDF – restructuring of data, including merging data from multiple sources? If data values are included, one can with SPARQL queries retrieve “mashed up” data.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">--- Larry Hoyle<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> <a href="mailto:ddi-users-bounces@icpsr.umich.edu">
ddi-users-bounces@icpsr.umich.edu</a> [<a href="mailto:ddi-users-bounces@icpsr.umich.edu">mailto:ddi-users-bounces@icpsr.umich.edu</a>]
<b>On Behalf Of </b>Wackerow, Joachim<br>
<b>Sent:</b> Thursday, December 17, 2015 5:40 AM<br>
<b>To:</b> Data Documentation Initiative Users Group (<a href="mailto:ddi-users@icpsr.umich.edu">ddi-users@icpsr.umich.edu</a>) <<a href="mailto:ddi-users@icpsr.umich.edu">ddi-users@icpsr.umich.edu</a>><br>
<b>Subject:</b> [DDI-users] [MT] Implementable representations / roundtrip of DDI data/metadata<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I wrote a couple of thoughts on the basis of some conversations in Copenhagen and in the last modelers meeting.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I think the major challenge now is to find the right balance between modeling the reality in a correct way, structuring the model smartly, and producing implementable representations.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">DDI data/metadata should be able to use different representations without loss of information. The model itself is one of these representations.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It would be great if the future discussions on design patterns, versioning, review of the model etc. could be done with this background in mind.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Any comments welcome.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Achim<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>