[Oslc-Automation] Automation spec updated based on synchronous/asynchronous discussion - plus 1 issue

[Michael F Fiedler]

The Automation specification has been updated with the proposed language
(Option 4) describing asynchronous and synchronous interactions and
comments are requested from the community.   Sections to review are the
description of service provider capabilities [1], query capabilities [2]
and the HTTP method table [3] which has reverted to its previous content.

One issue was raised around status codes and the Location header for the
synchronous case.   In this case the Automation Result is returned in the
POST response to the Automation Request and there may not be a
reference-able artifact created by the POST.   The HTTP spec [4] states
that in this case the status code is expected to be 200, not 201.  Do we
need to state anything explicit in the specification regarding this?  or do
we just default to HTTP norms of behavior?

[1] -
http://open-services.net/bin/view/Main/AutoSpecificationV2#Automation_Service_Provider_Capa
[2] -
http://open-services.net/bin/view/Main/AutoSpecificationV2#Query_Capabilities
[3] -
http://open-services.net/bin/view/Main/AutoSpecificationV2#Automation_Service_Provider_HTTP

[4] - http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.5

Regards,
Mike

Michael Fiedler
IBM Rational Software
fiedler at us.ibm.com
919-254-4170
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120618/6e6017dc/attachment-0003.html>