Skip to main content

Notice

We are in the process of rolling out a soft launch of the RDA website, which includes a new member platform. Existing RDA members PLEASE REACTIVATE YOUR ACCOUNT using this link: https://rda-login.wicketcloud.com/users/confirmation. Visitors may encounter functionality issues with group pages, navigation, missing content, broken links, etc. As you explore the new site, please provide your feedback using the UserSnap tool on the bottom right corner of each page. Thank you for your understanding and support as we work through all issues as quickly as possible. Stay updated about upcoming features and functionalities: https://www.rd-alliance.org/rda-web-platform-upcoming-features-and-functionalities/

#130354

Dear Makx,
Thanks for the reply, and apologies for not having followed all
of the discussion on github (I am watching it, but the volume of
messages is more than I can keep up with).
Certainly, it is undesirable to require that all metadata conform
to a de jure standard. The crux of the issue I was raising is
contained in the following questions. When does a community
guideline become a community standard? if a repository that serves
a particular community develops a custom metadata standard, they
can declare that a “community standard”, no?  But this would not
advance interoperability or reuse outside of that community. What
is the minimal size of a community that can declare its own
standard? What is the process for achieving and verifying
community endorsement?
I rather liked Michel Dumontier’s suggested requirement that
every community specification is encoded in a manner that allows
computational verification of 1) syntax, and 2) content
expectations. I may have missed some replies, but apparently this
suggestion did not fly, perhaps because it was deemed too onerous.
Cheers,
SiriJodha

On 10/15/19 12:50 PM, Makx Dekkers
wrote:

cite=”mid:***@***.***”>

medium)”>

style=”color:windowtext;mso-fareast-language:EN-US”>Dear
SiriJodha,

style=”color:windowtext;mso-fareast-language:EN-US”> 

style=”color:windowtext;mso-fareast-language:EN-US”>We’ll
take your comment into account and use ‘standard’
consistently.

style=”color:windowtext;mso-fareast-language:EN-US”> 

style=”color:windowtext;mso-fareast-language:EN-US”>However,
we do still have a discussion about how formal a ‘standard’
needs to be. See for example
href=”https://github.com/RDA-FAIR/FAIR-data-maturity-model-WG/issues/29#issuecomment-522873345″
moz-do-not-send=”true”>https://github.com/RDA-FAIR/FAIR-data-maturity-model-WG/issues/29#issuecomment-522873345.
Whenever they exist, it should be recommended to conform to
de-jure standards but it may also be necessary to
allow for de-facto standards, and even
specifications that may become standards in the future – for
example to allow for research in new and innovative areas
that are so young that there has been no time to develop
standards.

style=”color:windowtext;mso-fareast-language:EN-US”> 

style=”color:windowtext;mso-fareast-language:EN-US”>Would
you agree?

style=”color:windowtext;mso-fareast-language:EN-US”> 

style=”color:windowtext;mso-fareast-language:EN-US”>Kind
regards, Makx.

style=”color:windowtext;mso-fareast-language:EN-US”> 

style=”color:windowtext;mso-fareast-language:EN-US”> 

1.0pt;padding:3.0pt 0cm 0cm 0cm”>

lang=”EN-US”>From:
style=”color:windowtext” lang=”EN-US”>
***@***.***-groups.org

Sent: 15 October 2019 09:28
To: ***@***.***-groups.org
Subject: Re: [fair_maturity] RDA FAIR data
maturity model: Invitation to contribute!

 
Hello All,
I’m okay with the prioritization of the indicators as shown
in the survey. However, indicator R1.2-01M,
“Metadata includes provenance information according to
community-specific guidelines”, uses the term “guidelines”
while the term “standards” is used when referring to community
conventions in all the other indicators. I think some
clarification on when conformance to standards (presumably de
jure standards) is needed and when guidelines suffice.
Moreover, how the latter are codified and deemed to be
community endorsed.
Cheers,
SiriJodha

On 10/14/19 2:17 PM, ChrisB via FAIR Data
Maturity Model WG wrote:

style=”font-family:”Arial”,sans-serif”
lang=”EN”>Dear members of the RDA FAIR data maturity
model Working Group,
style=”font-family:”Arial”,sans-serif”>

style=”font-family:”Arial”,sans-serif”
lang=”EN”> 
style=”font-family:”Arial”,sans-serif”>

style=”text-align:justify;line-height:115%”>
style=”font-family:”Arial”,sans-serif”
lang=”EN”>The date of our next workshop, which will
take place at the 14th RDA plenary in Helsinki, is
fast approaching. Two weeks ago, we shared with you a
survey with the aim to propose a final set of
priorities at our next workshop. We already thank
those of you who responded, we certainly can see that
some trends are emerging.
style=”font-family:”Arial”,sans-serif”>

style=”text-align:justify;line-height:115%”>
style=”font-family:”Arial”,sans-serif”
lang=”EN”> 
style=”font-family:”Arial”,sans-serif”>

style=”text-align:justify;line-height:115%”>
style=”font-family:”Arial”,sans-serif”
lang=”EN”>Yet, as we seek to have priorities to be
accepted by the largest number of people and
communities, we encourage those of you who did not
respond yet to share your opinion about the
prioritisation of indicators [1]. We thank you
in advance for devoting 5 minutes of your time to the
survey and we remind you that no account nor
registration is needed. Please note that, the
survey will be closed the 20th of October
2019.
style=”font-family:”Arial”,sans-serif”>

style=”text-align:justify;line-height:115%”>
style=”font-family:”Arial”,sans-serif”
lang=”EN”> 
style=”font-family:”Arial”,sans-serif”>

