Description
This is a very high level idea, might be worth separate grant/development. To a degree described on https://github.com/con/external-services and implemented "in parts" separately e.g. in https://github.com/dandi/dandi-archive/blob/1312714be91c3a8c43116073bbf39f9477e56b04/web/src/views/FileBrowserView/FileBrowser.vue#L332 .
Although "Actionable" is not a part of original FAIR, and I didn't research into the "FAIR offsprings", I think such development would largely align with FAIR principles as to facilitate AIR components: there is a growing number of external services which could operate on FAIR resources, quite often directly in the browser client. That facilitates building modular and composable platforms without requiring tight integration and increase of development headaches. E.g. our visitors of https://dandiarchive.org/ can easily operate/visualize/explore/analyse files in the archive by following into external registered services. E.g.
- go to https://dandiarchive.org/dandiset/000026
- on the right click "Open With" -> "Neurosift" and navigate / explore data on neurosift.
- we also provide similar integrations at individual file levels, e.g. go to https://dandiarchive.org/dandiset/000026/draft/files?location=sub-I45%2Fses-MRI%2Ffmap&page=1 and then for .nii.gz files you could "Open With" Bioimagesuite/Viewer.
So I wondered to see WDYT on a potential to register services which would be associated with standards and potentially prescribe endpoints to operate on.