I agree with Laca's comment that some additional text on expected use would be helpful.
One thing that I found confusing is that Section 2.1 has > Because there are numerous commands associated with the GNU > environment that are not available in a default environment, this > case proposes that a path setting of > > PATH=/usr/bin:...:/usr/gnu/bin > > allows access to the GNU commands with no equivalent in the default > environment, and Section 2.4 has > GNU components that do not conflict with existing or anticipated > components in the system's default commands environment should not > be placed in /usr/gnu, and do not require 'g'-prefixing. So I guess the Section 2.1 text only applies for the case where we don't currently have a conflict, but we foresee one? Also, one nit: new cases should use the new stability taxonomy, so Stable should be Committed. mike
