> I've been wondering whether its a smart idea to change a whole lot of this > now. I think the Normalizer code and friends shows we can keep the model the > same for now yet develop most of our code the way we see fit. The new model > will fall out, and we'll immediately know what the transformation steps are: > the Normalizer ends up being the conversion step between the old GOM and the > new GOM. > > Does that make sense to you?
It can wait. > Of course, I'm now seeing that this is very bad communication-wise, since > you'll have to understand all that ugly xml code in order to understand what > the code does. > > Hmm. Maybe we should take it further. I'm thinking here that we should > forget about the xml there and build the example model completely in code. Sounds good for a test model we can write unit tests against. regards Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
