[Oslc-Automation] Automation Plan parameters - in vs out

[John Arwe]

My implementers are unclear as to how they should differentiate between 
input and output parameter definitions from the content at [1]. 
Given all our iterations/gyrations on the calls, I confess I'm no longer 
sure how to do so either. 
I suppose we might re-use oslc:readOnly for this (if it is r/o from the 
perspective of the Plan implementation, that's an input property, and the 
converse), but that seems pretty dicey and prone to conflict when a 
parameter definition is re-used in multiple contexts.  It seems more 
likely to be a property of the usage of a parameter within the context of 
a given Plan (and potentially implementation).


[1] 
http://open-services.net/bin/view/Main/AutoSpecificationV2?sortcol=table;up=#Resource_AutomationPlan


Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli OSLC Lead - Show me the Scenario
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120405/cc4a89eb/attachment-0003.html>