[Tf-curation] [TF-CMDI] Next CMDI/Curation TF meeting

Fri Oct 26 15:34:22 CEST 2018

> Furthermore there is section on multilingual metadata (p23) which in
> fact does not mention ISO 639-3 but it probably should.

It mentions BCP 47, which does fall back to the ISO 369 family of language codes. However, this relates to @xml:lang. I guess that Pavel means a recommendation that ISO 639-3 should be used for a language metadata element (what language is the resource about), which is different than multinguality of the metadata record itself. The harvest conversions/VLO import handling does focus on ISO 639 and some older SIL codes, so there is a clear preference in the infrastructure. So, I think it’s very likely that such a language element bound to the ISO 639-3 code set will be part of the recommended component(s) ;-)

Menzo

---------------------------------------------------------------------------------------------------------
Dr. Menzo Windhouwer
Lead Software Engineer – Structured Data

KNAW Humanities Cluster
Department of Digital Infrastructure
T + 31(0)20 2246800

PO Box 10855
NL – 1001 EW Amsterdam

Oudezijds Achterburgwal 185
NL - 1012 DK Amsterdam

huc.knaw.nl
------------------------------------------------------------------------------------------------------------- 

On 26/10/2018, 15:22, "tf-cmdi-bounces at lists.clarin.eu on behalf of Pavel Stranak" <tf-cmdi-bounces at lists.clarin.eu on behalf of stranak at ufal.mff.cuni.cz> wrote:

    Thanks for the update, Twan. I am looking forward to the recommended components. Seems to be exactly what I was asking about.

    Pavel

    > On 26 Oct 2018, at 14:14, Twan Goosen <twan at clarin.eu> wrote:
    > 
    > Hi Pavel,
    > 
    > Thanks for your interest and feedback. Something along the lines of
    > minimal metadata has (obviously) been on our radar/agenda more or less
    > from the beginning of the best practices initiative. Along the way
    > attention to this topic has branched off into the 'general info' aka
    > 'recommended components' initiative which Hanna and I are currently
    > trying to get off the ground. We plan to schedule a meeting on this
    > topic in the near future, and of course you are very welcome to attend
    > and/or get involved with this effort.
    > 
    > As Hanna was not present this topic was not covered in this week's
    > meeting (so no related notes) but we did discuss it briefly at the joint
    > task forces meeting at the annual conference - see the notes at
    > <https://trac.clarin.eu/wiki/Taskforces/CMDI/Meeting20181008>.
    > 
    > In addition to this, some of the points you mention are covered
    > partially, or at least strongly relate to specific (planned) content of
    > the guide. The best practice of providing English metadata is part of
    > CS3 (p19):
    > 
    >> The default language for element contents is English, meaning that English wording should be provided for each element of the CMDI profile used. Additionally, other languages may be used, complementing the English version of a CMDI record. The possibility of multilinguality has to be already included in the design of the component. For the specification of the language applied, each element should be provided with an @xml:lang attribute (even when the content is in English). Use a BCP 47 language tag to unambiguously identify the respective language within @xml:lang.
    > 
    > Furthermore there is section on multilingual metadata (p23) which in
    > fact does not mention ISO 639-3 but it probably should. It does, again,
    > state that..
    > 
    >> If a language other than English is allowed/possible, an English version should be provided wherever feasible.
    > and
    > 
    >> Especially titles and descriptions should be multilingual. Provide English variants first, or if not feasible start with the ‘native’ language followed by English
    > A section on licensing information is foreseen but has not been written yet.
    > 
    > I hope that clarifies the situation. Let us know if you are interested
    > in contributing in any way!
    > 
    > Best,
    > Twan
    > 
    > On 25/10/2018 18:13, Pavel Stranak wrote:
    >> Hi Twan,
    >> 
    >> I had a look at the notes and also the Best Practices document. I see no mention anywhere of something like a requirement for minimal standard CLARIN metadata. We discussed it a long time ago, I believe Jan Odijk initiated it. Is it completely out of interest of the TFs now, either because it turned out impossible to agree on anything, or maybe because we turned out to all implement suitable minimal set even without rules?
    >> 
    >> I mean really basic things like:
    >> --------------------------------
    >> - English MD required, other languages possible
    >> - Everything has a title, author and description (in English, see point 1), data files (as opposed to software) also have a language
    >> - ISO 639-3 is used for language
    >> - Everything has a license (since without it data can as well not be there, nobody is allowed to use it)
    >> 
    >> This is pretty much it, from the top of my head.
    >> 
    >> Best,
    >> Pavel
    >> 
    >> 
    >> 
    >>> On 25 Oct 2018, at 17:31, Twan Goosen <twan at clarin.eu> wrote:
    >>> 
    >>> Hi all,
    >>> 
    >>> Thanks to the participants (more than I had expected :D) for an
    >>> interesting meeting! I have added some notes to
    >>> <https://trac.clarin.eu/wiki/Taskforces/CMDI/Meeting20181025#Notes>.
    >>> 
    >>> We agreed to schedule our next meeting second half of November. For
    >>> those interested in attending, here's a *Doodle*:
    >>> 
    >>> 	<https://doodle.com/poll/k2989x9av9mvw6mb>
    >>> 
    >>> As soon as we have a date I will create a meeting page and we can draft
    >>> an agenda. Note that the scope will likely be broader than just best
    >>> practices, so even if you have not been involved in editing the best
    >>> practice guide you might find it interesting to attend. The notes of
    >>> today's meeting give a good overview of potential topics of discussion.
    >>> 
    >>> Best,
    >>> Twan
    >>> 
    >>> On 25/10/2018 10:35, Twan Goosen wrote:
    >>>> Hi all,
    >>>> 
    >>>> Here's a reminder that we have a join task forces meeting scheduled for
    >>>> 14:00 CEST this afternoon [1]. Thus far not that many people have
    >>>> indicated they could attend but perhaps others are interested in
    >>>> joining. I think the most important thing to do concretely is turn our
    >>>> thoughts, discussions and conclusions from the annual conference into
    >>>> concrete actions and see if we can come up with some sort of roadmap. If
    >>>> you would like to review these, note that (somewhat) processed notes of
    >>>> the task forces meeting are now available at the meeting page [2].
    >>>> 
    >>>> The zoom link for today's meeting is
    >>>> <https://clarin.zoom.us/j/534115968>. Hope to see you this afternoon!
    >>>> 
    >>>> Best,
    >>>> Twan
    >>>> 
    >>>> [1] https://trac.clarin.eu/wiki/Taskforces/CMDI/Meeting20181025
    >>>> [2] https://trac.clarin.eu/wiki/Taskforces/CMDI/Meeting20181008#Notes
    >>>> 
    >>> 
    >>> -- 
    >>> Twan Goosen
    >>> Software developer at CLARIN ERIC
    >>> www.clarin.eu | twan at clarin.eu
    >>> _______________________________________________
    >>> Tf-curation mailing list
    >>> Tf-curation at lists.clarin.eu
    >>> https://lists.clarin.eu/cgi-bin/mailman/listinfo/tf-curation
    >> 
    > 
    > -- 
    > Twan Goosen
    > Software developer at CLARIN ERIC
    > www.clarin.eu | twan at clarin.eu

    _______________________________________________
    Tf-cmdi mailing list
    Tf-cmdi at lists.clarin.eu
    https://lists.clarin.eu/cgi-bin/mailman/listinfo/tf-cmdi