I really wish I could understand what you mean. I think I get the difference between a contract and its enforcement and software architecture, but is there a reason why these should not be addressed in the same talk? There is clearly something I'm not getting here, so perhaps further explication could help me to see it? Thanks, Roy On 11/7/07 11:24 AM, "D Chudnov" <[log in to unmask]> wrote: > On 11/6/07, Roy Tennant <[log in to unmask]> wrote: >> I have a presentation coming up and I'm considering doing what I'm calling a >> "Library Software Manifesto". > > It's a fine line between focusing people's attention on specific > aspects of how to enter into and enforce contracts and dancing about > architecture. --