IDublinCore behavior should be removed (With a long B/C path)

[rnixx]

It makes no sence to work with inherited behaviors in the core. This causes confusion when working TTW.

E.g. Some can either set Dublin core behavior on a content type OR the behaviors it consists of to a type. Otherwise we have duplicate fields in forms. For the user this is not very intuitive.

Related issue:

plone/plone.app.contenttypes#182

Cheers

[jensens]

+1

I'am sure it was intended to make things simple (as a shortcut). Thats not the case. In fact it confuses people.

Also changing behaviors parts in addons is more effort (we feeled the pain in collective.wfeffectiverange).

At a first i would deprecate it and dont use the behavior in p.a.contenttypes any longer. Also remove it from the docs and add a statement about it (comment) in the code.

If we really want a kind of "bundle" of behaviors we could introduce some sort of "makro" expanding on line in the FTI to a bunch of behaviors. If. I'am not sure if we really want this.