[Tf-curation] lindat profile mappings to VLO

[Thomas Eckart]

> For 2) in fact what I object most is not the lack of direct download but
> the use of what for lindat users is dubbed "project page".
I agree. A ResourceProxy of type "Resource" should normally point to the 
actual resource (like the concrete corpus, tool, webservices etc.).

> So either we give a clear semantic to that field in our repo or my
> modest opinion is that I would rather see a link back to our repo on the
> resources icon if the vlo.
>
> Once redirected to lindat-clarin or ilc4clarin, users can see all info
> including the license and download if the have the permission.
> What is your opinion of this solution?
> I saw other repos do this...
That is definitely one way to do it and already more helpful for the end 
user as the status quo for "Deltacorpus 1.1".

Nonetheless, I think that this not a good solution: the CMDI 
specification allows 5 types of ResourceProxys. A reference to the 
original context of the resource in its repository is already part of it 
("LandingPage"). Right now this reference may not be prominent enough at 
the VLO record page (maybe we find a better solution?), but it is 
already there.

The "Resource"-typed ResourceProxys are defined (at least regarding the 
upcoming CMDI 1.2 specification) as references to "A resource that is 
described in the present CMDI instance, e.g. a text document, media file 
or tool.". If you don't want to directly link to the actual data, I 
guess omitting these ResourceProxys would be the standard-compliant way 
to go.
I personally think that direct links to the data should be part of the 
resource description, because it increases the usefulness of the VLO for 
the end user and of the resource in the context of the whole infrastructure.

Best,
Thomas


-- 
Thomas Eckart
Natural Language Processing Group
Department of Computer Science
University of Leipzig
Augustusplatz 10
04109 Leipzig, Germany