OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Created: (ENERGYINTEROP-379) Use of "Type" inthe naming convention


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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]