SYSMLR — Clarification required for Copy relationship

There's a few issues with the Copy relationship as described in the specification.

1. It's unclear what constraint 3 means. What are subrequirements (nested or derived)?

2. How do you match subrequirements in the slave to subrequirements in the master?

3. There's no constraint on the number of Copy relationships that a slave Requirement can be involved in (e.g. one Requirement could be the slave of two different master Requirements). What happens to the "text" tag if there are multiple masters?

4. There's no constraint stopping a Requirement from being directly or indirectly a master of itself. Shouldn't there be?

Defer

Postponed to the next RTF