Searching for a well-engineered Component/Media Content Management System (CCMS/MCMS)

What do have YouTube, Flickr, SourceForge, Blogger and similar sites in common? - They have a user system and let the users publish their videos/fotos/software/articles. Other users can, apart from viewing/downloading/reading, comment and rate videos/fotos/software/articles. Generally speaking, in both cases the mentioned websites are content management systems for components. A component is a generalization of video/foto/software/article. And there is an architecture that seems to reflect this generalization; it is called component content management system or CCMS:

http://en.wikipedia.org/wiki/Component_content_management_system

Having such a CCMS would allow to build a website with general components which are than specified by the webmaster (using e. g. XML).

What CCMS (or MCMS for Media Content Management System) are available there?
Is there a comparison list similar to cmsmatrix.org but more focussed on this architecture?

 

DLE is one of such CMS, with blogging/gallery functions enabled
by some additional modules depending on needs of a webmaster,
but maybe you can just write down exactly what you expect 4m
CMS. I believe there will be much more answers in no time, then.

 

Hi AlcVitRes and thanks for your response. The following examples should illustrate how I indend to use such a CMS:

Example 1: Car Prototypes

A customer wants to create a gallery of car prototypes. Each car has a photo and a set of properties (name, motor, max. speed, etc.). The fotos with some properties should be shown in a list with pagination. On a detail page all properties should be shown in a template.


Example 2: Real Estate Objetcs

A customer wants to create a gallery of real estate objects. Each car has a photo and a set of properties (name, address, size/area, etc.). A google map should be shown also based on the value of a specific property. The fotos with some properties should be shown in a list with pagination. On a detail page all properties, several fotos and a Google map should be shown in a template.


My expectations from a "Component CMS"

• The webmaster specifies the component's properties in XML or any other convenient way.
• The provides an extended search with a filter based on the specified properties.
• The webmaster specifies the template where component's details are displayed.
• The webmaster specifies the template for the list view of a component.
• The backend of the CMS allows webmaster to control a large number of components in a convenient manner.

Another way of looking at "Component CMS":
Is is a simplified database development environment for the Web, similar to Microsoft Access.
In Access you design your database and the forms for the presentation of the data.