6595 2009-02-19 06:45:48 +0000 Eventing: WS-Eventing needs to specify behavior for empty filters 2009-04-21 21:32:48 +0000 1 1 1 Unclassified WS-Resource Access Eventing FPWD All All CLOSED REMIND hasProposal P2 normal --- 1 gilbert.pilz gilbert.pilz bob dug public-ws-resource-access-notifications oldest_to_newest 23824 0 gilbert.pilz 2009-02-19 06:45:48 +0000 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. 24152 1 bob 2009-03-11 09:57:34 +0000 proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0055.html 24153 2 bob 2009-03-11 09:58:56 +0000 discussion at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0056.html 24169 3 bob 2009-03-11 17:45:22 +0000 Action-41 on Gil 24326 4 bob 2009-03-19 09:53:57 +0000 proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0077.html 24395 5 bob 2009-03-24 19:49:51 +0000 2009-03-24 resolved with proposal contained in comment 4