1.
observer service ongoing research (started in feb 07) Nicolas Maisonneuve INSEAD CALT http://www.calt.insead.edu/

2.
It’s about <ul><li>Context: </li></ul><ul><ul><li>The belonging to several virtual Communities 2.0 (of practice/interest) exposing their activity data with a web feed (RSS/Atom) mechanism </li></ul></ul><ul><li>Problem: </li></ul><ul><ul><li>Situation awareness overload </li></ul></ul><ul><li>Approach: </li></ul><ul><ul><li>Mechanism to create a customizable perception of the communities’ activity </li></ul></ul><ul><li>Futur works </li></ul>

3.
Context

4.
Context

5.
Problem

6.
Problem

7.
Problem / approach

8.
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.

9.
Observer Service

10.
Observer Service: focus aspect <ul><li>Examples: </li></ul><ul><li>I want to be aware only about </li></ul><ul><li>People oriented activity: </li></ul><ul><ul><li>When new people are connected </li></ul></ul><ul><ul><li>the activity of a friend in a given community.. </li></ul></ul><ul><ul><li>the activity around my published posts (e.g. who read it) </li></ul></ul><ul><li>Resource oriented activity: </li></ul><ul><ul><li>new messages related to a given topic/issue </li></ul></ul><ul><ul><li>only popular/important messages about a topic because I’m not so much a fan about that topic </li></ul></ul>

11.
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) <ul><li>Configuring my perception of the environment (i.e. the information I will receive from it) according to: </li></ul><ul><li>- my interest (I’m a priori more interested by posts about technology than about business). </li></ul><ul><li>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) </li></ul>

12.
How create a channel? <ul><li>Model of an event </li></ul><ul><li>Event = {user, action/type, resource (optional), date, source}. </li></ul>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)

13.
How create a channel? <ul><li>Usage (no user interface for the moment, just an url to create) </li></ul><ul><li>URL: http://perceptionmodule/watch </li></ul><ul><li>Arguments: A combination of criteria following the format: </li></ul><ul><li> event.property = value according to the event model describe </li></ul><ul><li>Results : A web feed </li></ul><ul><li>Examples: A member wishes to be informed: </li></ul><ul><li>When new threads are created. http://perceptionmodule/watch? event.ressource.type=thread & event.type=creating </li></ul><ul><li>When of new threads are created on the “technology” subject. http://perceptionmodule/watch? event.ressource.type=thread & event.type=creating </li></ul><ul><li>& event.resource.tag=technology </li></ul><ul><li>Only about important threads on meeting (i.e. a high level of activity). </li></ul><ul><li>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 </li></ul><ul><li>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 </li></ul>

14.
Futur works <ul><li>Research aspect </li></ul><ul><ul><li>Attention model for the social activity: use the analogy with the visual attention models (visual sampling / visual search used in aviation and robotics) </li></ul></ul><ul><ul><li>Integration of attention profiles (APML) </li></ul></ul><ul><ul><li>Improve the event model with social and activity properties to be able to filter/rank events (e.g. include a level of reputation for an author) </li></ul></ul><ul><ul><li>(information ranking model according to a selected attention profile) </li></ul></ul><ul><li>Development aspect </li></ul><ul><ul><li>UI for the end-user (web2.0 widget) </li></ul></ul><ul><ul><li>Integrate conversations from email/skype (perception module) </li></ul></ul><ul><ul><li>Integration of visualization (people tag cloud as a useful visualization tool in a SN context , see my blog http://nico.maisonneuve.free.fr ) </li></ul></ul>

15.
Watch Service