style=”text-align:justify;line-height:115%”>
style=”font-family:”Arial”,sans-serif”
lang=”EN”>As a next step towards a common set of
assessment criteria, we started to explore a scoring
mechanism relying on the FAIRness indicators and their
prioritisation. The underlying idea is to assess and
objectively score the implementation level of the FAIR
principles. This idea is currently being discussed on
the GitHub [2]. Please don’t hesitate to comment on
that proposal and suggest any change in the approach.

style=”font-family:”Arial”,sans-serif”>

style=”text-align:justify;line-height:115%”>
style=”font-family:”Arial”,sans-serif”
lang=”EN”> 
style=”font-family:”Arial”,sans-serif”>

style=”text-align:justify;line-height:115%”>
style=”font-family:”Arial”,sans-serif”
lang=”EN”>Lastly, we will soon post the presentation
for the workshop on the RDA FAIR data maturity model
web page. The workshop will be held on the 23rd
of October in the Dipoli Bldg – Kaleva room
during the Breakout 2 from 14:30 to 16:00 local
Helsinki time (11:30 to 13:00 UTC). If you
cannot physically attend the meeting a remote access
is available [3].
style=”font-family:”Arial”,sans-serif”>

style=”text-align:justify;line-height:115%”>
style=”font-family:”Arial”,sans-serif”
lang=”EN”> 
style=”font-family:”Arial”,sans-serif”>

style=”text-align:justify;line-height:115%”>
style=”font-family:”Arial”,sans-serif”
lang=”EN”>Kind regards,
style=”font-family:”Arial”,sans-serif”>

style=”text-align:justify;line-height:115%”>
style=”font-family:”Arial”,sans-serif”
lang=”EN”> 
style=”font-family:”Arial”,sans-serif”>

style=”text-align:justify;line-height:115%”>
style=”font-family:”Arial”,sans-serif”
lang=”EN”>The editorial team
style=”font-family:”Arial”,sans-serif”>

style=”text-align:justify;line-height:115%”>
style=”font-family:”Arial”,sans-serif”
lang=”EN”> 
style=”font-family:”Arial”,sans-serif”>

style=”text-align:justify;line-height:115%”>
style=”font-family:”Arial”,sans-serif”
lang=”EN”>[1]
href=”https://forms.gle/uWXpT27i2RiSei5V7″
moz-do-not-send=”true”>https://forms.gle/uWXpT27i2RiSei5V7
style=”font-family:”Arial”,sans-serif”>

style=”text-align:justify;line-height:115%”>
style=”font-family:”Arial”,sans-serif”
lang=”EN”>[2]
href=”https://github.com/RDA-FAIR/FAIR-data-maturity-model-WG/issues/34″
moz-do-not-send=”true”>https://github.com/RDA-FAIR/FAIR-data-maturity-model-WG/issues/34
style=”font-family:”Arial”,sans-serif”>

style=”text-align:justify;line-height:115%”>
style=”font-family:”Arial”,sans-serif”
lang=”EN”>[3]
href=”https://global.gotomeeting.com/join/708547405″
moz-do-not-send=”true”>https://global.gotomeeting.com/join/708547405
style=”font-family:”Arial”,sans-serif”>

 

style=”font-size:9.5pt;font-family:”Arial”,sans-serif;color:#222222;background:white”>This
e-mail is intended only for the person to whom it is
addressed.

style=”font-size:9.5pt;font-family:”Arial”,sans-serif;color:#222222;background:white”>If
an addressing or transmission error has misdirected this
e-mail,

style=”font-size:9.5pt;font-family:”Arial”,sans-serif;color:#222222;background:white”>please
notify the author by replying to this e-mail. If you are
not

style=”font-size:9.5pt;font-family:”Arial”,sans-serif;color:#222222;background:white”>the
intended recipient you must not use, disclose, copy, print
or

style=”font-size:9.5pt;font-family:”Arial”,sans-serif;color:#222222;background:white”>rely
on this e-mail.

style=”font-size:9.5pt;font-family:”Arial”,sans-serif;color:#222222;background:white”>PwC
may monitor outgoing and incoming e-mails and

style=”font-size:9.5pt;font-family:”Arial”,sans-serif;color:#222222;background:white”>other
telecommunications on its e-mail and telecommunications
systems.

Full post:
href=”https://www.rd-alliance.org/group/fair-data-maturity-model-wg/post/rda-fair-data-maturity-model-invitation-contribute”
moz-do-not-send=”true”>https://www.rd-alliance.org/group/fair-data-maturity-model-wg/post/rda-fair-data-maturity-model-invitation-contribute
Manage my subscriptions:
href=”https://www.rd-alliance.org/mailinglist”
moz-do-not-send=”true”>https://www.rd-alliance.org/mailinglist
Stop emails for this post:
href=”https://www.rd-alliance.org/mailinglist/unsubscribe/65835″
moz-do-not-send=”true”>https://www.rd-alliance.org/mailinglist/unsubscribe/65835

— Siri-Jodha Singh KHALSA, Ph.D., SMIEEENational Snow and Ice Data CenterUniversity of ColoradoBoulder, CO 80309-0449 Phone: 1-303-492-1445 GV: 1-303-736-9976http://cires.colorado.edu/~khalsahttp://orcid.org/0000-0001-9217-5550


Siri-Jodha Singh KHALSA, Ph.D., SMIEEE
National Snow and Ice Data Center
University of Colorado
Boulder, CO 80309-0449 Phone: 1-303-492-1445 GV: 1-303-736-9976
http://cires.colorado.edu/~khalsa
http://orcid.org/0000-0001-9217-5550