Project

General

Profile

CIM Issues #5015

Create validation constaints for the UML model and profile

Added by Herbert Falk about 3 years ago. Updated about 2 years ago.

Status:
In Progress
Priority:
Normal
Author/Contact Info:
Kendall Demaree
Base Release:
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):

61970-501

Version:
v2
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
Origination Date:
10/05/2016
Origination ID:
13_269
Originally Assigned To:
Svein Harald Olsen

Description

There is a need to describe constraints to the information model and profiles. Using static model (classes and attributes) for modeling constraints is not recommended. Object Constraint Language (OCL) is part of UML 2.0 and are to some degree supported by Sparx EA.

Proposed Solution

The Sparx EA usage and support is outside the scope of 61970-501, and will be follow up as part of the requirement to the modeling and profiling tool. As we are using semantic web languages RDFS-plus for the vocabulary it would make to use Shapes Constraint Language (SHACL) (https://www.w3.org/TR/shacl/) for the validation and constraints. It is also a strong believe it will be easier to convert from SHACL to OCL than the other way. However, we might need to see in the dialog with Sparx how the constrains can be model the easiest to make it possible to be exported as SHACL.

Decision

[2022-09-22: The use of SHACL as part of the 501 profiles will be added to Ed2 fo 501. Need to evaluate the need to include OCL -> SHACL transformation.]

Also available in: Atom PDF