[Oslc-Automation] Final changes (hopefully) for Actions spec: desiredResult -> finalStatusLocation

[John Arwe]

> 4. I allowed multiple values for oslc:finalStatusLocation ([1], [2]), in 
case the final status is reflected in more than one place (to allow future 
interaction patterns to aid 

Just make sure this doesn't open up the door to mixing single and 
multi-message IPs.  I don't remember if there was additional text at this 
point ... IIRC there's a non-normative "there be dragons" warning, if that 
survived it's probably sufficient - it's not like we have an iron-clad 
proof that they cannot ever be mixed (although we're getting close), but 
we have articulated specific cases where doing so causes conflicts.

While I'm here: regrets for this week's meeting, at W3C F2F

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/20140416/8b44195e/attachment-0003.html>