The problem was Babbage's insistence that in projects that followed, he tried to implement an ever more complex design. He failed to complete them as a result. His final designs incorporated very sophisticated features which were beyond the technology of the time although elegant. You have to sell this design as well as create it. Common requirements cannot be ascertained without a statement of common needs or problems.
Big leaps take more effort and destabilize existing initiatives.
I agree that the problem statement is required and that it must account for designs which are already advanced in some systems. Add categories or members you think relevant. There is no harm in drawing a skeleton of the systems, functions and application features which influence the URN design or the problems that require it be done. This is not the same as saying this working group must declare formal definitions for these or attempt to broaden the scope of the work unacceptably. But 'draw the circle'.