WS-Eventing needs to cover the following case: a Subscribe message is sent to
an Event Source that supports filtering. The Subscribe message contains a
wse:Filter element. The value of the @Dialect attribute of this element is
understood and supported by the Event Source. However, due to various
properties of the filter and/or the Event Source, the Event Source can
determine that no Notifications will ever match this filter.

1.) We should define a fault for this condition, perhaps
"EmptyFilterSpecified".

2.) In general it is not possible for an Event Source to determine, at
Subscribe time, whether there will ever be any Notifications that match the
filter. However, some Subscribers may want to know if any checking was done to
determine if the filter was empty. There are a range of things we can do from
offering some pious advice to Event Sources to make "best efforts" to defining
policy assertions that describe, on a per-Dialect basis, the amount of checking
that is performed.

Strawman proposal: define new fault and offer some pious advice on making "best
efforts" to determine if the filter is empty.

proposal at
http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0055.html

discussion at
http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0056.html

Action-41 on Gil

proposal at
http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0077.html

2009-03-24 resolved with proposal contained in comment 4