In last Thursday's automation workgroup meeting we discussed the recent mailing list thread [1] on the possible need for an outputParameter (or perhaps other name) attribute on Automation Requests. Pramod agreed to consider documenting a scenario he had thought of on the list for consideration. Some of the points from the workgroup meeting were:
- It is understood that the purpose of the outputParameter attribute on the Result is a means recording what parameters went into producing the result without saying anything about when they were introduced. - it is understood that a provider could add such an attribute itself, even if not defined in the spec, if it is useful for its scenarios. Drawback would be generic consumers might not look there for it. - the scenario around using an attribute in the Request as a placeholder or means of carrying parameters across the execution was probably not sufficient in itself. But Pramod had put some thought into future chaining or composite automation where it may be useful or required and will document. If anyone else has scenarios around this where you feel having outputParameters (or some attribute to hold new/changed parameters on the request), please bring them up on the list. [1] - http://open-services.net/pipermail/oslc-automation_open-services.net/2012-October/000326.html Regards, Mike Michael Fiedler IBM Rational Software [email protected] 919-254-4170
