[Oslc-Automation] Regarding oslc_auto:verdict in OSLC automation spec

[Xin Peng Liu]

Hi David & Charles,

I agree with using "error" instead of "erroneous", since usually we use 
"error" to described any abnormal behaviors of IT systems rather than 
"erroneous", and "error" can express like a adjective in similar context 
as others do.


Your sincerely,

XIN PENG LIU (David, 刘昕鹏)
ADVISORY SOFTWARE ENGINEER
Rational Quality Manager Development, IBM China Development Lab


Phone: 86-010-82452825 | Phone: 86-13520163713
E-mail: xinpengl at cn.ibm.com
Chat: David_Box524 at hotmail.com David_Box davidbox.524 at gmail.com 
"No pains, no gains."


8 Dongbeiwang Westen Road
Beijing, Haidian District 100193
China




From:   David N Brauneis <brauneis at us.ibm.com>
To:     Charles Rankin <rankinc at us.ibm.com>
Cc:     oslc-automation at open-services.net, 
oslc-automation-bounces at open-services.net
Date:   2012-09-14 04:23
Subject:        Re: [Oslc-Automation] Regarding oslc_auto:verdict in OSLC 
automation      spec
Sent by:        oslc-automation-bounces at open-services.net



I agree with Charles - I like the changes for pass -> passed, warn -> 
warning, and fail -> failed but would prefer to see erroneous be error. 

Regards,
David
____________________________________________________
David Brauneis
STSM, Rational Software Delivery Automation Chief Architect
email: brauneis at us.ibm.com | phone: 720-395-5659 | mobile: 919-656-0874 



From:        Charles Rankin/Austin/IBM at IBMUS 
To:        oslc-automation at open-services.net, 
Date:        09/13/2012 03:17 PM 
Subject:        Re: [Oslc-Automation] Regarding oslc_auto:verdict in OSLC  
     automation        spec 
Sent by:        oslc-automation-bounces at open-services.net 



oslc-automation-bounces at open-services.net wrote on 09/13/2012 09:34:09 AM:

> From: Xin Peng Liu <xinpengl at cn.ibm.com> 
> 
> I looked through the latest spec, and found for the several values of 
> oslc_auto:verdict, seems not all of them are of the same part of 
> speech, but for oslc_auto:state, the values are consistent to be 
> adjective. I assume values of oslc_auto:verdict should all be adjective
> or noun (better adjective). 

That sounds like a reasonable request 

> If all adjective, then we get: 
> http://open-services.net/ns/auto#unavailable 
> http://open-services.net/ns/auto#passed 
> http://open-services.net/ns/auto#warning 
> http://open-services.net/ns/auto#failed 
> http://open-services.net/ns/auto#erroneous 

I like this version better.  I definitely like changing pass->passed and 
fail->failed.  I'm not keen on "erroneous".  I think that "error", while 
not an adjective, actually reads well and feels better.  If you plug them 
all into the sentence "The automation is in a/an <state> state", they all 
read fine. 

Charles Rankin_______________________________________________
Oslc-Automation mailing list
Oslc-Automation at open-services.net
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net

_______________________________________________
Oslc-Automation mailing list
Oslc-Automation at open-services.net
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120914/c1bcd0b1/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 6419 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120914/c1bcd0b1/attachment-0004.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 543 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120914/c1bcd0b1/attachment-0005.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 525 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120914/c1bcd0b1/attachment-0006.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 550 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120914/c1bcd0b1/attachment-0007.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/20120914/c1bcd0b1/attachment-0001.gif>