Abstract In Aspect-Oriented Software Development, the selection of join points is an essential part. Join point selections identify the points in a program (ie in its code, or during its execution) at which aspectual adaptations need to take place. In order to communicate such selections independent of the underlying aspectoriented programming language, it is desirable to visualize join point selections in an appropriate way. In this paper we focus on the appropriateness of interaction diagram-based and state diagram-based visualizations of join point queries, exemplified with help of two business rule examples. As a result, we discover that even if join point queries are based on interactions in the base application, state diagram-based representations are needed to appropriately capture the selection semantic of that query.