Good catch. I updated the type and aligned the description a bit more with 'state'.
Regards, Mike Michael Fiedler IBM Rational Software [email protected] 919-254-4170 Paul McMahan/Raleigh/I BM@IBMUS To Sent by: [email protected], oslc-automation-b cc ounces@open-servi ces.net Subject [Oslc-Automation] value type for AutomationRequest / desiredState 09/11/2012 05:06 PM The spec defines the 'desiredState' property of AutomationRequest[1] as having value type String. The 'state' property is defined as having value type AnyResource. The values for the state property are defined as URIs [2]. Since the value of a 'desiredState' property needs to correspond to a URI for the 'state' property, shouldn't both 'desiredState' and 'state' have value type AnyResource? Best wishes, Paul McMahan IBM Rational [1] http://open-services.net/wiki/automation/OSLC-Automation-Specification-Version-2.0/#Resource_AutomationRequest [2] http://open-services.net/wiki/automation/OSLC-Automation-Specification-Version-2.0/#State-and-Verdict-properties _______________________________________________ Oslc-Automation mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-automation_open-services.net
