On Wed, Sep 8, 2010 at 2:15 PM, Ethan Jewett <[email protected]> wrote: > On Wed, Sep 8, 2010 at 1:57 PM, Richard Hirsch <[email protected]> wrote: >> On Wed, Sep 8, 2010 at 1:02 PM, Ethan Jewett <[email protected]> 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 >
