On Mon, 8 Jul 2002 10:21, Stephen McConnell wrote: > >Currently the metainfo packages are different and incompatible. This is > > only going to increase over time. > > The DTD for an external form of a <compoent-info/> declaration does not > restrict you to the use of a particular meta model. It is simply the > criteria for model creation. Currently, the DTD used in containerkit is > the same as the DTD used in the Merlin meta.info model.
The DTD is only part of the picture. Currently both products use different mechanisms to locate data (different file names) and as they use serialized formats by default they will never ever be compatible in that respect. > What I'm > suggesting here is that components that are put in place to support the > current *common* <component-info/> DTD should not be impacted by changes > that are not formally introduced as new visions to the *common* defintion. So change can be blocked if it doesn't go through a "formal process". Hmmm... Still cant see any reason to put it in framework without coresponding code to support it. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
