Over the last years a multitude of approaches and frameworks making prescriptions on how to document an enterprise architecture (EA) have been developed. These approaches target different purposes and correspondingly different concerns (areas of interest) in the architecture. In this way, a company seeking to develop or evolve an organization-specific EA documentation technique based on different approaches most likely runs into difficulties to understand the interdependencies between the different frameworks. In this research-in-progress paper, we revisit well-known documentation approaches to devise different types of concern relationships that may be helpful during development and evolution of an organization-specific EA documentation technique.