[Zope-CMF] Extensible Metadata

Carl Rendell cer@sol43.com
Thu, 8 Aug 2002 13:33:05 -0700


On Thursday, August 8, 2002, at 12:46  PM, zope-cmf-
request@zope.org wrote:

> Message: 11
> Subject: Re: [Zope-CMF] Extensible Metadata
> From: Tres Seaver <tseaver@zope.com>
> To: Chris Withers <chrisw@nipltd.com>
> Cc: noa@adequat.net, zope-cmf@zope.org
> Date: 08 Aug 2002 14:21:22 -0400
>
> On Thu, 2002-08-08 at 09:53, Chris Withers wrote:
>> Noa Harvey wrote:
>>>
>>> I don't think changing Dublin core would be correct, I just think 
>>> that
>>> the metadata tool should provide automatic form generation, and 
>>> services
>>> for changing an object's metadata. Also, the possibility to have
>>> epressions that are more complex then just lists of suggested values.
>>
>> I suggested this too, Tres poo-poo'ed the idea :-(
>
> I don't object to the general idea of generated forms, but I don't want
> them used as the default for the "stock" DublinCore schema.  Convincing
> me otherwise will involve actually writing the generating skin method
> and demonstrating that it doesn't make using the form more painful.
>
> Tres.
>

Sorry folks, but I'm getting confused by this subject. In my mind 
the DublinCore module represents a standard set of Metadata as 
described in the DublinCore recommendation ie

   http://dublincore.org/documents/#recommendations

The element set recommendation from DublinCore includes 15 elements

   Title, Creator, Subject, Description, Publisher, Contributor, 
Date ,Type
   Format, Identifier, Source, Language, Relation, Coverage, Rights

So the module itself is pretty close to the mark when it comes to a 
'standard' set of metadata for all of the cataloged object types. 
That make me believe that we would not want to change the 
DublinCore module to provide extensibility as it is an attempt to 
conform to a standard.

If one wanted a different set of metadata, regardless of starting 
point, one could easily write their own - no conforming - module 
and use it in place of DublinCore.

I realize that I'm more than likely standing alone on this point, 
but I believe that there are more than enough tools within the 
current tool set to allow extension of the catalog 'metadata' to 
fit any particular case [ at least I have not run into a 
limitation ].

I also feel that the skins allow more than enough flexibility to 
create new forms when there is a need to add additional attributes 
to objects, be that in the metadata form, edit form, or else where. 
As a result, I'm of the same mind as Tres.. someone would need to 
demonstrate that automatic form creation (for any interaction) 
would provide significant value over an above the simple method of 
changing skins.

Just an opinion of course...

~C

Carl E. Rendell
Solution43
Information Distribution Consulting        |   "Ahhhh the power of
cer@sol43.com                              |    acquisition"  - Chef Z