Event Interpretations Ontology

[Seif Lotfy]

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

[Seif Lotfy (seif)]

GUYS PLEASE LOOK AT THIS

[Mikkel Kamstrup Erlandsen (kamstrup)]

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.

[Seif Lotfy (seif)]

OK then i will change the recentlyused manager IF SIEGFRIED AND MARKUS AGREE
plus i have some thoughts baotu the ontology that she be taken in consideration

[Mikkel Kamstrup Erlandsen (kamstrup)]

This is very related to the whole events ontology thing, and must also be meticulously documented in our API docs. Since I am knee deep in both, I'll assign this bug to myself.

[Seif Lotfy (seif)]

So after last nights heated discussion i think we agreed on
access, leave, create, delete, modify, send, receive (copy, paste) as our only event interpretations for now...
I will start the implementation today

[Markus Korn (thekorn)]

I think with our ontology stuff we can consider this bug as fixed.