Representing conditional execution about workflow-run-crate HOT 7 CLOSED

Sine this RO-Crate profile is about a particular enactment of a workflow, then it might be simpler to not model the condition.

As a bonus, I guess one could record the decision to skip a step. For CWL that would require the CWL document and the input object for that workflow step, then one could investigate the JavaScript statement that was evaluated and found to produce a False (== skip) result. For CWL steps that weren't skipped, the step input object should already be represented allowing a similar analysis post-run of the decision by a human evaluating the JavaScript statement.

from workflow-run-crate.

This is related to #15. However, there is no SkippedActionStatus on schema.org. Maybe we need another field? Or we can use the PotentialActionStatus with that meaning?

from workflow-run-crate.

It depends on the workflow language if conditional execution means the step is run or the datalink is rewired - presumably some evaluation happens though. Is that part of the ControlAction with no tool invocation?

Or would it be an AssessAction that could end up with either subclass IgnoreAction or ChooseAction? Might get quite elaborate as you would then as object of those have what was evaluated rather than what inputs were potentially going to be used.

{
  "@context": "https://schema.org",
  "@type": "IgnoreAction",
  "agent": {
    "@type": "Person",
    "name": "John"
  },
  "object": {
    "@type": "BefriendAction",
    "agent": {
      "@type": "Person",
      "name": "Steve"
    },
    "instrument": {
      "@type": "WebPage",
      "url": "https://www.social.com"
    }
  }
}

from workflow-run-crate.