[Oslc-Automation] OSLC Actions: Dialog for later execution interaction pattern - moved to Automation

[John Arwe]

> someone suggested a different name for them, but I've forgotten what
> that was. ...

IIRC: immediate execution bindings

I did a top-to -bottom read of Core-Actions this morning, seems to be 
coming along nicely.  There's some editorial stuff I'll try to knock off 
this afternoon ET (to reduce the odds of a collision) so you can diff them 
in the morning.

Q1: in the resource shape interaction pattern, we say that the client 
serializes the RDF in an "appropriate" format.  I don't think it gives the 
client any way to find out what constitutes "appropriate" though.  My 
thinking was that we say the provider has to offer a representation 
(including the binding data) using a format it supports for input; we'd 
either use the existing header mechanisms to assert its content type, or 
invent new if necessary.  I.e. a client happy to take the defaults could 
just "copy" the contents of :contentAsRdf, copy the Content type header, 
done.  I'm only concerned with that minimum sort of baseline; if the 
provider accepts others and the client wants to introspect at run time, 
all the HTTP substrate can be used.  "with RDF body" has some words around 
this that could be re-used, and/or re-factored into the appendix.

Q2: [having read Only the Core piece so far] it was moderately surprising 
to see the Creation Factory IP point off to Automation; CF's are part of 
Core, that sort of thinking.  Core-Actions for CFs and Automation-=Actions 
for templates is what I expected coming in.

I have to prep for W3C mtg now, so I'll come back to the "do we need that 
level of indirection" question later today.  I think that's the only 
big-animal one open (jog my memory if there are others), but I wanted to 
queue up the bits above before you left for the day.


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