Disclaimer: Naming conventions provided hereafter are proposals. Beyond the naming conventions which are always arguable, there is a hierarchical data structure which is essential to Content Management.
Objects used in Content Management are "Media Objects". The Media Objects are "undifferentiated". They could be digital audio, image, video, etc. Naming convention should be added to qualify these undifferentiated Media Objects.
When Object Metadata aimed at describing the Media Object is added, the combinaition can be called: "Content Object". So, a Content Object is a Media Object with its Metadata.
When Usage Rights aimed at protecting a Content Object are added, the combinaition becomes a Protected Content Object. Note that Licenses are one of the possible protections for Content Objects.
Protected Content Objects and Unprotected Content Objects can be grouped to be delivered as a package. A group of Protected Content Objects and/or Unprotected Content Objects can be called Mashed Content Objects. Each Content Object in a group can be protected or not.
Unprotected Content Objects, Protected Content Objects, and/or Mashed Content Objects can be inserted in a bearer service to be delivered to end-users. A bearer service that includes Content Objects (protected or not, mashed or not) becomes a Content Service.
Content Management is about moving Content Objects (protected or not, mashed or not) into bearer services.
Content Objects (protected or not, mashed or not) are TMF resources added to other TMF resources in support of the bearer services. Bearer is used here in the context of bearing Content Objects to an end-user.
Among other tasks, Content Management should manage Object Metadata, make sure Content Objects are protected if they have to be protected, and mashed if they have to be mashed.