- Customer has upgraded from Tridion Sites 2013 to Sites 9.5.
- Developer has found multiple schemas that are sharing the same namespaces.  The schema pairs are somewhat similar, likely an administrator had copied and pasted from the source tab of one schema to the source tab of another schema as a shortcut.
- No content issues have been found with these schemas on Sites 9.5 or 2013, but developer would like to know whether there are any possible issues which the customer may encounter in the future.
- If there are potential issues, developer would like to know how to update the schema configurations so that the namespaces are unique, and what actions would be necessary afterward.
- The duplicate schema pairs were identified using this query and then manually removing the duplicates.

select 'tcm:'||publication_id||'-'||item_reference_id||'-8' as tcmId, title
from items
where item_type=8 and
content like '%uuid:11f1f1fb-11b1-1ba1-b111-c1ad11fe111a%'
order by title;

 

If a developer generates Java code from all of the client Content and Metadata schemas, then the sharing of namespaces is a problem as it results in naming collisions.

If the schema xmlns is changed, there are no changes for the content.  If the targetNamespace is changed, the components should be updated accordingly.

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="uuid:27d8ffbc-8162-4cdf-8463-111111c11111" xmlns:tcmi="http://www.tridion.com/ContentManager/5.0/Instance" 
elementFormDefault="qualified" targetNamespace="uuid:27d8ffbc-8162-4cdf-8463-111111c11111">