Skip to content

Section 6.7: CIM Model Manager consensus needed #35

@tviegut

Description

@tviegut

In reference to the introductory paragraph below:

Enumeration literal names should follow the same rules as attribute names (Section 5.4.7), except in case some established conventions exist, e.g. SI unit symbols or currencies

Kendall Demaree commented:

I do not agree. We should stick to a form that fits tools. The SI units have already been changed into tool friendly names. These cases are relatively rare and the documentation can compensate for any limitations in expressing SI unit names exactly.

[tk] here is where initial value or alias in literal can be useful.

[kd] Need global agreement on a specific use of alias. Yes, it would make sense to have programmatic form and more friendly textual form not restricted with programming conventions. i want to make sure we can use typical enum expressions in java or C++ just like we restrict names on classes or attributes for these implementations.

Update 2013-05-15 [tk]: I agree with you on this one ! Exceptions meant are about the upper case / lower case convention. E.g., "USD" as currency, it starts with upper case letter (where it should be lower case letter). Similar for e.g. "T", like for Tesla in units or "G" for giga in multipliers; according to our naming rules, it should be "t" / "g", and it's wrong.

Metadata

Metadata

Assignees

No one assigned

    Labels

    cim mm consensus neededCIM Model Manager consensus neededdocumentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions