[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-08-06 Thread Siegfried Gevatter
** Changed in: zeitgeist Milestone: 0.4.1 = 0.5.0 -- What value should subject.origin have? https://bugs.launchpad.net/bugs/487321 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-08-04 Thread Mikkel Kamstrup Erlandsen
** Changed in: zeitgeist Status: Triaged = Fix Released -- What value should subject.origin have? https://bugs.launchpad.net/bugs/487321 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-07-26 Thread Launchpad Bug Tracker
** Branch linked: lp:~zeitgeist/zeitgeist/sort-by-orig -- What value should subject.origin have? https://bugs.launchpad.net/bugs/487321 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-07-02 Thread Mikkel Kamstrup Erlandsen
Considering Siegfried's comment #23 and Michal's comment #24, and with a free interpretation of Seif's domain moniker in comment #27 I think we actually agree more or less on what to put in origin. I'll write a draft docstring and put up a branch for review. Watch this space - we may actually be

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-06-29 Thread Seif Lotfy
Ok this issue has to be settled once and for all IMHO I think it makes sense to look at origin as the domain of the subject of the event in question. Maybe Subject.origin is a better interpretation than event.origin but this would mean an API break. The benefits of having origin follow the

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-06-29 Thread Michal Hruby
I personally don't like that, you can have a simple method which will extract the domain from uri, on the other hand having possibility to create at least a partial tree of how you got to a uri is more useful. -- What value should subject.origin have? https://bugs.launchpad.net/bugs/487321 You

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-06-12 Thread Mikkel Kamstrup Erlandsen
** Changed in: zeitgeist Milestone: 0.3.4 = 0.4.1 -- What value should subject.origin have? https://bugs.launchpad.net/bugs/487321 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-05-14 Thread Michal Hruby
I think that it makes sense to store in subject.origin the location where subject.uri can be found. Therefore the web page visit events could have as origin set either their referrer page or the domain (only if referrer is unavailable, since we can parse the domain from uri anyway). As for

Re: [Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-05-14 Thread Siegfried Gevatter
2010/5/14 Michal Hruby michal@gmail.com: Therefore the web page visit event could have as origin set -- the domain Completely agree. As for Mikkel's IM use case, I don't think it's ZG's job to log every message, so there'd be only some kind of CONVERSATION_STARTED event Completely agree.

Re: [Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-05-14 Thread Seif Lotfy
So lets say i switched from i opened a website the a document will the website be the origin of the document... if yes i think this is kinda wrong. since we are talking about a subject origin as opposed to what you are suggesting what i would call a event origin... Lets have an irc meeting... With

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-04-12 Thread Siegfried Gevatter
** Changed in: zeitgeist Milestone: 0.3.1 = 0.3.4 -- What value should subject.origin have? https://bugs.launchpad.net/bugs/487321 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-01-08 Thread Mikkel Kamstrup Erlandsen
One use case I want to cover also is IM messages, I am working on a Telepathy observer that logs chats to Zg. How would I model this via the Zg datamodel? Let's see... So I observe that john@example.com sends me the message Hello Dolly via MSN. His real name is John Doe, I can this from

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-01-08 Thread Mikkel Kamstrup Erlandsen
I missed a subject.uri in my previous comment... I don't really know what to store in there..? -- What value should subject.origin have? https://bugs.launchpad.net/bugs/487321 You received this bug notification because you are a member of Zeitgeist Developers, which is the registrant for

Re: [Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-01-08 Thread Seif Lotfy
u forgot the subject uri I agree we shouldnt put telepathy.desktop in This is a use case where empathy cant even inform us what happened since we r hooked into telepathy. plus a telepathy .desktop does nto exist. yet i see no alternative atm. Let us think about it today in some sort of meeting...

Re: [Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-01-08 Thread Siegfried Gevatter
2010/1/8 Mikkel Kamstrup Erlandsen mikkel.kamst...@gmail.com: subject.origin = mailto:john@example.com; Good point. I suppose finding out whether you are talking to John Doe because you clicked on a link in some file isn't really doable, so storing the mail there for IM and the web for

Re: [Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-01-07 Thread Seif Lotfy
yes event origin should tell us which subject triggered it but Again this is going to be a hard implementation. Imagine opening a doc, then quickly check mail, then open something related to the doc (call it x). the little mail there messes up the equations plus there is not way to have the

Re: [Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-01-07 Thread Siegfried Gevatter
2010/1/7 Seif Lotfy s...@lotfy.com: yes event origin should tell us which subject triggered it but Again this is going to be a hard implementation. Imagine opening a doc, then quickly check mail, then open something related to the doc (call it x). No, because origin would be something the data

Re: [Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2010-01-07 Thread Seif Lotfy
We will then have to fully rely on external dataproviders for that 2010/1/7 Siegfried Gevatter rai...@ubuntu.com 2010/1/7 Seif Lotfy s...@lotfy.com: yes event origin should tell us which subject triggered it but Again this is going to be a hard implementation. Imagine opening a doc, then

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2009-12-08 Thread Mikkel Kamstrup Erlandsen
There is no need for event origin. If u want the origin of an event u look for the subject of the event before The client has no rigorous way to find out which event came before. We can apply heuristics, but I don't like that -- What value should subject.origin have?

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2009-12-08 Thread Mikkel Kamstrup Erlandsen
there are three interesting URIs to log: - The URL my brower window points to That's what I consider as origin, and why I'm asking for other stuff to use a different name (be it domain or whatever else). Ok. Let's skip the finer details of the naming as long as we agree on the basic

Re: [Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2009-12-08 Thread Siegfried Gevatter
2009/12/8 Mikkel Kamstrup Erlandsen mikkel.kamst...@gmail.com: So you don't consider the actual URL that I download part of the event? No. If the user just downloaded a file, he will want to work with the local version, not download it again. Knowing where the file came from is also important

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2009-12-07 Thread Seif Lotfy
Ok lets keep origin at the physical location at which the subject resided. This can be closed if we just agree. -- What value should subject.origin have? https://bugs.launchpad.net/bugs/487321 You received this bug notification because you are a member of Zeitgeist Framework, which is the

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2009-12-07 Thread Mikkel Kamstrup Erlandsen
I think Physical location at which the subject resided at the moment of interaction is a good formulation. It is still incomplete though. We need to define whether or not trailing slashes should be included - and stuff like that. I'd like to keep this bug open until all of this is thoroughly

[Zeitgeist] [Bug 487321] Re: What value should subject.origin have?

2009-12-03 Thread Seif Lotfy
IMHO we should stick to using the origin as the domain of the subject /path/to/file == /path/to youtube.com/aflkasflkasjf == aflkasflkasjf It will give us the option of knowing which are the most used documents in a folder or most watched videos on youtube.com -- What value should