Andreas Hartmann schrieb:
(...)
I see the MetaDataManager as a service which offers the functionality
to store meta data which are needed by other components. If the
MetaDataManager
exposes a fixed attribute set, we'll have to change the core API whenever
we change a component's meta data set.
Assume you're implementing a component needing several meta data attributes
in a publication. If you're using the CustomMetaData, you're running into
several problems:
- risk of name clashes, especially if you're using the pub as a template
and add further components
- you have to implement your own namespacing syntax to avoid name clashes
- making the component available to the public can also lead to name
clashes
IMO we should not separate between LenyaMetaData and CustomMetaData, but
we should offer each component to use its own meta data set.
The type "CustomMetaData" was just a first proposal, as someone on the
list mentioned a custom need for metadata, which he suggested to store
in the site tree, but I thought a metadata mechanism was better for
this. Since the CustomMetaData is not yet actually used, we can remove
it and generalize LenyaMetaData instead. Or, we could rename
CustomMetaData to ComponentMetaData, add support for parameterizing the
namespace, and say that this is to be the container for all non-core
metadata.
Do you think we should distinguish metadata attributes from different
components according to namespace, or should we support a hierarchy
instead (each component getting its own subelement in the metadata) ?
--
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
