<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:"Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Dear all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Just a general thought on the topic.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Correct me if I am wrong, as I have not worked on CMDI so long. :)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I think what metadata within the CMDI-VLO does not have is a standard way to have both a custom field (which ideally should be also controlled) and a CLARIN normalised
field (to make near 100% facet coverage) for the same value. Instead, CMDI centrally normalises whatever source fields a provider defines (and/or mapping them to other fields CLARIN needs)…this could cause confusions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">This is different from the approach of other metadata. For instance, in Europeana, there are dc:type (which you can put anything about a type of a resource (eg
photo, newspaper)) and edm:type (which is mandatory and has to be one of TEXT, IMAGE, VIDEO, SOUND, and 3D). Similar situation can be seen in other metadata such as EAD (as global attribute of NORMAL). This is the way normally how to make a facet consistent.
On the other hand, CLARIN has too few restrictions on the controlled vocabularies, elements, and cardinalities etc, which leads to many metadata curation tasks, so, at least, I think this kind of point can be more clarified in the CMDI guidelines people are
preparing. For example, we could say “keep original values and recommend to create a new field to map them to CLARIN vocabularies (CLAVAS etc).” In this way, we can finally have the controlled vocabularies for VLO we have dreamed of. This would be an alternative
solution for CLARIN to pass the curation tasks to the data providers (although I cannot say for sure if it is the easiest solution, when VLO/CMDI is already mature and hard to change).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Go Sugimoto<o:p></o:p></span></b></p>
<p class="MsoNormal"><a href="mailto:Go.Sugimoto@oeaw.ac.at"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0563C1">Go.Sugimoto@oeaw.ac.at</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">
</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><a href="acdh.oeaw.ac.at"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0563C1">Austrian Centre for Digital Humanities (ACDH)</span></a><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><a href="oeaw.ac.at"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0563C1">Austrian Academy of Sciences</span></a><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Skype: heygo4it<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">LinkedIn:
</span><a href="https://www.linkedin.com/in/gosavethequeen"><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0563C1">https://www.linkedin.com/in/gosavethequeen</span></a><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">ResearchGate:
</span><a href="http://www.researchgate.net/profile/Go_Sugimoto2"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0563C1">http://www.researchgate.net/profile/Go_Sugimoto2</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">
</span><span lang="EN-GB" 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:14.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> tf-curation-bounces@lists.clarin.eu <tf-curation-bounces@lists.clarin.eu>
<b>On Behalf Of </b>Ondrej Košarko<br>
<b>Sent:</b> Tuesday, June 12, 2018 10:07 AM<br>
<b>To:</b> Odijk, J.E.J.M. (Jan) <j.odijk@uu.nl><br>
<b>Cc:</b> tf-curation@lists.clarin.eu<br>
<b>Subject:</b> Re: [Tf-curation] clavas vocabulary for licenses<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Dear Jan, all,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I'm wondering if CLAVAS (or any "fixed" vocabulary) is a good fit for fields where new values will appear over time. Even though we try to avoid it as much as possible, we do have custom licenses applicable to just one particular item.
How'd a dictionary handle that? A catch all "other" value doesn't feel right. Would that mean updating the dictionary periodically, and having "invalid" values in between the updates?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Currently we are using url with this concept <a href="http://hdl.handle.net/11459/CCR_C-6586_2c79d86a-5a75-0890-d407-7d9cb86b9beb">http://hdl.handle.net/11459/CCR_C-6586_2c79d86a-5a75-0890-d407-7d9cb86b9beb</a> to identify/point to the
license. Then the license name in our profile is optional and just a string.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Ondrej<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">2018-06-11 22:02 GMT+02:00 Odijk, J.E.J.M. (Jan) <<a href="mailto:j.odijk@uu.nl" target="_blank">j.odijk@uu.nl</a>>:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="NL"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Dear Curation task force,<span lang="NL"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="NL"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The list of values for license in the (META_SHARE originating) profile resourceInfo (clarin.eu:cr1:p_1360931019836) is quite extensive, and I would like to reuse it for a profile
I manage. A disadvantage is that no semantics for the vocabulary items are defined, but one can imagine working on that together with the original profile creator (Penny Labropoulou)<span lang="NL"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="NL"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I cannot reuse the vocabulary because it is a vocabulary of a CMDI element (and not, on its own, of a component).<span lang="NL"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="NL"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">An option would be to make this vocabulary a vocabulary in CLAVAS.<span lang="NL"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I understood from Menzo that there are plans for CLAVAS vocabulary for license, and I wonder whether this one is being taken into consideration, and what the plans for such a vocabulary
are.<span lang="NL"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="NL"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I look forward to your response<span lang="NL"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Jan<span lang="NL"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">-----------------------------------------------------<span lang="NL"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Prof.dr. Jan Odijk<span lang="NL"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Professor of Language and Speech Technology<span lang="NL"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="NL">Director CLARIAH<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="NL">UiL-OTS<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="NL">Trans 10 k. 2.33<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="NL">3512 JK Utrecht<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="NL">T +31 30 253 5745<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="NL">F +31 30 253 6000<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="NL">Skype janodijk10<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="NL">-----------------------------------------------------<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="NL"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Tf-curation mailing list<br>
<a href="mailto:Tf-curation@lists.clarin.eu">Tf-curation@lists.clarin.eu</a><br>
<a href="https://lists.clarin.eu/cgi-bin/mailman/listinfo/tf-curation" target="_blank">https://lists.clarin.eu/cgi-bin/mailman/listinfo/tf-curation</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>