<div dir="ltr"><div>2Thomas: Minor comment about the statement: even though I can see the good intention behind the statement, I have doubts if it has any legal basis. Moreover, from the user point of view I read the message as: "Please, rather do not use VLO because what you see here is probably wrong."</div><div><span style="color:rgb(41,28,22);font-size:12.48px;line-height:21.216px;background-color:rgb(211,222,240)">Please </span><strong style="color:rgb(41,28,22);font-size:12.48px;line-height:21.216px;background-color:rgb(211,222,240)">verify this information</strong><span style="color:rgb(41,28,22);font-size:12.48px;line-height:21.216px;background-color:rgb(211,222,240)"> at the original source or contact the original provider before using any of the resources or tools described on this page.</span><br></div><div><br></div><div><br></div><div>2Francesca: Please, file an issue at <a href="https://github.com/ufal/lindat-dspace">https://github.com/ufal/lindat-dspace</a> about exploiting the different ResourceTypes as pointed out by Thomas and also to use proper names for them. Few references:<br></div><div><a href="https://trac.clarin.eu/wiki/CMDI%201.2/Specification">https://trac.clarin.eu/wiki/CMDI%201.2/Specification</a><br></div><div><a href="https://www.clarin.eu/faq/how-do-i-point-files-im-describing-cmdi-how-does-resources-section-work">https://www.clarin.eu/faq/how-do-i-point-files-im-describing-cmdi-how-does-resources-section-work</a><br></div><div><a href="https://www.clarin.eu/faq/how-can-i-indicate-resources-described-cmdi-file-are-also-searchable-srucql">https://www.clarin.eu/faq/how-can-i-indicate-resources-described-cmdi-file-are-also-searchable-srucql</a><br></div><div><br></div><div><br></div><div>Best,</div><div>Jozef</div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 1 July 2016 at 13:22, Thomas Eckart <span dir="ltr"><<a href="mailto:teckart@informatik.uni-leipzig.de" target="_blank">teckart@informatik.uni-leipzig.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Francesca,<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Any suggestion?<br>
We would like to keep a common policy for all centers using the LINDAT<br>
software.<br>
</blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Another thing, in the our version of LINDAT the field "Demo URL" isn't<br>
generating any resource proxy in the resulting CMDI.<br>
Maybe that would be a more suitable candidate ...<br>
<br>
See this resource and its CMDI for reference.<br>
<a href="https://lindat.mff.cuni.cz/repository/xmlui/handle/11234/1-1741" rel="noreferrer" target="_blank">https://lindat.mff.cuni.cz/repository/xmlui/handle/11234/1-1741</a><br>
</blockquote></span>
"Demo URL" ("A url with samples of the resource or, in the case of tools, of samples of the output.") sounds indeed like a better candidate for a resource reference. Beyond that I can't say anything about both of your problems as I am not involved in the LINDAT depositing service. Maybe someone working on the tool can jump in...<br>
<br>
Best,<br>
Thomas<br>
<br>
<br>
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
2016-06-30 16:47 GMT+02:00 Thomas Eckart<br>
<<a href="mailto:teckart@informatik.uni-leipzig.de" target="_blank">teckart@informatik.uni-leipzig.de</a><br></span>
<mailto:<a href="mailto:teckart@informatik.uni-leipzig.de" target="_blank">teckart@informatik.uni-leipzig.de</a>>>:<div><div class="h5"><br>
<br>
For 2) in fact what I object most is not the lack of direct<br>
download but<br>
the use of what for lindat users is dubbed "project page".<br>
<br>
I agree. A ResourceProxy of type "Resource" should normally point to<br>
the actual resource (like the concrete corpus, tool, webservices etc.).<br>
<br>
So either we give a clear semantic to that field in our repo or my<br>
modest opinion is that I would rather see a link back to our<br>
repo on the<br>
resources icon if the vlo.<br>
<br>
Once redirected to lindat-clarin or ilc4clarin, users can see<br>
all info<br>
including the license and download if the have the permission.<br>
What is your opinion of this solution?<br>
I saw other repos do this...<br>
<br>
That is definitely one way to do it and already more helpful for the<br>
end user as the status quo for "Deltacorpus 1.1".<br>
<br>
Nonetheless, I think that this not a good solution: the CMDI<br>
specification allows 5 types of ResourceProxys. A reference to the<br>
original context of the resource in its repository is already part<br>
of it ("LandingPage"). Right now this reference may not be prominent<br>
enough at the VLO record page (maybe we find a better solution?),<br>
but it is already there.<br>
<br>
The "Resource"-typed ResourceProxys are defined (at least regarding<br>
the upcoming CMDI 1.2 specification) as references to "A resource<br>
that is described in the present CMDI instance, e.g. a text<br>
document, media file or tool.". If you don't want to directly link<br>
to the actual data, I guess omitting these ResourceProxys would be<br>
the standard-compliant way to go.<br>
I personally think that direct links to the data should be part of<br>
the resource description, because it increases the usefulness of the<br>
VLO for the end user and of the resource in the context of the whole<br>
infrastructure.<br>
<br>
Best,<br>
Thomas<br>
<br>
<br>
<br>
--<br>
Thomas Eckart<br>
Natural Language Processing Group<br>
Department of Computer Science<br>
University of Leipzig<br>
Augustusplatz 10<br>
04109 Leipzig, Germany<br>
<br>
<br>
</div></div></blockquote><div class="HOEnZb"><div class="h5">
<br>
-- <br>
Thomas Eckart<br>
Natural Language Processing Group<br>
Department of Computer Science<br>
University of Leipzig<br>
Augustusplatz 10<br>
04109 Leipzig, Germany<br>
</div></div></blockquote></div><br></div>