-
Key: KERML-46
-
Status: open
-
Source: NIST ( Mr. Conrad Bock)
-
Summary:
Some multiple specializations in the libraries might be intended to be intersections, including feature specializations. For example, quite a few in Performances.kerml:
step subperformances: Performance[0..*] subsets performances, suboccurrences; expr subevaluations: Evaluation[0..*] subsets evaluations, subperformances; step subtransfers: Transfers::Transfer[0..*] subsets transfers, subperformances; step subtransfersBefore: Transfers::TransferBefore[0..*] subsets transfersBefore, subtransfers;
In Links.kerml:
assoc struct LinkObject specializes Link, Object ... { ... } assoc struct BinaryLinkObject specializes BinaryLink, LinkObject {... }
Might be others. Sometimes this is modeled with sufficiency, for example in Occurrences::Occurrence::
feature all spaceTimeEnclosedOccurrences: Occurrence[1..*] subsets timeEnclosedOccurrences, spaceEnclosedOccurrences { ... } feature all spaceTimeEnclosedPoints : Occurrence[1..*] subsets spaceTimeEnclosedOccurrences { ... }
If sufficiency isn't needed for other reasons, it could be replaced with intersection.
-
Reported: KerML 1.0a1 — Fri, 28 Apr 2023 14:35 GMT
-
Updated: Mon, 8 Apr 2024 21:42 GMT
KERML — Intersection missing for some multiple specializations
- Key: KERML-46
- OMG Task Force: Kernel Modeling Language (KerML) 1.0 FTF