Lists Home |
Date Index |
> >The key is that we have a formal means of
> >annotating the relationship between the master and the derived. In this
> >way we can design our processing pipeline to deal with whatever
> >constraints are appropriate at any stage. As long as people follow the
> >business rule that the universe of valid documents for any derived
> >schema is a subset of the universe of valid documents for the
> >corresponding master schema, it all works very well indeed. The problem
> >is that code review is the only way we have to enforce this rule.
Is the "formal means of annotating the relationship" through peer code
review? Or am I missing something...