[Oslc-Automation] outputParameter vs. hasContribution in response

[Joe Ross]

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, joeross at us.ibm.com
Tivoli Autonomic Computing & Component Technologies
512-286-8311, T/L 363-8311
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120823/0730ad11/attachment-0003.html>