** 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 Framewo
** 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 Zeitgeis
** 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 Framewo
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
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 re
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 pro
** 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 Framewo
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
2010/5/14 Michal Hruby :
> 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 valu
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 Mikkel'
** 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 Framewo
2010/1/8 Mikkel Kamstrup Erlandsen :
> 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
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...
w
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 Zeitgeis
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 Tele
We will then have to fully rely on external dataproviders for that
2010/1/7 Siegfried Gevatter
> 2010/1/7 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, the
2010/1/7 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).
No, because "origin" would be something the data provider
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.o
2009/12/8 Mikkel Kamstrup Erlandsen :
> "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
Unless we can settle this issue right now I think we should punt this to
0.3.2
--
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.
St
I am not sure Tracker's goal is to store metadata about non-existing
items (fx. if I delete an image Tracker also forgets that the image had
a width of 500px, but I could be wrong). Indeed I may also download a
file to a directory Tracker is not even monitoring.
The origin URL of a file is certain
2009/12/8 Mikkel Kamstrup Erlandsen :
> 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 (in case you want to give s
>> 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
> 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?
https://bugs.launc
2009/12/8 Mikkel Kamstrup Erlandsen :
> If we take an example where I donwload the file from the above URL,
> 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 "do
2009/12/8 Mikkel Kamstrup Erlandsen
> Siegfried, I think you need to elaborate a bit in order to make that
> comment useful...
>
> "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. Fx. the
Siegfried, I think you need to elaborate a bit in order to make that
comment useful...
"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. Fx. the "domain" of an RDF property is the range
in whic
Please rename it to "domain" then.
--
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 registrant for Zeitgeist Framework.
Status in Zeitgeist Framework: Triaged
Bug des
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 docu
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 registr
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 subject.ori
** Summary changed:
- Origin
+ What value should subject.origin have?
** Changed in: zeitgeist
Assignee: (unassigned) => Mikkel Kamstrup Erlandsen (kamstrup)
** Changed in: zeitgeist
Importance: Undecided => High
** Changed in: zeitgeist
Status: New => Triaged
--
What value sho
32 matches
Mail list logo
