Skip to content

ST6RI-895 Item usages should be able to be typed by occurrence definitions#715

Merged
seidewitz merged 2 commits intomasterfrom
ST6RI-895
Nov 27, 2025
Merged

ST6RI-895 Item usages should be able to be typed by occurrence definitions#715
seidewitz merged 2 commits intomasterfrom
ST6RI-895

Conversation

@seidewitz
Copy link
Member

This PR removes validation checks related to the definitions of item and part usages.

Previously, the implementation validated that an item usage is typed only by item definitions (or KerML structures). In particular, this prevented an item or part usage from being typed by an occurrence definition that is not an item definition.

While this restriction is mentioned in the specification in the Language Description subclauses for items and parts, there is actually no such restriction formally specified in the Metamodel. The property ItemUsage::itemDefinition subsets OccurrenceUsage::occurrenceDefinition, it does not redefine it, and ItemUsage has no validation constraints. So item usages should be able to be typed by occurrence definitions. (See also OMG issue SYSML21-418.)

In addition, the implementation validated that a part usage had exactly one part definition. However, this validation check is unnecessary, since a part usage always has an implied subsetting of Parts::parts, which provides typing by at least the base part definition Parts::Part.

The PR removes the validation checks for both item and part usages.

@seidewitz seidewitz self-assigned this Nov 16, 2025
@seidewitz seidewitz added this to the 2025-11 milestone Nov 16, 2025
@seidewitz seidewitz added the bug Something isn't working label Nov 16, 2025
@seidewitz seidewitz merged commit 9012208 into master Nov 27, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant