Just my 3 cents. Friday, June 3, 2005, 11:48:51 PM, J. Wolfgang Kaltz wrote:
JWK> As a general design strategy, my opinion is: JWK> LenyaMetaData is Lenya's specific metadata about a document - meaning, JWK> all metadata not clearly standardized in Dublin Core. IMO it makes sense JWK> to put all metadata pertaining to the document in this container. This JWK> does not say which component "uses" it; in fact we cannot predict future JWK> uses. Any component wanting to use this metadata must know its name and JWK> access it via the LenyaMetaData. This generic "metadata = simple JWK> attributes" approach does, I agree, imply that arbitrary, nested XML is JWK> not possible within the metadata. So the decisive question is, do we JWK> really need such XML within the metadata ? (IMO no) It was me who proposed custom XML metadata. which I had stored it in sitetree when used pure cocoon. I called it "metadata" just because it is associated with documents. Some of it replaced with DC in Lenya. The purpose of other was defining url parameters affecting rendering, they form additional navigation elements - a menues of these parameters. Each parameter was presented with: list of( prarmetername + list of ( value + title )) Another example of custom "metadata" im looking to is set of subscribers to notify on page changes: list of (email + attributes). Both examples do not fit attribute=value scheme. IMO storing custom XML data associated with documents MAY be usefull. But this definitely does not fit common concept of "metadata" (attributes+values), and is probably something else, which requires more complex handling (accessing with xpath, editing in cforms). I still hope there will be a way to implement such data w/out breaking core. EndOfCents. -- qMax --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
