[Tf-curation] clavas vocabulary for licenses
Ondřej Košarko
kosarko at ufal.mff.cuni.cz
Tue Jun 12 10:06:54 CEST 2018
Dear Jan, all,
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?
Currently we are using url with this concept
http://hdl.handle.net/11459/CCR_C-6586_2c79d86a-5a75-0890-d407-7d9cb86b9beb
to identify/point to the license. Then the license name in our profile is
optional and just a string.
Best,
Ondrej
2018-06-11 22:02 GMT+02:00 Odijk, J.E.J.M. (Jan) <j.odijk at uu.nl>:
>
>
> Dear Curation task force,
>
>
>
> 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)
>
>
>
> I cannot reuse the vocabulary because it is a vocabulary of a CMDI
> element (and not, on its own, of a component).
>
>
>
> An option would be to make this vocabulary a vocabulary in CLAVAS.
>
> 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.
>
>
>
> I look forward to your response
>
> Jan
>
> -----------------------------------------------------
>
> Prof.dr. Jan Odijk
>
> Professor of Language and Speech Technology
>
> Director CLARIAH
>
> UiL-OTS
>
> Trans 10 k. 2.33
>
> 3512 JK Utrecht
>
> T +31 30 253 5745
>
> F +31 30 253 6000
>
> Skype janodijk10
>
> -----------------------------------------------------
>
>
>
> _______________________________________________
> Tf-curation mailing list
> Tf-curation at lists.clarin.eu
> https://lists.clarin.eu/cgi-bin/mailman/listinfo/tf-curation
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clarin.eu/pipermail/tf-curation/attachments/20180612/cfe5a7bc/attachment.html>
More information about the Tf-curation
mailing list