hasContribution is intended for "real" output of the automation. Examples might be build binaries, log files or test execution results. outputParameter is intended to capture the parameters or environment variables which were used to produce an Automation Result. There was a somewhat late change in direction in which the workgroup decided the scope of outputParameter is: all inputParameters (whether modified or unmodified) plus any parameters added/created during the execution.
So, a hasContribution is a product of the automation execution and an outputParameter is meta-data related to the execution of the automation. Let us know if that does not clarify things. Regards, Mike Michael Fiedler IBM Rational Software [email protected] 919-254-4170 [email protected] wrote on 08/23/2012 07:15:39 PM: > Joe Ross/Austin/IBM@IBMUS > Sent by: [email protected] > > 08/23/2012 07:15 PM > > To > > [email protected], > > cc > > Jason Todoroff/Austin/IBM@IBMUS, Denilson Nastacio/Raleigh/IBM@IBMUS > > Subject > > [Oslc-Automation] outputParameter vs. hasContribution in response > > We implemented an early draft of the spec that did not have > outputParameter, so we used hasContribution to store our output > parameter values. Looking at the latest draft, it looks like we > should probably change this to use outputParameter. It's not really > clear to me why hasContribution is still there, and what it should > be used for, but I'm used to the concept of input/output parameters, > and that seems the most natural place to put the result information. > Is that the intent? > > ================================================ > Joe Ross/Austin/IBM, [email protected] > Tivoli Autonomic Computing & Component Technologies > 512-286-8311, T/L 363-8311_______________________________________________ > Oslc-Automation mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-automation_open-services.net
