[Oslc-Automation] Actions 2.0: additional provider constraints reference from Automation Request IP to Fixed Body IP appears to be dangling

[John Arwe]

Changes below are now live 

[1]: enclosed email aka original thread subject - both changes suggested 
by Martin below
[2]: reworked immediate execution dialog response; [2] includes link to 
the related resource shape as the usual spec table  ... ready for review
[3]: added HTTP version 1.1 requirement in bindings, per earlier in-line 
note
[4]: updated spec table for (immediate execution) dialog resource with 
"target probably is a X" statement for oslc:binding, based on current text 
of both specs
[5]: The auto# redirect now serves the correct RDFS (browser users: you 
MUST flush any existing cache to be sure you get it; Poster in FF at least 
WILL pull from cache for a good month - proven by example).  The webmaster 
has now turned off caching for application/rdf+xml and turtle files, 
across the site.  The auto.rdf link is broken; there is a conversation 
started on whether that becomes the current best practice or whether the 
link becomes functional again (if BP changes, we need to point the link in 
the generated HTML to auto#).  If the BP is to leave those links with 404, 
it will go through Core for awareness of the leads so all the vocabularies 
get fixed; otherwise we have nothing more to do, and (once you clear 
caches ... for me, FF's "clear cache" button did not help, had to CTL-F5 
on the .rdf page) you'll either get latest or get 404.


[1] 
http://open-services.net/wiki/core/Exposing-arbitrary-actions-on-RDF-resources/#pattern-autoreq
[2] 
http://open-services.net/wiki/core/Exposing-arbitrary-actions-on-RDF-resources/#Pattern.3A-Delegated-UI-dialog-for-immediate-execution
[3] 
http://open-services.net/wiki/core/Exposing-arbitrary-actions-on-RDF-resources/#Resource.3A-Request
[4] 
http://open-services.net/wiki/automation/OSLC-Automation-Specification-Version-2.1/#Resource.3A-Dialog
[5] http://open-services.net/ns/auto# 

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:   03/18/2014 01:31 PM
Subject:        Re: [Oslc-Automation] Actions 2.0: additional provider 
constraints reference from Automation Request IP to Fixed Body IP appears 
to be dangling



I believe it should be referring to the recognition rule, not "provider 
restrictions". 

In addition, "that resource MUST conform to the requirements placed on 
those resources by the OSLC Automation specification. " should probably 
move to "additional provider constraints", instead of being under the 
recognition rule, as it's not needed for pattern recognition.



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/20140319/87d8559f/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/20140319/87d8559f/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/20140319/87d8559f/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/20140319/87d8559f/attachment.gif>