Description: 
My understanding is that a Requester can not express requirements in the form of WS-Policy, nor can the Requester have a policy. A Requester can only adhere to the policy specified by a Provider.
 
The first paragraph of 4.4 creates the impression that a Requester may have a policy. It states that when a requester and a provider express requirements on a message exchange, intersection identifies compatible policy alternatives (if any) included in both requester and provider policies On the contrary - section 3.4 states that a policy is supported by a requester but it rightfully does not specify that a Requester has a policy. 

Also, accordingly to the Abstract, the Framework deals with ...the policies of a Web Service... but not with the policies of a Requester of the Web Service.


Justification:
Clarify the difference between Requester Policy and Requester supporting a policy

Target: 
WS-Policy Framework, 4.4 Policy Intersection

Proposal:
Change the first paragraph of 4.4 

From:

Policy intersection is useful when two or more parties express policy and want to limit the policy alternatives to those that are mutually compatible. For example, when a requester and a provider express requirements on a message exchange, intersection identifies compatible policy alternatives (if any) included in both requester and provider policies. Intersection is a commutative, associative function that takes two policies and returns a policy.

To:

Policy intersection is useful when two or more parties express policy and want to limit the policy alternatives to those that are mutually compatible. Policy intersection identifies compatible policy alternatives (if any) included in the policies. Intersection is a commutative, associative function that takes two or more policies and returns a policy.