[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsn] Analysis of filtering
Where
do we draw the line? Defining nesting may not be so hard for us, but the
specification is not exactly aimed at ourselves :-)
There
are all sorts of possibilities for composing filters ranging from defining
simple commutative filters (which is what we should include in the spec,
IMHO), all the way to someone deploying entire business rules in the form
of filters. One may possibly compose rules for detecting when a
particular IT event qualifies as a Sarbanes Oxley material event and put
these rules in the form of filters in the Subscription! What is the
complexity of such rules language - I don't know. Do we want to explicitly
prohibit such usage - I don't think so either.
So
basically, if we bake in simple filters and simple rules for their
composition in the core spec, we will have a simple and
fairly useful spec for majority of the use cases and we will still leave the
door open for unlimited extensibility for those advanced users out
there.
Just
my 2 cents.
Thanks,
Sanjay
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]