[OASIS Issue Tracker] Commented: (ENERGYINTEROP-379) Use of "Type"in the naming convention

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

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

Gerald Gray commented on ENERGYINTEROP-379:
-------------------------------------------

I kept waiting for this to be discussed or covered as an agenda item when we went through issues.  Somehow it never made the cut.  

Clever use of delaydelay to ignoreignore something that is dumbdumb.  

I have filed this under "Harmless but stupid".  Closing.

> Use of "Type" in the naming convention
> --------------------------------------
>
>                 Key: ENERGYINTEROP-379
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-379
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>          Components: schema
>    Affects Versions: wd22
>         Environment: Gerald Gray
>            Reporter: Gerald Gray
>            Assignee: William Cox
>
> Ei Enroll - In some places the "Type" suffix appears to make sense, e.g. ResourceGenerationType where perhaps a distinction is being made among different types of resources, however, in some places it is somewhat confusing e.g. ResourceTypeType. (Would this indicate where an enum would be used?)
> Is there a naming convention here to distinguish complex types in the schema with the "type" suffix?

-- 
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