Project

General

Profile

CIM Issues #5894

CDPSM conflicting roles OperationalLimitType.OperationalLimit and OperationalLimit.OperationalLimitType

Added by Martin Miller over 2 years ago. Updated about 1 month ago.

Status:
In Progress
Priority:
Normal
Author/Contact Info:
Base Release:
Solution to be Applied To:
Solution Version:
Solution Applied By:
Completion Date:
CIM Keywords:
Breaking Change:
Breaking Change Description:
CIM Impacted Groups:
WG13
Requestor:
Standard(s):

61968-13

Version:
2
Clause:
6.3.2.89
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
Origination ID:
Originally Assigned To:

Description

The role OperationalLimitType.OperationalLimit in section 6.3.2.89 is in conflict with the role OperationalLimit.OperationalLimitType in section 6.3.2.87 because they are both roles of the same relationship

Proposed Solution

Given that the model manager guidelines usually promote 0..1 roles over 0..* roles,
and also taking into consideration maintaining consistency with other existing profiles like CGMES,
remove the role OperationalLimitType.OperationalLimit in section 6.3.2.89
and preserve the role OperationalLimit.OperationalLimitType in section 6.3.2.87

Decision

18-Sep-2024 Joint TF Hybrid Meetings - Minneapolis:
Reviewed and have moved to In Progress. To be fixed in CIM18. Should be reconfirmed upon completion of CIM18 (some dependence on the unbalanced discussions).

#1

Updated by Chavdar Ivanov about 2 months ago

  • Status changed from New to Open
#2

Updated by Todd Viegut about 1 month ago

  • Status changed from Open to In Progress
  • Decision updated (diff)

Also available in: Atom PDF