[Zope-CMF] Future CMF

[Erik Lange]

At 10:21 AM 10/5/02, Paul Everitt wrote:

>Speaking of "Future CMF" (and thanks, Erik, for relabeling the subject
>line), Jim's announcement of proposal on this topic has received no
>comments:
>
>
>http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/ 
>ContentManagementProjectsForZope3
>
>Zero, zippo, nada.

Here's my personal comment:

Once again the visions of the pope brought tears into my eyes :-)

>Here's what we'd really like to see: people who care deeply about one
>of the topics (workflow, metadata, etc.) become the champion for that
>topic.

We're pretty focused on metadata here at mmm, and we would love to 
contribute in any way we can.

First step would be a complete implementation of Dublin Core elements, but 
I belive we should have some sort of plug-in structure for metadata sets, 
that can be assigned to the objects in the framework.. I.e. the Dublin Core 
metadata set even in it's complete form, doesn't deliver all the metadata 
elements needed when working with media. The "time" data is missing, so you 
can't describe a resource that is defined by time in a specific mediafiles 
internal timeline, i.e. a clip in the masterfile. (Example; Car-chase: in 
01:12:35:12 - out 01:15:54:03 - "Car-chase" is ofcourse DC.Title, but what 
is in/out?)

MPEG7[1] and MPEG21[2] are metadata sets that operates with timebased 
resources, and a structure that allows to plugin various metadata sets into 
the framework has been on our wishlist for some time.. presently we just 
adds the extra metadata we needs as properties on our objects, and it works 
okay - but it's not the ideal way of doing it.

I imagine that other special areas has their own sets of specialised 
metadata as well, so I think going for such a structure will be usefull in 
a lot of scenarios.

For us, the posibillity of using MPEG7- and MPEG21-implentations together 
with Dublin Core metadata would, as I see it, in reality make the semantic 
web [3] of multimedia come to life ! :-)

>For those that don't want to be champions...at least read the section
>under "Background".  I tried to capture some of the spirit and intent
>of what has gone on up to now.  This latest discussion has illustrated
>that we have more work to do in getting this nailed down!

Well... we're on ! :-)

What do we do next.. ?

Regards,
Erik

[1 ]MPEG-7, formally named "Multimedia Content Description Interface", is a 
standard for describing the multimedia content data that supports some 
degree of interpretation of the information's meaning, which can be passed 
onto, or accessed by, a device or a computer code. MPEG-7 is not aimed at 
any one application in particular; rather, the elements that MPEG-7 
standardizes support as broad a range of applications as possible.
http://mpeg.telecomitalialab.com/standards/mpeg-7/mpeg-7.htm

[2] The vision for MPEG-21 is to define a multimedia framework to enable 
transparent and augmented use of multimedia resources across a wide range 
of networks and devices used by different communities.
http://mpeg.telecomitalialab.com/standards/mpeg-21/mpeg-21.htm

[3]: The semantic web: "A road map for the future, an architectural plan 
untested by anything except thought experiments." - by Tim Berners-Lee
http://www.w3.org/DesignIssues/Semantic.html