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

[John Arwe]

> > I'm agnostic on which choice we make, functionally.  My inner 
> > minimalist leans towards pointing in text to Core, done. 

> ... would you be happy for us to just exclude the 
> finalStatusLocation from the deferred dialog binding? 

I would lean toward the explicit ptr to Core.  This occurs in the context 
of a spec (Automation) where other (non-deferred) dialogs that create 
Automation Requests expect the client to take different (additional) 
actions in the case of a successful create - search for a corresponding 
Result, and look *at that* for blah blah.  Those additional actions, if 
mistakenly applied to a deferred dialog's output, would lead to a client 
hang (no Result ever appears, or if it's bundled with the Request it never 
changes into 'finished' state).

But I can live with either the explicit ptr or silence.


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/20140417/c33d5b2a/attachment-0003.html>