In previous work we have developed an abstraction mechanism for a known cross-cutting concern in Ambient Intelligence software that untangles this concern from the base code. Motivated by the predominant view that AOP also includes unscattering, we discuss here a thought experiment on how to add unscattering to our abstraction mechanism. We find that this will not necessarily ease software development. This leads us to pose a number of questions whether unscattering is always required, and if an approach that only untangles can be considered as being AOP.