It is largely down to taste as both methods work.
I reserve UriQuery
for navigation that involves a payload. This is the case in which UriQuery is discussed in the prism documentation. I don't like them because they use weakly typed data - in this case strings. You have to serialise and deserialise. For complex data, this is error prone.
An aggregated event lets you pass a Argument object when you publish the event. You do not have to serialise and deserialise the query but you will need a common library to define the argument class.