<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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;
color:black;}
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
{mso-style-priority:99;
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;
color:black;}
code
{mso-style-priority:99;
font-family:"Courier New";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Vorformatiert Zchn";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
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;
color:black;}
span.HTMLVorformatiertZchn
{mso-style-name:"HTML Vorformatiert Zchn";
mso-style-priority:99;
mso-style-link:"HTML Vorformatiert";
font-family:Consolas;
color:black;}
span.E-MailFormatvorlage22
{mso-style-type:personal-reply;
font-family:"Verdana",sans-serif;
color:#44546A;}
.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 bgcolor="white" lang="DE" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#44546A;mso-fareast-language:EN-US">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#44546A;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#44546A;mso-fareast-language:EN-US">ich muss sagen, ich fände es fatal, wenn wir deswegen die Dublin Core Terms-Property für URI und Literale empfehlen.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#44546A;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#44546A;mso-fareast-language:EN-US">Es ist eine Sache, wenn jemanden durch die vorgeschlagene DCMI-Property-Definition für seinen homogenen Datenbestand mit nur Literalen
die Absolution bekommt, dct:rights zu benutzen. Aber da wir hier Empfehlungen aussprechen wollen, die speziell das Zusammenspiel von Daten von verschiedenen Bereitstellern optimieren soll, würde ich das zumindest für die RDF-Daten im KIM-Titeldatenprofil auf
keinen Fall unterstützten. Wenn man unterschiedlich Werttypen an ein und derselben Property hat, sind SPARQL-Abfrage meiner Vorstellung nach nicht praktikabel und es wäre praktisch immer eine Transformation nötig, bevor man heterogene Daten gemeinsam benutzen
kann. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#44546A;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#44546A;mso-fareast-language:EN-US">Es kann sein, dass das im ESE-Datennutzungskontext keine Rolle spielt, das weiß ich natürlich nicht.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#44546A;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#44546A;mso-fareast-language:EN-US">Besten Gruß von<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#44546A;mso-fareast-language:EN-US">Jana<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Von:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> dini-ag-kim-lizenzen [mailto:dini-ag-kim-lizenzen-bounces@lists.dnb.de]
<b>Im Auftrag von </b>Stefanie Rühle<br>
<b>Gesendet:</b> Dienstag, 3. Juli 2018 14:47<br>
<b>An:</b> dini-ag-kim-lizenzen@lists.dnb.de<br>
<b>Betreff:</b> [dini-ag-kim-lizenzen] Fwd: Re: [dcmi/usage] Literal value for dct:rights (#30)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Hallo zusammen,<o:p></o:p></p>
<p>der folgende Vorschlag für eine Änderung der range für dcterms:rights ging gerade über die dcmi Usage Board Liste.<o:p></o:p></p>
<p>Gruß<o:p></o:p></p>
<p> Stefanie<o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
<br>
-------- Weitergeleitete Nachricht -------- <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td nowrap="" valign="top" style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal" align="right" style="text-align:right"><b>Betreff: <o:p></o:p></b></p>
</td>
<td style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal">Re: [dcmi/usage] Literal value for dct:rights (#30)<o:p></o:p></p>
</td>
</tr>
<tr>
<td nowrap="" valign="top" style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal" align="right" style="text-align:right"><b>Datum: <o:p></o:p></b></p>
</td>
<td style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal">Tue, 3 Jul 2018 05:28:57 -0700<o:p></o:p></p>
</td>
</tr>
<tr>
<td nowrap="" valign="top" style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal" align="right" style="text-align:right"><b>Von: <o:p></o:p></b></p>
</td>
<td style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal">tombaker <a href="mailto:notifications@github.com"><notifications@github.com></a><o:p></o:p></p>
</td>
</tr>
<tr>
<td nowrap="" valign="top" style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal" align="right" style="text-align:right"><b>Antwort an: <o:p></o:p></b></p>
</td>
<td style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal">dcmi/usage <a href="mailto:reply+0050685fbc8763098882ff883cc3ba458c2b6b44d7f2a65192cf0000000117532e0992a169ce13999409@reply.github.com">
<reply+0050685fbc8763098882ff883cc3ba458c2b6b44d7f2a65192cf0000000117532e0992a169ce13999409@reply.github.com></a><o:p></o:p></p>
</td>
</tr>
<tr>
<td nowrap="" valign="top" style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal" align="right" style="text-align:right"><b>An: <o:p></o:p></b></p>
</td>
<td style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal">dcmi/usage <a href="mailto:usage@noreply.github.com"><usage@noreply.github.com></a><o:p></o:p></p>
</td>
</tr>
<tr>
<td nowrap="" valign="top" style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal" align="right" style="text-align:right"><b>Kopie (CC): <o:p></o:p></b></p>
</td>
<td style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal">Subscribed <a href="mailto:subscribed@noreply.github.com"><subscribed@noreply.github.com></a><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p>I almost upvoted this, but agree that it would be good to recommend vocabularies. A bit more concise, adding references to Creative Commons and RightsStatements.org:<o:p></o:p></p>
<pre><code>Recommended practice is to refer to a rights statement with a URI, preferably<o:p></o:p></code></pre>
<pre><code>from a formal rights statements vocabulary such as those defined by Creative Commons<o:p></o:p></code></pre>
<pre><code>[CC] or RightsStatements.org [RIGHTS]. When no such URI is available, it is<o:p></o:p></code></pre>
<pre><code>acceptable to refer to the rights statement with a literal denoting such a<o:p></o:p></code></pre>
<pre><code>statement or with the full text of the statement.<o:p></o:p></code></pre>
<p style="-webkit-text-size-adjust:none"><span style="color:#666666">—<br>
You are receiving this because you are subscribed to this thread.<br>
Reply to this email directly, <a href="https://github.com/dcmi/usage/issues/30#issuecomment-402138560">
view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFBoX2ds9Vcy3q124NTyWlgunHDOdjlIks5uC2OJgaJpZM4UYGQX">
mute the thread</a>.<img border="0" width="1" height="1" style="width:.0104in;height:.0104in" id="_x0000_i1025" src="https://github.com/notifications/beacon/AFBoX-aRisqLiN3H2QMcC3rwVv2fH7GFks5uC2OJgaJpZM4UYGQX.gif"><o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>