Policy alternatives, negation, [Non]AnonResponse assertion and the none URI

There is view among the WS-Policy wonks (not sure how widely accepted 
this is or whether the WS-Policy specs explicitly calls this out) that 
when there are alternatives present and the selected alternative does 
not contain an assertion X but another alternative does, then the effect 
  of such a selection consists of negation of X.

We have two assertions AnonResponse and NonAnonResponse assertions. Both 
of them require that the 'none' URI be allowed for the response EPR. 
Does that mean that negation of any of these implies 'none' must not be 
used?

If so, that is a problem, none is useful for things like one-way 
operations that don't use the response EPR for that MEP.

Additionally, if one has two alternatives one with AnonResponse only and 
one with NonAnonResponse only, then that would be self-contradictory.

-Anish
--

Received on Monday, 16 April 2007 16:57:31 UTC