YAML->RDF->YAML won't produce a properly runnable file in some cases

Some ordering is lost in conversion, but this could be fixed by setting @container: @list in the context for these fields: engineConfig and source.

Also, default field can in theory include a map or a list. Not sure how to deal with this. Some options:

• Allow only primitive values for default (no maps, lists or files).
• Require maps and lists to be represented in another way e.g. class: SerializedValue, value: <JSONString>.
• Drop the idea that execution semantics survive loading to RDF graph.

I suggest we temporarily disallow maps and lists for default, and introduce support in future iteration.

[tetron]

Have you written any code that automatically goes from RDF to YAML? I'd like that to be a feature of the schema salad tools, which will make it obvious what actually works and what doesn't.

Ah, no. Guess the title is misleading; the issue is preserving all info when loading to RDF.

I only wrote a PoC-type workflow runner using rdflib when draft2 was being developed. May be worth updating to check if it can be done. Also remember trying to use frames to convert it back but failing (though didn't try too hard).

[mr-c]

Moved to common-workflow-language/cwltool#598