Johan Stuyts wrote:
Conclusion
----------
IMHO there should be more consensus about what is needed and what is feasible in a relatively short time, e.g. half a year to a year.
I think building a generalized workflow based on a standard is too ambitious. Leaving out some more complex constructs decreases usability. It might be an option to choose a (proper) subset of a standard with which a large percentage (definitely more than 80%. Having to resort to another solution in one of four situations is not acceptable) of use cases can be implemented.
I would suggest to start on an existing code base, e.g. Lenya or whatever, make
an appropriate Cocoon block out of it (there had been a list of requirements to meet)
and start from there.
If that goes along with some documentation :-) and an isolated sample I'm +1
Guido
Else I guess discussions just keep going forever ;-)
The existing code base might not satisfy everybody, but at least it's something
concrete to start with, even if it will be totally modified resp. refactored in the end.
Michi
-- Guido Casper ------------------------------------------------- S&N AG, Competence Center Open Source Tel.: +49-5251-1581-87 Klingenderstr. 5 mailto:[EMAIL PROTECTED] D-33100 Paderborn http://www.s-und-n.de -------------------------------------------------
