W3C home > Mailing lists > Public > public-ws-addressing@w3.org > April 2007

Non-anon extensibility and policy intersection

From: David Hull <dmh@tibco.com>
Date: Mon, 23 Apr 2007 17:28:07 -0400
Message-ID: <462D24E7.8030905@tibco.com>
To: "public-ws-addressing@w3.org" <public-ws-addressing@w3.org>

A while ago I suggested that we have a way of saying things like
"non-anon response endpoints must be mailto: (or fit some other
pattern)".  Our decision was to leave this out of scope, which is fine
with me, but we want to be sure not to disallow it.

Suppose I make an assertion, basically "the service support non-anon",
generically.  Later, you want to refine that by saying, "Well, actually,
the service only supports mailto: non-anon".  As I understand it, policy
intersections are aimed at this sort of thing.

However, if I intersect a policy that says "non-anon allowed" with one
that says "mailto: only", I get the empty set, since the two assertions
are different.  I would like to get "mailto: only".
Received on Monday, 23 April 2007 21:28:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:17 GMT