Jörn Nettingsmeier wrote:
[...]
* the LenyaMetaDataGenerator introduces a somewhat nicer structure by
using wrappers, but these need to be defined somehow. is there
general interest to have hierarchical metadata, or do you prefer flat
for internal use?
IMO a flat structure is sufficient.
ok, the new schema is flat. i have even flattened the "var:is_live"
thing into just a <isLive/> element. it's probably easier and more
concise to extend the schema when new var:foo fields are needed than to
build extensibility into the schema. this way, the schema can be used as
documentation.
Hmmm - the is_live workflow variable is not generic, it is just a
variable which is used by the default publication's workflow. I'm
not yet familiar with your code - does it still support arbitrary
workflow variables?
[...]
We should abandon the concept of "custom" meta data and introduce
modularized meta data instead. IMO this is not too complex and should
be implemented for 1.4, since it affects the content repository.
as michi remarked, it is important to be able to differentiate between
core metadata that is handled by lenya and must be backwards compatible,
and custom stuff that is just passed through as-is.
I totally agree, but this is a different issue. We have several concern
areas which are not necessarily related:
1) Backwards compatibility
Since meta data are stored with the content, they must either
be stable, or there must be a migration tool.
2) Protection
Maybe some meta data should be read-only, or only accessible from
certain components.
3) Validation
It should be possible to define additional meta data sets which are
used by custom components. The meta data should be validated, i.e.
the set of keys is fixed.
I don't understand why (3) would violate (1) ...
Maybe you (Jörn + Michi) can explain your concerns?
Thanks!
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
