See email from Ken Laskey: http://lists.w3.org/Archives/Public/public-ws-policy/2007Jul/0047.html

1. The expanded definition for policy [1] at times seems to cover an  
immense amount of the general description space but then the examples  
for use are mostly restricted to the tedious (but necessary for  
message level interoperability) details.  The discussion does not  
support the business use that is needed if services are to accomplish  
more than geek talk.  Even at the wire level, a big gap is how do  
consumers use WS-Policy to express their capabilities and  
requirements that will be used to determine policy intersection.  The  
consumers do not have WSDLs and may have no interest in UDDI.  They  
do, however, want to point to a policy that says you should not sell  
their contact information, i.e. what was carefully exchanged in a  
manner to initially ensure privacy will remain private.