Replies: 1 comment
-
As a stab at what might not be automatically derivable, the ShEx spec refers to a FAIRDataTeam schema for FAIR. I'm not sure how complete it is intending to be in comparison to the resource you name.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There is a proliferation of FAIR checklists. These usually involve someone going through and manually answering questions on a form, enumerating questions about things like which standards are followed. This is often time-consuming and usually incomplete for large projects because it's hard for one person to hold all this in their head - and likely to become out of date.
E.g. FIP has the following Qs:
Some questions like I2 can be answered programmatically, looking at uris and mappings as well as value sets/enums. Others may be out of band for the schema, although in some cases we may want to encourage more schema-level metadata that describes the information ecosystem the schema is intended for.
F1 could be answered by introspecting whether
identifier
is declared, what the range is, and what constraints are on that range.It looks like FIP has an RDF serialization, in principle it should be possible to have a simple linkml tool that would partially populate a FIP - or perhaps just a TSV output is sufficient.
I think this would be beneficial as it would lower the barrier to continuous evaluation of FAIRness metrics, rather than this be a one-off box checking exercise that rapidly becomes incomplete and stale.
Beta Was this translation helpful? Give feedback.
All reactions