I feel quite the opposite. Without a holistic view of the problems users are facing, it is easy to write rules that later conflict with each other when people try to keep the rules too narrowly scoped. This is one of the issues I have with the way the specification was stitched together. When discussing the current state and issues that users are currently facing, getting information about related problems, even if they need to be addressed separately when it comes to specification language, is useful and important for creating a consistent system.
I have at this point split off the module-level inline annotation issue into its own thread as I feel I have enough working information and a demonstration of the current lack of specification at a point of interoperability to do so.