Create ODIS FAIR Implementation Profile

[pbuttigieg]

Following the development of FIPs for each WorldFAIR case study / work package, ODIS will create its FIP using the JSON-LD/schema.org conventions.

We do this to avoid lock-in to the nanopublication ecosystem, which uses bespoke semantics that have no mapping to more generic standards. More on the rationale for this decision in Section 4 of Buttigieg, P. L. (2023). WorldFAIR (D11.2) New interoperability specifications and policy recommendations (Version 1). Zenodo. https://doi.org/10.5281/zenodo.10219933.

Relevant background:

• WorldFAIR Project (M3): FAIR Implementation Profile Workshop

[pbuttigieg]

@fils I'll create the JSON-LD/schema.org shell, and use the {{VAR}} tags to identify where query output can be spliced in to periodically autogenerate our FIP.

I'll be using semantics from the FAIR Vocabulary for the principles and sub-principles.

I'll also reference the FAIR Implementation Profile (FIP) Ontology, but I think much of this will be redundant or second-order qualifications of schema.org terms. [Edit: looks like I can embed the questions as question identifiers in AskAction typed values in potentialAction].

[pbuttigieg]

@fils - the shell is ready.

It turns out that the leanest way to do this is to create a CreativeWork record (we could consider Dataset, but something prevents me from applying that type to the KG itself, rather to one of its releases) for the ODIS KG itself, and then encode the FIP questions in an AskAction associated with it. We can now script a query-based response for most of them, some aren't good questions (i.e. they don't actually address the FAIR Principles), so we may add some more or leave some out.

The FIP Ontology links to the FAIR Vocabulary itself, so we don't strictly need to, but it may be worth it for robustness and also to declare where we think a FIP Question is or isn't actually about a FAIR Principle or subprinciple.