[Oslc-Automation] Core Actions updates

[John Arwe]

I have updated Core Actions with the content noted at [1].  The templates 
section is just above [3] (templates is now final topic in overview) if 
anyone would care to sanity-check it.

I also see that when we resolved issue 8 [2] during [1] with "strongly 
RECOMMENDED", we were unaware of existing text at [3] specifying a MUST 
for what I think is the same statement.  So we need to settle on one 
value.

In [4], the final bullet of the first list seems completely out of 
place/does not apply to consumers.  Do we really have to tell producers to 
use HTTP at this point?

In [4], the text beginning as follows seems ripe for deletion based on our 
last meeting's resolution allowing arbitrary media types in 
representations: Note: If OSLC implementors want to specify literal HTTP 
request bodies, e.g. for `text/plain` or binary data...

I gave it a top-to-bottom read without finding any glaring holes.  Seems 
like we need to scrub the issues page and red text notes to see what's 
really still open.  What do we want to do about diagrams?


[1] http://open-services.net/wiki/automation/AutomationMeetings20140123/
[2] http://open-services.net/wiki/core/Actions-2.0-Issues/
[3] 
http://open-services.net/wiki/core/Exposing-arbitrary-actions-on-RDF-resources/#Re-use-by-domain-specifications
[4] 
http://open-services.net/wiki/core/Exposing-arbitrary-actions-on-RDF-resources/#constructing-http-requests

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/20140128/ad8f8842/attachment-0003.html>