Actually its just the Name attributes that are strange, user-defined Label attributes *do* behave as if they are local to that content-type. andy ..... Ermmm - no, that; exactly what I would have expected and what it won't do for me. For example, Article has a field Label: Tags Name: Field_tags Its value has several type attributes that constrain what in some programming language or other I might call its "type" - I can re-use these without problem. But suppose I want to create another content-type of my own with a field having the same Label and Name - the system won't do it - I have to call them say Tags1 and Field_tags1. Now Label and Name are not different kinds of things from the other fields so why should they be immutable ? Also - they *are* re-used, but only in content that comes out-of-the box not user-defined content. This seems to be a limitation (but it may be me doing something wrong). If it *is* a limitation in practice then my question is - is it a necessary limitation of the model/paradigm and if so why ? andy