Project

General

Profile

CIM Issues #5849

Association between AggregateNode and Pnode

Added by Herbert Falk about 2 months ago. Updated 6 days ago.

Status:
Closed
Priority:
Normal
Author/Contact Info:
Becky
Base Release:
iec61970cim17v34_iec61968cim13v12_iec62325cim04v09
Solution to be Applied To:
Solution Version:
iec61970cim17v34_iec61968cim13v12_iec62325cim04v10
Solution Applied By:
BLI
Completion Date:
02/17/2022
CIM Keywords:
Breaking Change:
Breaking Change Description:
CIM Impacted Groups:
None
Requestor:
Standard(s):
Version:
Clause:
AggregateNode
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
02/02/2022
Origination ID:
16_0133
Originally Assigned To:

Description

The association between AggregateNode and Pnode should be instead to AggregatedPnode.


Proposed Solution

The association is actually only between AggregateNode and AggregatedPnode. There is no use case to support a need for the association between the AggregateNode and IndividualPnode. Therefore the association should be removed from Pnode and added instead to AggregatedPnode. Existing cardinality is many to many, what should this cardinality actually be? 0..1 to 0..1 or 0..many to 0..many?


Decision

2/17/2022: Cardinality; set to 0..1 -> 0..1; no known use case to support the many to many at this time. Agreed to change the association (add new and remove the existing).

#1

Updated by Becky Iverson 6 days ago

  • Status changed from New to Closed

Also available in: Atom PDF