Open ljgarcia opened 9 months ago
input
and output
were proposed for the ComputationalWorkflow
profile and later adopted as well by the ComptutationalTool
profile. input
and output
are of type FormalParameter
so (my understanding) they are meant to represent an abstraction rather than an actual thing. Making a parallel to functions and function calls, FormalParameter
is a parameter used when defining the workflow/tool, not an argument used when the workflow/tool is actually used.
@nsjuty could you please follow up with ComputationalWorkflow
group? You could also make the liaison with RO-Crates so we find out the way to go (hopefully a compatible way for both communities). Thanks.
@ptsefton, thanks for suggesting the reuse of object
and result
schema.org properties. Since these properties have for range Thing
, I don't see anything againts refering to an instance of FormalParameter
. So it would be ok for me to update the Bioschemas profiles with these schema.org properties.
The semantics would be a bit different since in Computational{Tool,Worflow} profiles, we focus on tool/workflows specifications and not their execution. My understanding of CreateAction
is that it's more related to provenance metadata (what is actually done on a thing).
@stain, what is your opinion on the ComputationalWorkflow side ?
Original message by @ptsefton at https://github.com/BioSchemas/specifications/issues/653#issuecomment-1740468713