[Oslc-Automation] Core Actions - move content into appendix A?

[John Arwe]

I see this excerpt in a few places, I think always "right" after a link to 
appendix A.  It made me wonder/conclude if they should just move into that 
appendix (and then I'll wordsmith it a bit).
- I'd replace the should with an explicit deferral to HTTP + the norm.
- I'd hyperlink Automation (to 2.0)

I'm willing to do it, just want to make sure it's not separated for some 
reason I'm missing.


The response to this request SHOULD be 200 to indicate that the action has 
completed, or 201 or 202 to indicate that the request has been queued and 
will be dealt with at a later time, or a 4xx or 5xx status code to 
indicate failure.
Note: If returning a 202 HTTP status code, the HTTP specification suggests 
returning a monitor to track the status of the execution. It is 
recommended that if OSLC providers use the 202 status code that they 
consider using the OSLC Automation Specification’s Automation Request or 
Automation Result resource as such a monitor.


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/20140113/e9c888fc/attachment-0003.html>