Project

General

Profile

CIM Issues #5835

MarketEvent attribute eventStatus - use of Status Compound or enumeration

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

Status:
Closed
Priority:
Normal
Author/Contact Info:
Becky
Base Release:
iec61970cim17v34_iec61968cim13v12_iec62325cim04v08
Solution to be Applied To:
Solution Version:
iec61970cim17v34_iec61968cim13v12_iec62325cim04v11
Solution Applied By:
BLI
Completion Date:
03/03/2022
CIM Keywords:
Breaking Change:
Breaking Change Description:
CIM Impacted Groups:
None
Requestor:
Standard(s):
Version:
Clause:
MarketEvent
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
01/18/2022
Origination ID:
16_0119
Originally Assigned To:

Description

Attribute eventStatus uses as a datatype the Compound Status. Is the Compound Status the right choice for use by MarketEvent.eventStatus?


Proposed Solution

Will the Compound Status continue to exist and be managed by WG14 with many other Compounds being replaced by classes? Previously the eventStatus had an enumeration with the values; active, cancelled, completed, planned. Discuss use cases for using Compound Status vs enumeration.


Decision

2/24/2022: Agreed to add a new class (to be named) that would be associated to for status life cycle of the event (status (string), dateTime, reason). Propose model updates in next call.
3/3/2022: Updated datatype of eventStatus to String.

#1

Updated by Becky Iverson 6 days ago

  • Status changed from New to Closed
  • Decision updated (diff)

Also available in: Atom PDF