Hi Jörn, IMO the problem about this schema is that it is not generic, i.e. it is not possible to add custom meta data sets without changing the schema. Additionally, if you convert meta data to elements, you have to make assumptions, e.g. regarding the internal storage of workflow versions. This is a concern of the workflow engine, the meta data component may only read or write the meta data but not try to parse or understand them.
I'd prefer something like this: <meta-data xmlns="http://apache.org/lenya/...";> <elements namespace="..."> <element name="foo"> <value>hello</value> <value>world</value> </element> ... </elements> ... </meta-data> I understand that this is not as good as your suggestion when it comes to validation, but IMO we have to use a really extensible and generic format to render meta data as XML. WDYT? -- 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]
