W3C home > Mailing lists > Public > public-ws-policy@w3.org > January 2007

RE: NEW Issue: How to ignore some "ignorable" assertions only?

From: Asir Vedamuthu <asirveda@microsoft.com>
Date: Sat, 13 Jan 2007 22:06:44 -0800
Message-ID: <1E0F0378382054439F14D5450650478F0BFD78D1@RED-MSG-42.redmond.corp.microsoft.com>
To: Prasad Yendluri <prasad.yendluri@webmethods.com>, <public-ws-policy@w3.org>

>does not allow for ignoring only  a subset 
>of the assertions marked "Ignorable" 

In your case, the requestor is aware of a set of assertions that it is willing to ignore. For instance, let's say the requestor's policy alternative contains assertions A & B and the set of assertions that the requestor is willing to ignore contains C & D. That is,

A1 = {A, B, C, D}.

Let's say provider P's policy is,

A2 = {A, B, C-ignorable, D-ignorable}

and provider Q's policy is,

A3 = {A, B, C-ignorable, D-ignorable, X-ignorable}

Using the strict mode policy intersection, A1 & A2 are compatible and A1 & A3 are incompatible. That is, the requestor can ignore a subset of the ignorable assertions. I hope this helps.

Asir S Vedamuthu
Microsoft Corporation

From: public-ws-policy-request@w3.org [mailto:public-ws-policy-request@w3.org] On Behalf Of Prasad Yendluri
Sent: Wednesday, January 10, 2007 11:59 AM
To: public-ws-policy@w3.org
Subject: NEW Issue: How to ignore some "ignorable" assertions only?

Title: How to ignore some of the assertions marked "Ignorable" only?

The current Intersection Algorithm's use of "Strict" and "Lax" modes does not allow for ignoring only  a subset of the assertions marked "Ignorable". In many use cases it is conceivable that the consumer would want to ignore only some of the assertions. 

How to derive the intersection / effective compatible subset that the consumer wants to use with only a subset of the assertions marked ignorable?

Articulated in the description section but, I think it is desirable to enable this.
Target: WS-Policy 1.5 - Framework

Received on Sunday, 14 January 2007 06:08:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:23 UTC