J. Wolfgang Kaltz wrote:
access it via the LenyaMetaData. This generic "metadata = simple
attributes" approach does, I agree, imply that arbitrary, nested XML is
not possible within the metadata. So the decisive question is, do we
really need such XML within the metadata ? (IMO no)
i also think that the answer tends to be no, which in turn means it is a
piece of cake to make these attributes into jcr properties
To summarize, IMO it is in fact good code to encapsalute (non-DC)
metadata within LenyaMetaData, including the name of the attributes, and
any component needing access does something like
metaData.getFirstValue(LenyaMetaData.WHATEVER_ATTRIBUTE)
seems to me to be a difference whether the knowledge about attributes
should reside centrally in LenyaMetaData, or decentrally with the
various components. each has their strengths, but until we have very
loose coupling between lenya components, i don't see much harm in having
this knowledge centralized.
Any issues other than getting current meta attributes about a document
should not be handled via the MetaData interfaces.
explain?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
