You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Crate MUST contain a data entity of type ["File", "SoftwareSourceCode", "ComputationalWorkflow"] as the Main Workflow.
This could be interpreted as saying that the types must be exactly ["File", "SoftwareSourceCode", "ComputationalWorkflow"], while WorkflowHub actually allows for more types to appear on the list. This is required by the Provenance Run Crate profile (which adds HowTo), so I propose we change the spec as follows:
The Crate MUST contain a Main Workflow data entity whose types MUST include File, SoftwareSourceCode and ComputationalWorkflow.
The text was updated successfully, but these errors were encountered:
I'm wondering what the best-practice way of changing this is now we have the versioned spec. Do you think it would be a breaking change to implementers? I guess possibly, if they are looking for the exact 3 terms to identify something as a main workflow...
Yes, it's potentially breaking in case anyone is doing such a strict check, however unlikely. So the profile's version should change to 2.0.
In any event, it's very important that WorkflowHub keeps allowing the extra types as it does now, even with the current spec, so that Provenance Run Crates can be uploaded to the registry.
The current spec says:
The Crate MUST contain a data entity of type
["File", "SoftwareSourceCode", "ComputationalWorkflow"]
as the Main Workflow.This could be interpreted as saying that the types must be exactly
["File", "SoftwareSourceCode", "ComputationalWorkflow"]
, while WorkflowHub actually allows for more types to appear on the list. This is required by the Provenance Run Crate profile (which addsHowTo
), so I propose we change the spec as follows:The Crate MUST contain a Main Workflow data entity whose types MUST include
File
,SoftwareSourceCode
andComputationalWorkflow
.The text was updated successfully, but these errors were encountered: