[Bug 4393] [Primer] Add text to strict and lax policy intersection discussion describing how a policy consumer can determine issues due to intersection mode conflicts

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4393





------- Comment #1 from cbarreto@adobe.com  2007-03-27 23:49 -------
Update - concrete proposal: 
Perform the following changes to the Primer text

Change in 3.4.1 Strict and Lax Policy Intersection, in the 3rd paragraph, 4th
sentence as follows:

"When using the strict intersection mode, assertions marked with
|wsp:Ignorable| are part of the policy alternative vocabulary, so the
|wsp:Ignorable| attribute does not impact the intersection result even when the
|wsp:Ignorable| attribute value is "true"."

Add to 3.4.1 Strict and Lax Policy Intersection, after the 4th paragraph as
follows:

"In certain cases the provider may intend for their policy or policies to be
intersected using one mode, while a requestor may not support that same mode
while they both have expectations on expected results. For example, a provider
of a service which handles line of business (LOB) processing can provide a
number of qualities of service (QoS) which are exposed as policies. A requestor
can effectively navigate which QoS (service interface) to use through its
requirements. 
However, the requestor of an LOB processing service may need to consistently
apply certain assertions in order to use a service, whether these are the
requestor’s own, or accepted from the provider. In particular, requestors which
require strict mode intersection could encounter unnecessary intersection
results such as failures (no policy alternatives available) without any
information as to why the failure occurred. In such cases it is useful for the
requestors to apply multiple intersection modes when consuming policies and
comparing the results, in order to detect conflicts and specify their source.

Regardless of chosen policy intersection mode, the wsp:Ignorable marker on a
policy assertion does not express any requirement on the behavior of the
client, rather, it is used for intersection as indicated in Section 2.7. After
intersection, any assertions contained in the resulting policy that are
understood by the client are handled as expected, and are not ignored,
regardless whether those assertions are marked with wsp:Ignorable."

Received on Tuesday, 27 March 2007 23:49:36 UTC