Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of hirsch.dick@gmail.com
 designates 209.85.215.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=gA+EUby78dX6Tb/qUNZvlM/cW2D3dpAuqyao+hf+VBBe58Y7EMCYERRMWKqaHYssIQ
         ey5cjlRhG2utwwHICMniuN9Yw6zkgNqq5YRWvSH70UebY0ppcoFElDv4jcvVCBLv5C3b
         qF1AhondBitbnbKTghQ8a+RZl4wMsXGjUvdVo=
MIME-Version: 1.0
In-Reply-To: <AANLkTinjURYkU3QPcDRuzG9zs-szNYYSh4ybnT3xsvhg@mail.gmail.com>
References: <AANLkTimawYdsYfLSGrgZoj-J2t7o88Pk=0yjRx2w=_BR@mail.gmail.com>
	<AANLkTi=m2wUDQyqDfOG9SFv4XNK7fH7_x6F-CqVd1tVB@mail.gmail.com>
	<AANLkTi=k+DhZ9ZRfKj5WB9kd8jDyXjTYb4T+5LXsTBpn@mail.gmail.com>
	<AANLkTinjURYkU3QPcDRuzG9zs-szNYYSh4ybnT3xsvhg@mail.gmail.com>
Date: Wed, 8 Sep 2010 15:20:10 +0200
Message-ID: <AANLkTimTNuYT6Moj6-Myg-dtXCwD=XaodUWGiQ0+e0ZM@mail.gmail.com>
Subject: Re: Filters / actions
From: Richard Hirsch <hirsch.dick@gmail.com>
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Sep 8, 2010 at 2:15 PM, Ethan Jewett <esjewett@gmail.com> wrote:
> On Wed, Sep 8, 2010 at 1:57 PM, Richard Hirsch <hirsch.dick@gmail.com> wrote:
>> On Wed, Sep 8, 2010 at 1:02 PM, Ethan Jewett <esjewett@gmail.com> wrote:
>
>>> 1. A wizard-based UI for setting up actions (we can keep the
>>> expert-mode, but I think we need a guided way to set these up)
>>
>> lift has a new wizard framework - maybe we should take a look at that
>
> My thoughts exactly :-)
>
>> There are also some things missing that Ray mentions (like location.)
>> I've been thinking about have an action test that looks at a message
>> meta-data - we could probably cover a lot with that - I don't exactly
>> what sort of syntax would be necessary (XPath?)
>
> Regarding location, my preference would be to canonicalize the way
> that ESME stores location data in the metadata. We could just do it in
> the web client and document it, basically saying, "If you want to
> store location data in a way that ESME knows about, do it this way,
> and if you want to store it some other way in the metadata, that's
> fine too."

look at the twitter annotations for 'place' for a good foundation :
http://dev.twitter.com/pages/annotations_overview
>
> Regarding actions that filter arbitrarily based on metadata, the
> metadata isn't necessarily XML so XPath would be of limited use. In
> the discussion a couple months ago we stopped short of deciding on the
> structure of the metadata, so it is hard to say how we would allow
> filtering it. It's probably a discussion we should finish first,
> before deciding on location or filtering.

Agreed

>
> Ethan
>