PROV DM- PR preparation -second iteration
Activity Description Package
In order to push forward the Activity Configuration discussion, I have attached a last version of the class diagram below.
Documentation of the class diagram:
Using the Parameter class allows to list the values read by an activity to parametrize its execution.
Each Parameter instance is identified by its name and can be queried.
A Parameter is a specific class. In contrary to ValueEntity it does not hold all the relations an Entity may have :
• no wasAttributedTo --> Agent link
• no hadMember--> Activity link
• no Used --> Activity link
• no wasGeneratedBy --> Activity link
If a Parameter value is chosen with respect to a Result Entity R, computed on purpose to generate this configuration value, or just reused from a previous excecution, then the Parameter Instance may have a wasInfluencedBy relation to this Result Entity R. This Entity R is then described in the system with the usual Entity links wasGeneratedBy and the Activity generating this value may also be described. The WasInfluencedBy relation is part of the relations defined in the vo-dml list of relations (College Park version).
This allows Parameter instances to be totally focused on the Configuration part of the Provenance DM, but still be able to trace the origin of their value.
The description of this parameter is stored in the ParameterDescription instance, which is connected via a Parameter --> ParameterDescription link, a Subset of Entity --> EntityDescription link.
Identified and dedicated access to the configuration information allows to trace and interpret the quality of the activities/result entities more efficiently than sorting between Entity types and Used relations types.
It suits to the life cycle of a Parameter instance which is the same as its related Activity.
Would an Activity instance A be deleted from the database, all Parameters instances bound to it would also be deleted, while the Entities instances consumed by A still pervades into the database as it may be used by another task/activity.
To represent the semantics and encoding of the configuration values entered to run an activity distinguished from the datasets consumed and produced. A Parameter can be queried, on its value and on its description.
The values used to control the activity are either contained into a Configuration file , which contains a key=value list .
This resource is stored as an Entity of type = Document.
The mechanism to search a value into this Document is managed by the project providing the Provenance information, usually using contextual text search.
This method needed to explore the ConfigFile content is outside the scope of this model.
- Activity Configuration package and its relation to the IVOA Prov DM:
- class diagrams with independent parameter class/ no more derivation:
- class diagram with the description links from Execution part ( left classes ) to Description part (right part)