Re: [Zeitgeist] [Bug 487321] Re: What value should subject.origin have?
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. :) -- 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 Framework: Triaged Bug description: + origin = info.get_uri().rpartition(/)[0] WHY? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 487321] Re: What value should subject.origin have?
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 the wildcards coming up we could rethink that... On Fri, May 14, 2010 at 8:19 PM, Siegfried Gevatter rai...@ubuntu.comwrote: 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. :) -- What value should subject.origin have? https://bugs.launchpad.net/bugs/487321 You received this bug notification because you are subscribed to The Zeitgeist Project. Status in Zeitgeist Framework: Triaged Bug description: + origin = info.get_uri().rpartition(/)[0] WHY? -- This is me doing some advertisement for my blog http://seilo.geekyogre.com -- 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 Framework: Triaged Bug description: + origin = info.get_uri().rpartition(/)[0] WHY? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 487321] Re: What value should subject.origin have?
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... when do u have time? 2010/1/8 Mikkel Kamstrup Erlandsen mikkel.kamst...@gmail.com 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 Zeitgeist Framework. Status in Zeitgeist Framework: Triaged Bug description: + origin = info.get_uri().rpartition(/)[0] WHY? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp -- 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 Zeitgeist Framework. Status in Zeitgeist Framework: Triaged Bug description: + origin = info.get_uri().rpartition(/)[0] WHY? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 487321] Re: What value should subject.origin have?
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 browser activities (if you agree with having that) sounds good to me. Can we find some description for the origin field which covers both cases without having to list them explicitly (ie. not having a different explanation of it for every activity type)? It doesn't make much sense to store app://telepathy.desktop or app://empathy.desktop in event.actor because I have no way of knowing which app shows the message to the user Uhm, that may be problematic. Maybe we can just have something a la genericapp://im and let apps look up what the default IM client is and show that. There may be different clients for supporting different protocols though, so it's not so easy. I missed a subject.uri in my previous comment... I don't really know what to store in there..? IMHO it should be something which when clicked shows the logs of the conversation. I discussed this with Gerfried Fuchs (upstream developer for the IRC client Smuxi), who wants to add Zeitgeist support to Smuxi, and he said he'd think of a scheme for irc://, which we can then discuss with other IM client developers. -- Siegfried-Angel Gevatter Pujals (RainCT) Free Software Developer 363DEAE3 -- 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 Zeitgeist Framework. Status in Zeitgeist Framework: Triaged Bug description: + origin = info.get_uri().rpartition(/)[0] WHY? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 487321] Re: What value should subject.origin have?
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 event.origin(x) = doc just my opinion 2010/1/7 Siegfried Gevatter rai...@ubuntu.com 2009/12/8 Mikkel Kamstrup Erlandsen mikkel.kamst...@gmail.com: Domain seems to imply that it is the place where the subject is currently located. It also strikes me as a very vague and possibly ambiguous word here. Agreed, root would be a better name. If we take an example where I donwload the file from the above URL, there are three interesting URIs to log: I don't remember how we came to discussing this, but let me explain my position on this again. If you really want root -let's call it like this for now- for optimizing whatever you want to optimize (I'm still not sure what you want it for...), then it should be an implementation detail which isn't exposed in the API. It doesn't make any sense for it to be there. Completely unrelated, I propose that we add a new property to events, called origin. This property would cover where does this event come from, ie. what other subject triggered it. So for example if you open project.odt and there click on searchengine.com and search for elephants which brings you to searchengine.com/elephants and there you click on elephants.com/the-truth-about-them that would give you the events: - uri: file:///home/humanoid/project.odt, origin: None - uri: searchengine.com, origin: file:///home/humanoid/project.odt ... some other events because in the middle you talked to an IM contact ... - uri: searchengine.com/elephants, origin: searchengine.com ... some other events because you switched to another tab and looked up photos of elements there ... - uri: elephants.com/the-truth-about-them, origin: searchengine.com/elephants The case of downloads gets more complicated so let's not get into it just right now. Cheers, -- Siegfried-Angel Gevatter Pujals (RainCT) Free Software Developer 363DEAE3 -- What value should subject.origin have? https://bugs.launchpad.net/bugs/487321 You received this bug notification because you are subscribed to The Zeitgeist Project. Status in Zeitgeist Framework: Triaged Bug description: + origin = info.get_uri().rpartition(/)[0] WHY? -- 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 Zeitgeist Framework. Status in Zeitgeist Framework: Triaged Bug description: + origin = info.get_uri().rpartition(/)[0] WHY? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 487321] Re: What value should subject.origin have?
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 quickly check mail, then open something related to the doc (call it x). No, because origin would be something the data provider gives (in my example above, I guess we can forget for now about knowing that searchengine.com came from the ODT, but the other ones between Firefox items only are certainly possible). -- Siegfried-Angel Gevatter Pujals (RainCT) Free Software Developer 363DEAE3 -- What value should subject.origin have? https://bugs.launchpad.net/bugs/487321 You received this bug notification because you are subscribed to The Zeitgeist Project. Status in Zeitgeist Framework: Triaged Bug description: + origin = info.get_uri().rpartition(/)[0] WHY? -- 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 Zeitgeist Framework. Status in Zeitgeist Framework: Triaged Bug description: + origin = info.get_uri().rpartition(/)[0] WHY? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
