[OASIS Issue Tracker] Commented: (ENERGYINTEROP-350) enumerationattribute names are not consistent; should all be UpperCamelCase

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25196#action_25196 ] 

Toby Considine commented on ENERGYINTEROP-350:
----------------------------------------------

If we are talking about Enumeration Values of foo, then they should be all UpperCamel, and we can follow Token rules
If we are talking about fooEnumeration, the element name in an event message is lowerCamel
If we are talking about the type that contains enumeration, its name is FooEnumerationType, UpperCamel

> enumeration attribute names are not consistent; should all be UpperCamelCase
> ----------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-350
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-350
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>          Components: model, schema, spec
>    Affects Versions: wd22
>         Environment: William Cox
>            Reporter: William Cox
>            Assignee: Toby Considine
>
> The naming convention for the attributes (values) of an enum need to be typographically consistent across EMIX and EI (at least).
> Most of these are UpperCamelCase. 
> For example, EiConstraintBehavior is all caps and should be UpperCamelCase.
> This mirrors issue EMIX-314

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira