[Feature]: Handle Composite Aggregation correctly #75
Description
What type of issue is this?
- Bug report
- Feature request
Prerequisites
- I have written a descriptive issue title
- I have verified that I am running the latest version of the SysML2.NET
- I have searched open and closed issues to ensure it has not already been reported
Description
SysML2 defines 2 composite Aggregation that are not-derived.
The Section 7.2 describing the ownership of element can be resumed like:
If Element B is owned by Element A, the structure looks like this:
- Element A holds a reference in its OwnedRelationship list to Relationship R.
- Relationship R points back to Element A via its OwningRelatedElement property.
- Relationship R holds a reference in its OwnedRelatedElement list to Element B.
- Element B points back to Relationship R via its OwningRelationship property.
Proposed solution: Implements a specific collection to replace the List used when dealing with Composite aggregaiton to reflect this pattern
Steps to Reproduce
System Configuration
- SysML2.NET version:
- Environment (Operating system, version and so on):
- .NET Framework version:
- Additional information: