This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6687 - Eventing - order of filter vs format processing
Summary: Eventing - order of filter vs format processing
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
Keywords: hasProposal
Depends on:
Reported: 2009-03-11 18:15 UTC by Doug Davis
Modified: 2009-04-21 21:32 UTC (History)
0 users

See Also:


Description Doug Davis 2009-03-11 18:15:10 UTC
Now that we have Format feature we need to make it clear that the filtering is done _before_ any formatting of the events happens.

We have new text for Format that looks like (from proposal):
In order to support this broad variety of event delivery requirements, this specification introduces an abstraction called a Delivery Mode and an abstraction called Delivery Format. These concepts are used as extension points, so that event sources and event consumers may freely create new delivery mechanisms that are tailored to their specific requirements. This specification provides a minimal amount of support for delivery mode and format negotiation by allowing an event source to provide a list of supported delivery modes and formats in response to a subscription request specifying a delivery mode or format it does not support.

add to the end:
When the Delivery Format feature is engaged the formatting of the
going events occurs after any filtering. This ensures that regardless
of what type of formatting might occur, the same Filter dialect/expression
can be used to subset the event stream.
Comment 1 Robert Freund 2009-03-17 20:43:14 UTC
proposal in description accepted
Comment 2 Doug Davis 2009-03-17 23:46:24 UTC