[Zope3-dev] Re: DC Contributors

[Garrett Smith]

Fred L. Drake, Jr. wrote:
  > If this isn't a direct match for a Dublin Core element, let's not
> overload it.  We have a component architecture and an annotation model
> that let's us be very flexible; let's not waste it by fudging the use
> of DC elements.  Our current use is already pretty questionable in my
> book, simply because there can be multiple things described, and the
> way we use the DC data isn't clearly defined.

I agree, but the current use of the pattern:

   dc = zapi.getAdapter(context, IZopeDublinCore)
   doSomthing(dc.modified)
   doSomethingElse(dc.created)

is widespread. It seems to me we either overload DC or move the core 
Zope metadata into its own interface. I strongly prefer the later 
option. I think the use of DC as core metadata management for Zope is 
dubious.

Mapping from zope metadata core to dublin core is a simple adapter 
application.

> I think we should have DC data for the Zope object distinct from any
> metadata we're using the system to store, and I don't think this kind
> of usage pattern is very clearly discussed anywhere.  

Agreed.

> Regret asking?  ;-)

It's innevitable that I regret posting questions/suggestions like this 
;-) But not having access to 'modified by' info is a major oversight, 
IMO. Maybe this is a good time to define IZopeObjectMetadata (???) and 
move away from using DC for such a central role.

I can facilitate some discussion on this. Is the original advocate of 
using DC as the central metadata model still around and kicking? Apart 
from it being a prominent standard for metadata, its advantages aren't 
apparent to me.

  -- Garrett