Our industrial partners have difficulties coping with maintenance and reuse of their software applications, due to the hard coded presence of domain knowledge in the implementation. This paper reports on the remarkable analogy between this phenomenon and aspect-oriented programming, which leads to the interesting question: Is domain knowledge an aspect? Using a simplified example based on a real-world application, we illustrate that this problem could benefit from the AOP philosophy. Nevertheless, a number of important issues remain to be addressed. Contents