On Mon, Oct 27, 2008 at 6:23 PM, Boris Burtin <[EMAIL PROTECTED]> wrote: > > ----- "Robert Burrell Donkin" <[EMAIL PROTECTED]> wrote: > >> just FYI there's currently a standardisation effort underway for xml >> representation of sieve scripts >> http://tools.ietf.org/id/draft-freed-sieve-in-xml-01.txt >> >> 1 maybe you'd be in a position to provide useful feedback > > Hey Robert. Thanks for pointing this out. I didn't realize that others are > thinking about representing filter rules as XML. I think our goals at Zimbra > are a bit >different.
maybe, maybe not :-) IMHO the current standards effort is skewed towards big *nix vendors but there are a number of people also interested in other types of applications. > For simplicity's sake, we limit the kinds of scripts that users can generate. > This makes it easier to write a UI-based filter rule editor. AIUI there are a number of people interested in this. it may be possible to make contact with them through the standards list. >A general-purpose XML mapping is more than we need at this point. I'll keep >this RFC in the back of my mind if we need to expand the filtering >functionality >in the future. IMO a lot of the current standards effort is unfortunately skewed towards >> 2 a suitable visitor might be useful for standard or custom >> transformation to xml > > I wrote a visitor framework for what I'm doing, just to maintain my sanity > with tree navigation. Currently there's a good amount of Zimbra-specfic > stuff i there. > Let me poke around and see if I can split out the general > node navigation code. Should be easy enough to write a Node->String > converter once that's in > > place. great i think that it should be possible reasonably quick to come up with a visitor framework that would allow pluggable translation to xml. even if it's coded from scratch, feedback from one real life application would be very useful. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
