[Oslc-Automation] OSLC Actions: Action for resource that does not yet exist: worked example

[John Arwe]

Having just searched...

1: Correct (and unsurprising) to say we've not spec'd any way to initiate 
execution of a templated request.
2: I don't see text allowing them to be cleaned up "quickly", which I 
thought we had in here already.
3: I don't see any mention of the oslc:usage value for templates, did we 
scrap that entirely in favor of TemplateDialog as a type?
4: wrt #1, we should consider if that's a gap.  If I wanted to emulate a 
client-centric reader, you also haven't told me that updating its state to 
queued/etc Must Not have the desired effect.

Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli OSLC Lead - Show me the Scenario




From:   Martin P Pain <martinpain at uk.ibm.com>
To:     John Arwe/Poughkeepsie/IBM at IBMUS, 
Cc:     oslc-automation at open-services.net, "Oslc-Automation" 
<oslc-automation-bounces at open-services.net>
Date:   01/30/2014 12:44 PM
Subject:        Re: [Oslc-Automation] OSLC Actions: Action for resource 
that does not yet exist: worked example



> It will never be executed *in this 
> scenario*, because... *and the client will never change its state to
> make it eligible for execution*. 

The client cannot change its oslc_auto:state to make it eligible, as its 
oslc_auto:state is already set to oslc_auto:new, as that is what the 
provider wants submitted to the creation factory. There is no spec'd way 
to make this exact request resource (at this exact URI) eligible for 
execution. The provider has decided that this resource is not eligible for 
execution (because it was created by a template dialog), and it has not 
exposed this in the data as there is no way allowed by the spec to 
advertise this in the data. Therefore there is nothing about the data that 
can be changed to make it eligible for execution. There's nothing to stop 
the provider doing something provider-specific, but what I'm wanting to 
get across is that this is non-eligible, and that there is no spec'd way 
to make it eligible.

For now I've changed it to "This Automation Request resource itself is not 
eligible for execution", which hopefully covers both our points. (Although 
I'm not sure we introduce the term "eligible for execution" anywhere. 
Perhaps we need to include in in the Auto spec's discussion of template 
dialogs. 

All other suggestions are good, I've edited the page to include them. 
Thanks. 

Martin Pain
Software Developer - Green Hat
Rational Test Virtualization Server, Rational Test Control Panel
Open Services for Lifecycle Collaboration - Automation WG joint chair 

E-mail: martinpain at uk.ibm.com
Find me on:  and within IBM on:   




IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU 


Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140130/211399ec/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 518 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140130/211399ec/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1208 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140130/211399ec/attachment-0001.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 360 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140130/211399ec/attachment.gif>