I think open/close/modify makes the most sense. I prefer 'modify' over
'save' since fx. editing a contact or something like that is done in an
instant-apply dialog, without any notion of "saving".

Of course this whole deal is just a corner of our bigger problem - that
we need an event ontology. I'll start writing one down now, but it will
not be ready for this weekend. So I think we should just go with
open/close/modify for 0.3.0 and take our chance that we can build up a
good ontology around that without having to break the ontology when we
finalize it.

-- 
Interpretation conventions
https://bugs.launchpad.net/bugs/489262
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.

Status in Zeitgeist Framework: Triaged

Bug description:
I think using
visit/modified is non-sense
I would push for replacing it with open/close/saved
THIS IS CRITICAL FOR THE DATAPROVIDERS AS WELL AS CLIENT APPS


_______________________________________________
Mailing list: https://launchpad.net/~zeitgeist
Post to     : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help   : https://help.launchpad.net/ListHelp

Reply via email to