[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (ENERGYINTEROP-299) Need betterconsistency in the notion of an ID versus a name (line 892)
[ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23881#action_23881 ] Bruce Bartell commented on ENERGYINTEROP-299: --------------------------------------------- Use of Identifiers and names should be considered in the context of inheritance from IdendifiedObject from IEC61970. All objects in CIM are inherited from IdentifiedObject for common semantics on identifers and names. See contents of the class below. All objects in the model submitted by OSG use .mRid as the identifier when possible. Name as teh readable text name. IdentifiedObject aliasName The aliasName is free text human readable name of the object alternative to IdentifiedObject.name. It may be non unique and may not correlate to a naming hierarchy. IdentifiedObject description The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy. IdentifiedObject localName The localName is a human readable name of the object. It is only used with objects organized in a naming hierarchy. The simplest naming hierarchy has just one parent (the root) giving a flat naming hierarchy. However, the naming hierarchy usually has several levels, e.g. Substation, VoltageLevel, Equipment etc. Children of the same parent have names that are unique among them. If the uniqueness requirement cannot be met IdentifiedObject.localName shall not be used, use IdentifiedObject.name instead. IdentifiedObject mRID A Model Authority issues mRIDs. Given that each Model Authority has a unique id and this id is part of the mRID, then the mRID is globally unique. IdentifiedObject name The name is a free text human readable name of the object. It may be non unique and may not correlate to a naming hierarchy. IdentifiedObject pathName The pathname is a system unique name composed from all IdentifiedObject.localNames in a naming hierarchy path from the object to the root. > Need better consistency in the notion of an ID versus a name (line 892) > ----------------------------------------------------------------------- > > Key: ENERGYINTEROP-299 > URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-299 > Project: OASIS Energy Interoperation TC > Issue Type: Improvement > Reporter: Ed Koch > Assignee: William Cox > > Within the EiEvent class, the EiConstaint class, and the EiOptout class there are names and ID attributes. The presumption is that an ID is some sort of object reference and a name is some sort of human readable representation. In some cases such as EiProgram:programID and EiProgram:programName we use both. It is unclear where a name versus an ID is required and perhaps in some cases where both should be there. -- 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]