Determine how to add a problem specification to the RO-Crate

[wd15]

The Workflow Run RO-Crate infrastructure currently (to the best of our knowledge) does not support an entity that describes the reason for the RO-Crate. For simulation output this would related to the problem definition or problem specification. For a more general RO-Crate, this might be some sort of motivation for its existence.

The head node for an RO-Crate is a "DataSet", but his could possibly have two types if an appropriate type can be identified, but we probably need to remain within the confines of Workflow Run RO-Crate standards.

This question should be asked on the Workflow Run RO-Crate discussion channel.

[wd15]

After some discussion with @ztrautt it seems there are some options for this. There are three fields in CreativeWork that might serve this purpose,

• about
• isBasedOn

This field would appear in the top level ./ entity and point to another CreativeWork (which is a superset for DataSet), which is the problem definition. The keywords field would then have list of our DefinedTerms to pin down the phase field problem category and/or any other categorization such as application or material related keywords.