Andreas Hartmann wrote:
1) CONFIGURATION
<metadata name="dublincore-elements" prefix="dc" namespace="http://purl.org/dc/elements/1.1/">
<entry name="title"> A name given to the resource. Typically, Title will be a name by which the resource is formally known. </entry>
<entry name="creator"> ... </entry>
</metadata>
if we do this, lets make sure it plays nicely with JCR nodetypes
i am pretty sure there is a API to enumerate the elements in a schema, but i cant find it right now
This way we could get rid of pre-defined implementations and allow arbitrary meta data. The restriction is that there's a 1:1 mapping of meta data and namespace URIs.
.. which is probably not a real problem
An even simplier approach would be to allow the storage of custom meta data entries without configuration, i.e. without any restriction:
metaDataManager.setValue(namespaceUri, prefix, key, value);
easier, but means you cannot discover the possible values for a given metadata ns
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
