[Oslc-Automation] no cherry picking aka Ian.I.5 - changes are live, please review Carefully

[Martin P Pain]

>From a top-to-bottom read it looks fine. (I haven't looked at the diffs).

Just one note: In Overview -> Domain specific consumers: The 3rd-to-last 
bullet mentions multiple patterns per binding without saying that it 
doesn't happen. (It says "Note: At least one interaction pattern must 
match on a binding for the consumer to be compatible with that binding, 
but it is possible that multiple bindings may match.") I think it's 
probably fine as it is, but did you intend it leave it as-is or was it 
missed?

(The wording is a bit mixed, as it seems to be talking about both multiple 
("at least one") patterns per binding and also about "multiple bindings" 
being viable choices for a given consumer... but both of which are 
correct, so I don't propose we change it).

(I have other notes from my top-to-bottom read that I'll send separately).

Martin




From:   John Arwe <johnarwe at us.ibm.com>
To:     oslc-automation at open-services.net
Date:   12/09/2014 20:42
Subject:        [Oslc-Automation] no cherry picking aka Ian.I.5 - changes 
are live,       please review Carefully
Sent by:        "Oslc-Automation" 
<oslc-automation-bounces at open-services.net>



[1], [2], [3] have the changes integrated now.  I discovered that even 
without allowing cherry picking, there is at least one case where a single 
binding can match >1 IP; consequently not quite all of the weaseling was 
removed, and where it remains I articulated the case ... both for scrutiny 
and to say that we're not actually doing it in practice at this point, so 
it's more of a theoretical concern. 

Several other small fixes have also been made to the live copy.  Things I 
discovered while drafting Ian.I.5. 
1: The prose mentioned oslc:usage = default on bindings, but oslc:usage 
was not in the corresponding table for http:Request binding resources.  I 
added it 0:* 
2: We copied ParameterInstance from Automation and left rdf:value 0:* 
although our only use of it is 1:1.  I made it 1:1. 

Given how delicate these cherry picking changes were, I saved a 
before/after copy of the raw wiki text in case anyone wants a "just diffs" 
view; files attached here.  Doing this helped me catch at least one miss. 


0947 = before, 1329 = after ... approximate timestamps.  They won't 
exactly match the live copy any more, as I've since made a few more edits 
to tie up other loose ends.  You can use the History link off any page to 
pull your own copies if you want something with ALL the changes, including 
the small ones I just made at 1540. 

[1] 
http://open-services.net/wiki/core/Exposing-arbitrary-actions-on-RDF-resources/ 
spec 
[2] 
http://open-services.net/wiki/automation/OSLC-Automation-Specification-Version-2.1/ 
 wafer thin change: add finalStatusLocation to recognition rule; was 
already in text 
[3] http://open-services.net/wiki/core/Actions-2.0-Examples/  the "worked 
examples" 2 and 3 needed 1 binding split into 2 
Best Regards, John

Voice US 845-435-9470  BluePages 
Cloud and Smarter Infrastructure OSLC Lead [attachment 
"Actions1329wiki.txt" deleted by Martin P Pain/UK/IBM] [attachment 
"Actions0947wiki.txt" deleted by Martin P Pain/UK/IBM] 
_______________________________________________
Oslc-Automation mailing list
Oslc-Automation at open-services.net
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net



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