UTP11 — Who is the receiver of a LogAction?

Rational: Section 6.3.2 Test Behavior, Subsection LogAction says the following:
—
The LogAction defines the tester‘s desire to log certain aspects during the execution of a test case.
—

Issue: Since «LogAction» stereotype enhances UML::SendObjectAction, the receiver of the object to be logged must be explicitly mentioned. It is not clear who receives the sent object.

Commonly, a log is sent to the execution environment which accepts and persists the entry. This seems to be a tool concepts, too, comparable to Scheduler semantics. It might make sense to introduce another additional technical interface for logging at test execution system level. «LogAction» might extend uml::OpaqueAction, so that there is no explicit receiver to be specified on model level. Vendors must ensure that logs are transported properly to the log interface.

Actually, the issue does not target a technical error in the specification, since the multiplicity of the target pin of SendObjectAction is not defined and left open. Therefore, it is possible to neglect the receiver or to add one if needed.
However, subsection semantics and constraints are stated more precisely