--- http_interactions: - request: method: get uri: https://donnywinston.com/posts/implementing-the-fair-principles-through-fair-enabling-artifacts-and-services body: encoding: ASCII-8BIT string: '' headers: Connection: - close Host: - donnywinston.com User-Agent: - http.rb/5.1.1 response: status: code: 301 message: Moved Permanently headers: Accept-Ranges: - bytes Age: - '1' Cache-Control: - public,max-age=0,must-revalidate Content-Length: - '17399' Content-Type: - text/html; charset=UTF-8 Date: - Thu, 05 Oct 2023 19:47:46 GMT Etag: - '"134a1cd21902b5c1e8c1573920e09a2e-ssl"' Location: - "/posts/implementing-the-fair-principles-through-fair-enabling-artifacts-and-services/" Server: - Netlify Strict-Transport-Security: - max-age=31536000 X-Nf-Request-Id: - 01HC0P3GPE9SN8JV87J6RA5M3J Connection: - close body: encoding: UTF-8 string: |- Implementing the FAIR Principles Through FAIR-Enabling Artifacts and Services | Donny Winston

Implementing the FAIR Principles Through FAIR-Enabling Artifacts and Services

How does a Research Software Engineer (RSE) — often responsible for developing infrastructure to manage and share digital research objects (data, models, code, notebooks, workflows, etc.) — get from “Yes, FAIR sounds great, but how?” to “I better understand what the FAIR principles really mean and how I can put them into practice.”? I hope the diagram below can help.

Relating FAIR-Enabling Resource artifacts, from the FAIR Implementation Profile (FIP) ontology, to services. These services are what you deploy to implement each of the 15 FAIR Principles (from Box 2 of the seminal publication) for any actual given digital research object.

recorded_at: Thu, 05 Oct 2023 19:47:46 GMT - request: method: get uri: https://donnywinston.com/posts/implementing-the-fair-principles-through-fair-enabling-artifacts-and-services/ body: encoding: ASCII-8BIT string: '' headers: Connection: - close User-Agent: - http.rb/5.1.1 Host: - donnywinston.com response: status: code: 200 message: OK headers: Accept-Ranges: - bytes Age: - '0' Cache-Control: - public,max-age=0,must-revalidate Content-Length: - '17399' Content-Type: - text/html; charset=UTF-8 Date: - Thu, 05 Oct 2023 19:47:46 GMT Etag: - '"134a1cd21902b5c1e8c1573920e09a2e-ssl"' Server: - Netlify Strict-Transport-Security: - max-age=31536000 X-Nf-Request-Id: - 01HC0P3HBY5PMCW18MHJ81WKZ3 Connection: - close body: encoding: UTF-8 string: |- Implementing the FAIR Principles Through FAIR-Enabling Artifacts and Services | Donny Winston

Implementing the FAIR Principles Through FAIR-Enabling Artifacts and Services

How does a Research Software Engineer (RSE) — often responsible for developing infrastructure to manage and share digital research objects (data, models, code, notebooks, workflows, etc.) — get from “Yes, FAIR sounds great, but how?” to “I better understand what the FAIR principles really mean and how I can put them into practice.”? I hope the diagram below can help.

Relating FAIR-Enabling Resource artifacts, from the FAIR Implementation Profile (FIP) ontology, to services. These services are what you deploy to implement each of the 15 FAIR Principles (from Box 2 of the seminal publication) for any actual given digital research object.

recorded_at: Thu, 05 Oct 2023 19:47:46 GMT recorded_with: VCR 6.2.0