[Oslc-Automation] State and Verdict Names

[Michael F Fiedler]

The state and verdict values are not class names (which is what the naming
guidance recommends be capitalized) - they are literal values for
enumerations, so I don't think the guidance strictly applies.    A similar
example from core is:

http://open-services.net/ns/core#default

Of course, there are counter-examples as well:

http://open-services.net/ns/core#Zero-or-one, etc

How strongly do you feel they should be capitalized?  Enough to change the
spec given we have implementations?

Since the document referenced is only guidance, my opinion is that
Automation not change anything now and possibly add additional values in
the next revision.

Regards,
Mike

Michael Fiedler
IBM Rational Software
fiedler at us.ibm.com
919-254-4170

"Oslc-Automation" <oslc-automation-bounces at open-services.net> wrote on
01/03/2013 01:17:21 AM:

> Rohit Shetty <rohit.shetty at in.ibm.com>
> Sent by: "Oslc-Automation" <oslc-automation-bounces at open-services.net>
>
> 01/03/2013 01:17 AM
>
> To
>
> oslc-automation at open-services.net,
>
> cc
>
> Subject
>
> [Oslc-Automation] State and Verdict Names
>
> Hi,
>        Why do the state and verdict names start with lower case when the
> oslc resource design guidelines say they should be upper case?
>
> Regards,
>
> Rohit Shetty
> Architect - Manageability Integration, IBM Master Inventor
> Tivoli, Software Group, IBM
>
> [image removed]
>
> Phone: 91-80-41055478 | Mobile: 91-98866-26248
> E-mail: rohit.shetty at in.ibm.com
> Find me on: [image removed]  [image removed]  and within IBM on:
> [image removed]  [image removed]
>
> [image removed]
>
> Embassy Golf Links Business Park, Block B
> Bangalore, Karnataka 560071
> India
>
> _______________________________________________
> 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/20130108/7edc4c7a/attachment-0003.html>