John Didion

To summarize, we would add an implicit variable to every task. I propose to call this variable `task` because that's guaranteed not to clash with any existing variable names, since...

All good points. I think I've covered them in the draft PR https://github.com/openwdl/wdl/blob/542-runtime-access/SPEC.md

Yes to task name, `meta` and `parameter_meta`, as those are local to the task. I would leave call name, workflow name, etc as optional, although maybe standardize on the field...

@mlin please change target to `wdl-1.2`

@DavyCats I borrowed the "unwrap" terminology from Rust, which has an `Option` type with a function of that name with exactly the described behavior. Haskell has something similar. Scala and...

That is an option. I like using an array because it doesn't require us to introduce a new custom format. Trying to deserialize a heterogeneous array into anything other than...

@claymcleod this is a great PR, thanks! The only question is where to merge. Historically, our policy has been not to update a spec once it has been released. We...

Moved to `wdl-1.1.2`

@claymcleod Regarding the target branch, maybe there was a misunderstanding. I think we agreed to target `wdl-1.1.2`. Can you please change it back? Otherwise it looks good and I'm prepared...

Made these changes here https://github.com/openwdl/wdl/pull/632 rather than trying to rebase