Custom Sections in Templates need to be able to be common across all projects rather than polluting the schema

Currently for a project you create Templates for a Testcase and can add custom sections. Custom sections are exposed in the ETM schema which allow you to report on them however if you have multiple projects you get the custom sections from other projects as well in the schema even if they are the same field. ETM does not allow you a way to define a common URI to link common Custom Attributes. Three negative effects of this: Example - If a project had 10 custom sections. 1. With 50+ projects you would get 50x 10 custom sections appearing the schema definition with 10 of indentical name appearing with no obvious way to see which one you shoudl be using. 2. There is no way to make a generic PUB reporting template which works accross projects. We have at the moment 5 reports we want to use on a project. So we need to maintain 5x50 projects worth of templates using the SAME custom sections. 3. Custom schema's and publishing templates become very cumbersome to maintain. Fix would be similar to DOORS next. Allow users to specified a URI (or other unique ID) the the system can match together if they are the same. Default behaviour would be auto assigned and different but could be overwritten to link them together. Alternative way would be create a library of custom sections which could be shared across templates and managed that way. The current implementation is poorly designed for large companies with many projects.