|Description|| - <<in>> and <<out>> tags cannot be attached to stubs as it is not clear (especially with multiple in/out-paths) where the input/output occurs. |
- this feature should actually be renamed to no RAM metadata on anything but start points, responsibilities, and end points (this is required because otherwise the composition of aspects does not work - e.g., it is not possible to insert an aspect marker after the <<in>> on an OR-fork)
- hence, a responsibility may have an "out" and an "in"
- hence, a start point may have an "out" and an "in"
- hence, an end point may have an "out" but no "in"