Re: [Zeitgeist] Structure and items of an event object

2009-07-20 Thread Mikkel Kamstrup Erlandsen
2009/7/20 Siegfried Gevatter : > I tend to agree with your comment but I'm unsure about one thing: > >>> With this mindset it also makes sense to differentiate the lookup >>> functions, so we have something like: >>> >>>  FindEvents(...filters...) >>>  FindItems(...filters...) > > Maybe I'm just mi

Re: [Zeitgeist] Structure and items of an event object

2009-07-20 Thread Mikkel Kamstrup Erlandsen
2009/7/20 Seif Lotfy : > > >> 2009/7/20 Mikkel Kamstrup Erlandsen SNIP > LOVE IT LOVE IT LOVE IT > however what happens if i want to log an event where the subject has not > been registered yet? My initial idea here was to accept that and create a dummy item for that uri. Haven't given it deep th

Re: [Zeitgeist] Structure and items of an event object

2009-07-20 Thread Siegfried Gevatter
I tend to agree with your comment but I'm unsure about one thing: With this mindset it also makes sense to differentiate the lookup functions, so we have something like:  FindEvents(...filters...)  FindItems(...filters...) Maybe I'm just misunderstanding that, but if you imply that FindEvents

Re: [Zeitgeist] Structure and items of an event object

2009-07-20 Thread Seif Lotfy
2009/7/20 Mikkel Kamstrup Erlandsen > 2009/7/17 Seif Lotfy : > > Hey Here is my take again on the issue > > An event is something that happens > > Something happens needs and application to triger it and a target on > which > > the happening takes place (in our case a doc, note or webpage) > > >

Re: [Zeitgeist] Structure and items of an event object

2009-07-20 Thread Mikkel Kamstrup Erlandsen
2009/7/17 Seif Lotfy : > Hey Here is my take again on the issue > An event is something that happens > Something happens needs and application to triger it and a target on which > the happening takes place (in our case a doc, note or webpage) > > So my current proposal is to send around a tuple of

Re: [Zeitgeist] Structure and items of an event object

2009-07-16 Thread Seif Lotfy
Hey Here is my take again on the issue An event is something that happens Something happens needs and application to triger it and a target on which the happening takes place (in our case a doc, note or webpage) So my current proposal is to send around a tuple of 2 dicts that describe the event:

Re: [Zeitgeist] Structure and items of an event object

2009-07-16 Thread Mikkel Kamstrup Erlandsen
2009/7/16 markus korn : > > I just found a few issues and a few things I would like to discuss: > 1a.) although it is stated here otherwise, mimetype is not an optional > entry, the engine itself will discard events without a mimetype > 1b.) is mimetype really required for an event? Seif: as you ar

Re: [Zeitgeist] Structure and items of an event object

2009-07-15 Thread markus korn
On Thu, Jul 16, 2009 at 12:10 AM, markus korn wrote: > 1a.) although it is stated here otherwise, mimetype is not an optional > entry, the engine itself will discard events without a mimetype > 1b.) is mimetype really required for an event? Seif: as you are > working on this application watcher, wh