Both are talking about contracts, both deal with contracts as an XML level thing. Bill says contracts are best described as an ordered exchange of documents -- a protocol. Rich says that contracts are about the shape of the XML (tree) but not about the types of the values (stuff at the leaves) In his coverage of Tim Ewald's MSDN article, Rich does discuss document flows, but this time in terms of validation, that successively finer validation occurs at various points in the document flow.

Bill's point about interface changes propagating to clients is a good one. It is going to happen in all models designed around a static or explicit type system. The type system itself creates tight coupling between services and clients, so if the goal is loose coupling, then one way to do that is to get rid of the types. You can argue that this is what you are doing if you either use highly generic methods (you turn types into argument data) or a dictionary interface (same thing).

Food for thought.

create a marketplace that reflects people's desires and trust.

Of course, if you think some more, you start wondering what the software multipliers would be if you had corresponding ones...