-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
75 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
115e74b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The gaia-core container includes the OHDSI Methods Library which is a collection of open source R packages. I am thinking I want to detail this collection in my workflow. That might entail a name, a description and a version number for each member of the collection.
How will the two containers described here integrate with the catalog container? Is that integration pairwise. Like does the catalog container just integrate with the gaia-db container?
You have described the runtime environment that supports container integration a little indicating that it is a network. Can you say anything more about this "network"?
I am not wanting the workflow documentation to go deep. It can with RO-Crate and/or FAIRSCAPE. Instead I am trying to do the documentation in layers beginning with schema.org Actions. I am not inventing this approach. In this approach Action uses an "Instrument" with an "Object" to create a "Result". At least these properties of an Action take "Thing" as the type. Traditionally the thing for the "Instrument" that an Action uses with an "Object" is SoftwareSourceCode. And SoftwareSourceCode includes a property called runtimePlatform. It takes text so the rabbit hole ends. That being said, I need enough understanding to write this text.
Here is an exemplary workflow...