J. Wolfgang Kaltz wrote:
Hi list,
a few weeks ago we discussed changing the metadata handling, to
1. make metadata for a document mandatory;
2. store the metadata separately from the contents
3. add some Lenya-specific, non dublincore metadata, specifically the Lenya resource type within the metadata
(...)
that means we can switch back to a generic xhtml relax ng, yay.
Yes, except that we need to keep the lenya namespace IIUC, because the document may contain a lenya:asset
what about 3? will you handle 1 & 2 first, and then tackle 3? sounds good to me.
Yes, 1 & 2 are in fact a simple change (unless I've overlooked something), I can check that in later.
For the next step, I'm wondering to what degree different types of metadata should be separated. We could of course handle everything in the same Map, but maybe it's better to have a clear separation ?
Suggestion: the MetaData of a Document/Resource consists of 3 sets of metadata
- dublin core, this is the existing stuff. It is specified at document creation time; the "meta" usecase is used to edit this information in a GUI.
- lenya metadata: this is Lenya internal metadata, such as "resource type". It is automatically created and managed by Lenya, the user does not see this data.
- custom metadata (see also qMax's mail): this is the mechanism through which a Lenya implementer / customizer can assign arbitrary metadata to resources / documents.
All metadata would be stored in the .meta file (later: meta node), though perhaps in 3 different branches; whereas the API would explicitly distinguish the 3 types.
WDYT ?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
