Project

General

Profile

CIM Issues #5013

Unused abstract classes in profilesSometimes inheritance i

Added by Herbert Falk about 3 years ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Author/Contact Info:
Kendall Demaree
Base Release:
CIM16
Solution to be Applied To:
Solution Version:
Solution Applied By:
Completion Date:
CIM Keywords:
Breaking Change:
No
Breaking Change Description:
CIM Impacted Groups:
WG13
Requestor:
Standard(s):
Version:
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
09/07/2016
Origination ID:
13_267
Originally Assigned To:

Description

Unused abstract classes in profiles
Sometimes inheritance in profiles may skip over classes which have no properties in the profile. This seems to be default behavior of CIMTool. We need a policy for WG13 (at least) on how this situation should be addressed. This may be a profling issue, not canonical model, but this is a placeholder for the discucssion and decision.

Proposed Solution

Retain this ability to modify inheritance in the profile because it allows the canonical model to evolve inheritance differently than the profile without changing the profile.

Decision

Assign to software tooling

18-Sep-2024 Joint TF Hybrid Meetings - Minneapolis:
Reviewed. This is a very old issue and after review we do not currently have this issue in CIMTool. Have agreed to close.

#1

Updated by Eric Stephan about 3 years ago

  • Subject changed from Unused abstract classes in profiles Sometimes inheritance i to Unused abstract classes in profilesSometimes inheritance i
  • Decision updated (diff)
#2

Updated by Todd Viegut about 1 month ago

  • Status changed from Open to Review
  • Decision updated (diff)
#3

Updated by Todd Viegut about 1 month ago

  • Status changed from Review to Closed

Also available in: Atom PDF