Skip to main content

Why Copy-Pasting your Schemas Is Not a Good Idea

I just noticed something concerning -- I copy-pasted a Schema in Tridion 2011 SP1 HR1 and I noticed the UUID namespace of it did not change. In fact I ended up with two different Schemas having the exact same namespace.

So far, I have not found a case where that breaks, but it not look good to me (i.e. that UUID seems like it was put in place for a reason).

For me, the root nodes of the two Schemas are not the same, but some of the fields are. I believe there can be a clash there.

Still thinking for a use case where that breaks...


Comments

ingmaru said…
Will be a PITA if you are making use of XSLT templating :) for Compound it's not going to bother you :)
Peter Kjaer said…
This is a good example of a default value setting expectations.
In this case, the wrong expectations. The target namespace does not have to be unique and it shouldn't be changed automatically when you make a copy.

My guess is that the default value is unique mostly because we didn't think people would want it to be a tridion.com URL. And since you need the target namespace to have a valid XSD, it must have a value from the very beginning. You can't wait for the user to enter a value.

Speaking of the target namespace: it really should have been added long ago as a field on the General tab.