-
Key: SCE-25
-
Status: closed
-
Source: BPM Advantage Consulting ( Dr. Stephen White)
-
Summary:
RelationshipKinds should be well-known set of kinds. These kinds have semantic meaning and have notational impacts. Thus, they should be part of the normative spec through a standard enumeration (or perhaps sub-classes).
-
Reported: SCE 1.0b1 — Tue, 6 Sep 2022 15:37 GMT
-
Disposition: Closed; No Change — SCE 1.0b2
-
Disposition Summary:
Maintain how RelationshipKinds are defined through an extendible library
The vocabulary mechanism has been replaced by KindSets in
SCE-8.
In terms of this issue, there are downstream specifications, such as PPMN, that will use and extend the RelationshipKinds library.
Thus, we should close this issue (i.e., not convert to a fixed enumerated list).
It can also be noted that downstream specs do not have to use the library mechanism and can define their own enumerated set of relationship Kinds. -
Updated: Mon, 16 Sep 2024 14:12 GMT
SCE — Change RelationshipKinds from a Vocabulary to a UML Enumeration
- Key: SCE-25
- OMG Task Force: Specification Common Elements (SCE) 1.0 FTF