Add default metadata fields #214
And document its use.
By default, the following is assumed in every draft-4 CWL document unless overridden by the user
I don't think the RO ontology, which deals with aggregation and annotations, makes sense for metadata. We re-use existing vocabularies, e.g. using a JSON-LD context that maps to existing vocabularies like ORE, PROV, PAV, etc.
What would make more sense is to select certain provenance properties, e.g.
Using http://schema.org/ terms for project definition probably makes sense, but it's a bit too weak for my liking for provenance, e.g. if a tool description JSON was downloaded from somewhere, I would want to see that stated explicitly with pav:retrievedFrom (if the file is the same), or pav:importedFrom a resource in a different form (e.g. a http://bio.tools/ page), or pav:derivedFrom if further edits have been done.