J. Wolfgang Kaltz wrote:
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
hmm... we might be able to use object for that as well
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.
+1
plus we should take a look at how this maps to jcr nodetypes
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
