DEPL — Submission allows multiple objects with identical names (unique identifiers

Subject:
Submission allows multiple objects with identical names (unique identifiers, UUID, URI).

Problem:
This creates an enormous potential risk for object identification errors, by allowing duplicate identities to exist. Risks include problems reclaiming resources, naming service references, etc. Some examples of this area of concern are provided below, there might be other instances that have not been identified in this list.

MOF 2.0 document states
8.3. Classifier requirements for instantiation
Names must be unique within Class, Package, and Operation

Examples:
6.4.3.4 Constraints
If the UUID attribute is not the empty string, then it must contain a unique identifier for the package; packages with the same non-empty UUID must be identical.

6.4.4.4 Constraints
If the UUID attribute is not the empty string, then it must contain a unique identifier for the implementation; implementations with the same non-empty UUID must be identical.

6.4.15.4 Constraints
If the UUID field is non-empty, then it must contain a unique identifier for the artifact; artifacts with the same non-empty UUID must be identical.

6.4.17.4 Constraints
If the UUID field is non-empty, then it must contain a unique identifier for the interface; interfaces with the same non-empty UUID must be identical.

Proposed Resolution:
Correct requirements to disallow any use of duplicate (identical) identifiers in all defined name spaces.