[Oslc-Automation] New Automation 2.0 spec problem using verdict=incomplete which is not defined

[John Arwe]

[1] says (final sentence of paragraph) "An automation result is “finished” 
when it has an oslc_auto:state predicate with an object of 
oslc_auto:complete or oslc_auto:canceled or an oslc_auto:verdict property 
with a value other than oslc_auto:incomplete. "  We've referred to this 
definition "a few" times in the 200/201 interaction pattern discussions.

The problem is, our vocabulary lacks oslc_auto:incomplete.  We might be 
able to troll old versions to see if this is a rename issue; [2]'s list 
makes me think we might have renamed "incomplete" to "unavailable" at some 
point and missed [1].  I know a couple of us were madly drafting wildly 
varying versions of [1] on other pages for a while, so if an incomplete 
rename was properly reflected (in the then-current spec content) and then 
later the final version of [1]'s paragraph was copied in, there we go.




[1] 
http://open-services.net/wiki/automation/OSLC-Automation-Specification-Version-2.1/#Automation-Service-Provider-Capabilities
[2] 
http://open-services.net/wiki/automation/OSLC-Automation-Specification-Version-2.1/#State-and-Verdict-properties


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