Jörn Nettingsmeier wrote:
Andreas Hartmann wrote:
[...]
Well, IMO Lenya should behave like a framework and define the
structure of the meta data, but not the actual content. It should
be possible to add components without modifying the core. What
if you want to use a custom Workflow component which doesn't use
version elements to store meta data, or something like that?
just to clarify: basically all i wanted to say with the whole namespace
shebang is this:
let's first write the data specification.
then implement the specification.
(as opposed to hack in a bunch of variables as needed and call them
metadata.)
i don't care whether this is done with a relaxng grammar for the xml
realm, or with a nice javadoc comment for the object realm, as long as
it's done.
i don't care about the details of this specification either.
what i do care about is stopping people from ever again introducing
multi-dimensional, semantically overloaded metadata tables (!) with
built-in extensibility (!!) represented as single strings (!!!) without
so much as a passing regard for documenting this whole pile of shit
anywhere, and then having to use (shudder!) regexes to clean up the mess.
workflowVersion in its current state is an abomination unto $deity and
must die.
fast.
violently.
Actually I don't really understand this concern. The workflowVersion
meta data are accessed only by the workflow engine, they are strictly
private and I see no need for applying any regular expressions on
them. If you need workflow information, ask the workflow engine ...
There's no point in specifying the workflow meta data, because they
might change, and every workflow engine might use its own meta data
format.
IMO the real problem is that we can't distinguish between "private"
and "public" meta data yet.
-- 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]
