El mar, 13-06-2006 a las 16:58 +0200, Andreas Hartmann escribió: > Jörn Nettingsmeier wrote: > > Andreas Hartmann wrote: > >> Jörn Nettingsmeier wrote: > >>> 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 ... > > > > ... > > my starting point to achieve this goal was the LenyaMetaDataGenerator, > > which was written by a seasoned contributor to lenya, so i figured that > > this was the most obvious and consistent way to get at the data i need. > > No, this would be the wrong way. Unfortunately the generator publishes > the workflow meta data, which should be avoided. We could introduce > private meta data, or maybe it would be better to introduce a whole > new concept, e.g. internal document properties. But this would make > the code more complex.
I totally agree that we need private meta data and would like to remove the lenya:internal data block from the generator since it is causing many confusions and this private data should not be exposed to xml. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
