[Zope3-dev] Re: [Zope3-checkins] SVN: Zope3/trunk/src/zope/dublincore/ Dublin Core property to use Dublin Core meta data as simple properties.

2006-08-15 Thread Jürgen Kartnaller



Fred Drake wrote:

On 8/14/06, Jürgen Kartnaller [EMAIL PROTECTED] wrote:

It definitely doesn't obsolete the existing implementation.
DCProperty is the other way around.

DCProperty allows access to DC meta data via simple properties.


I agree that these should co-exist.  I'm not sure just what motivated
DCProperty, but it's clearly different from the partial adapter.  The
motivation for theh partial adapter was that for some content, some of
the data fields correspond directly to DC elements.  For those, we
wanted the DC adapter to use the fields instead of storing the
information outside the object.


When defining our content types we almost always end up with properties 
which are already defined in Dublin Core. Also the Dublin Core 
implementation of Zope 3 gives us a lot of meta data for free. Dublin 
Core has the advantage that the access to common information is 
standardized but it is not as easy to access DC meta data as it is to 
access a simple property of the content type.
So we decided to have the advantage of Dublin Core and the advantage of 
simple property access in one.



Regards
Jürgen

___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



[Zope3-dev] Re: [Zope3-checkins] SVN: Zope3/trunk/src/zope/dublincore/ Dublin Core property to use Dublin Core meta data as simple properties.

2006-08-14 Thread Florian Lindner
Am Montag, 14. August 2006 12:52 schrieb Jürgen Kartnaller:
 Log message for revision 69463:
   Dublin Core property to use Dublin Core meta data as simple properties.


 Changed:
   A   Zope3/trunk/src/zope/dublincore/property.py
   A   Zope3/trunk/src/zope/dublincore/property.txt
   A   Zope3/trunk/src/zope/dublincore/tests/test_property.py

Do I understand this change correctly that it obsoletes 
zope.dublincore.annotatableadapter.partialAnnotatableAdapterFactory?

Quote from zope/dublincore/tests/partial.txt which describes the 
partialAnnotatableAdapterFactory:

 Sometimes we want to include data in content objects which mirrors one
 or more Dublin Core fields.  In these cases, we want the Dublin Core
 structures to use the data in the content object rather than keeping a
 separate value in the annotations typically used.  What fields we want
 to do this with can vary, however, and we may not want the Dublin Core
 APIs to constrain our choices of field names for our content objects.

Should the partialAnnotatableAdapterFactory therefore be removed/deprecated?

Regards,

Florian
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



[Zope3-dev] Re: [Zope3-checkins] SVN: Zope3/trunk/src/zope/dublincore/ Dublin Core property to use Dublin Core meta data as simple properties.

2006-08-14 Thread Jürgen Kartnaller



Florian Lindner wrote:

Am Montag, 14. August 2006 12:52 schrieb Jürgen Kartnaller:

Log message for revision 69463:
  Dublin Core property to use Dublin Core meta data as simple properties.


Changed:
  A   Zope3/trunk/src/zope/dublincore/property.py
  A   Zope3/trunk/src/zope/dublincore/property.txt
  A   Zope3/trunk/src/zope/dublincore/tests/test_property.py


Do I understand this change correctly that it obsoletes 
zope.dublincore.annotatableadapter.partialAnnotatableAdapterFactory?

It definitely doesn't obsolete the existing implementation.
DCProperty is the other way around.

DCProperty allows access to DC meta data via simple properties.

partialAnnotatableAdapterFactory allows access via DC meta data to 
content properties.




Quote from zope/dublincore/tests/partial.txt which describes the 
partialAnnotatableAdapterFactory:



Sometimes we want to include data in content objects which mirrors one
or more Dublin Core fields.  In these cases, we want the Dublin Core
structures to use the data in the content object rather than keeping a
separate value in the annotations typically used.  What fields we want
to do this with can vary, however, and we may not want the Dublin Core
APIs to constrain our choices of field names for our content objects.


Should the partialAnnotatableAdapterFactory therefore be removed/deprecated?

No

Regards
Jürgen

___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



Re: [Zope3-dev] Re: [Zope3-checkins] SVN: Zope3/trunk/src/zope/dublincore/ Dublin Core property to use Dublin Core meta data as simple properties.

2006-08-14 Thread Fred Drake

On 8/14/06, Jürgen Kartnaller [EMAIL PROTECTED] wrote:

It definitely doesn't obsolete the existing implementation.
DCProperty is the other way around.

DCProperty allows access to DC meta data via simple properties.


I agree that these should co-exist.  I'm not sure just what motivated
DCProperty, but it's clearly different from the partial adapter.  The
motivation for theh partial adapter was that for some content, some of
the data fields correspond directly to DC elements.  For those, we
wanted the DC adapter to use the fields instead of storing the
information outside the object.


 -Fred

--
Fred L. Drake, Jr.fdrake at gmail.com
Every sin is the result of a collaboration. --Lucius Annaeus Seneca
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com