UMLR — As Events are Packageable Elements, how is their Package known?

Though an Event is a Packageable element (Figure 13.2 Events), it is unclear which Package owns it.
One possibility would be the Trigger that refers to it. However, more than one Trigger can refer to the same Event, and these Triggers may be in different Packages (e.g., BroadCast Events)
Another possibility would be the Package of the element that issues the Event. However, some Events have no clear originator. A SignalEvent may be issued from multiple places. More complexly, a change event may have multiple originators at the same time, from different Packages, such as on[Package1:A >Package2:B].

The purpose of being Packageable is usually to imports and the ability to have unqualified names. As events seem not to have names (other than usage within a trigger), it does not appear that they could be the target of an import.
If events don't and can't have names, they seem to be incorrectly identified as PackageablElements.

So solutions.
1) Stop them from being PackageableElements.
2) Give them names and make them classifiers.
....