Observer Service Like the human visual system providing a way to focus only on a subpart of what a human actually views, the observer service allows a user (or an agent) to focus his perception on a certain aspect of the activity of the community according to his intentions.
the activity around my published posts (e.g. who read it)
Resource oriented activity:
new messages related to a given topic/issue
only popular/important messages about a topic because I’m not so much a fan about that topic
Observer Service: granularity aspect Example of user’s profile for the topic aspect. The distribution of the thresholds of interest by topic. ( for a given topic the more the level is high, the more the messages about this topic are filtered to receive only the important ones) Example of user’s profile for the SN aspect. The distribution of the thresholds of interest for the member of his SN/community. ( for a given user , the more the level is high, the more the messages from this user are filtered to receive only the important ones)
Configuring my perception of the environment (i.e. the information I will receive from it) according to:
- my interest (I’m a priori more interested by posts about technology than about business).
my affinity in a Social Network (I’m a priori more interested by new posts from my friend user A than the work of the user B)
Arborescence of the event’s properties Description event.type The type of event (creating, reading, etc..) event.source The source’s name where the event comes (a specific community , skype or email, web feed) event.resource.id The ‘s id of the resource event.resource.tag The tag belonging to the resource , (e.g. the message’s topic) event.resource.type (e.g. a message, a conversation , a user) event.resource.activitylevel The level of activity (e.g. number of time a message has been read, or could be the % of diffusion in the community (i.e ratio readers/members) event.author The author’s name of the event event.author.tag The author’s tag (e.g. the author’s role, the author’s team)
Usage (no user interface for the moment, just an url to create)
Arguments: A combination of criteria following the format:
event.property = value according to the event model describe
Results : A web feed
Examples: A member wishes to be informed:
When new threads are created. http://perceptionmodule/watch? event.ressource.type=thread & event.type=creating
When of new threads are created on the “technology” subject. http://perceptionmodule/watch? event.ressource.type=thread & event.type=creating
Only about important threads on meeting (i.e. a high level of activity).
http://perceptionmodule/watch? event.ressource.type=thread & event.type=creating & event.resource.activitylevel=20 & event.resource.tag=meeting … see Delivrable 3.2 for more examples
So the user can create several web feeds to perceive the activity of the environment according to his profile of interest/social network (e.g. configuring each web feed for a given topic with a given threshold of of interest), as described in the slide #11