Francisco Javier Tirado Sarti

I think it will be better to introduce a URI reference construct in the spec and there, rather than using all type of expressions, be able to specify the values...

you can argue, accepting the $PROPS reserved word to narrow down possible values to parsing time, that this should be supported ``` { "name" : "send-email", "operation" : "https://{$PROPS.}/openapi.json#sendMail"} ```...

I would say (as @ricardozanini before) that a variable spec location case does not really fit in the workflow spec target use case set. I think it is a fair...

I vote for same functionality than dataInputSchema, thats it, by default the output is validated againts the output shema if present. If not valid, an error is thrown.

@tsurdilo I agree with your concerns, but for these use cases, you just avoid specifying an output schema (or include it for documentation purposes and set validateOnError to false). I...

@cdavernas Implementing $CONST in jsonpath properly was not straighforward. Although that is a proper language construct for a variable in jq, the proper language construct for jsonpath will be @.CONSTANT...

Regarding jsonpath, as far as I know, is still supported by the spec (although fortunately is not the default one anymore), but my point is that a user of the...

> Oh ok! Yeah the jq vs jsonpath vs ... is yet another discussion, but yeah, of course, any and all implementations are/should be allowed. I really never intended to...

Do we have a use case for sleep? Im asking because Ill remove sleeps altogether. We should wait for something, not a random amount of time.

Assuming we have to wait a random amount of time after an action has been executed and before another action is executed, I would add the sleep as an optional...