User Tools

Site Tools


at:urbiflock

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
at:urbiflock [2009/11/18 14:17] – adding elisagat:urbiflock [2009/11/18 15:14] elisag
Line 20: Line 20:
  
 The architecture of the Urbiflock framework shown below is divided in three layers: applications, Urbiflock core, and Urbiflock infrastructure.  The architecture of the Urbiflock framework shown below is divided in three layers: applications, Urbiflock core, and Urbiflock infrastructure. 
 +{{ :uf:urbiflock_architecture.png?375x400 |:uf:urbiflock_architecture.png}}
  
- +The application layer includes several core applications which are currently available in the framework such as flock and profile editors, and several users applications such as //I rate you// (IR8U), and //Guanotes//. The Urbiflock's core is composed of three main facilities specially designed to enable social interactivity and deal with the highly dynamic environment to which mobile devices exposes them: flockr, user profile and the TOTAM framework for flock communications. 
-The application layer includes several core applications which are currently available in the framework such as flock and profile editors, and several users applications such as //I rate you// (IR8U) that allows users to ask proximate users to rate them on a certain subject, and //Guanotes//. The Urbiflock's core is composed of three main facilities specially designed to enable social interactivity and deal with the highly dynamic environment to which mobile devices exposes them: flockr, user profile and the TOTAM framework for flock communications. +
 The infrastructure layer consists of three low-level abstractions on which the framework core is based: a RETE engine which orchestrates the flock composition, and the service discovery and communication APIs to discover and communicate with nearby applications, respectively.  The infrastructure layer consists of three low-level abstractions on which the framework core is based: a RETE engine which orchestrates the flock composition, and the service discovery and communication APIs to discover and communicate with nearby applications, respectively. 
  
-In the rest of this subsection we give a general overview of the relevant parts of the framework.+In the rest of this subsection we list the relevant parts of the Urbiflock framework.
  
-  * [[uf:flockr|Flockr]]:representation of the user in the framework +  * [[uf:flockr|Flockr]]: A flockr represents a user in the framework 
-  * [[uf:profiles|Profile]]: manage user's profile and cache profiles of other flockrs +  * [[uf:profiles|User Profile]]: Profiles in Urbiflock represent the user identity (e.g. name, gender, hobbies, etc.).
-  * [[uf:flock|Flock]]: a group of 'proximate' users +
-  * [[uf:proximities|Proximities]]: "functions" that determine whether or not a user is proximate. +
-    * isNearby: physical proximity +
-    * isFriend: static encoding of friendship relationships +
-    * doesProfileMatch: tests an attribute of a user's profile, form ATTR OP VAL, where ATTR is e.g. age, name, gender, hobbies, ..+
-    * combinators: and, or, not +
-  * [[uf:application|Application]]: define the API of an "application object" +
-  * [[uf:applications|Applications]]: manage applications+
  
-==== Applications ==== +  * [[uf:flock|Flock]]: a loosely defined group of users. It is an alternative representation of user groups specially designed to enable the dynamic interaction of social networks in pervasive social applications. A flock is defined in terms of a characteristic function. 
-  * [[uf:viewer|Flock Viewer]]: a viewer and editor to view existing flocks and to create new flocks. +  * [[uf:proximities|Characteristic Functions]]: "functions" that determine whether or not a user belongs to a Flock. 
-  * [[uf:app_viewer|Application Viewer]]: a viewer and editor to view existing applications and install/delete them. +  * [[uf:totam|TOTAM]]: tuple-based middleware for flock communication. 
-  * [[uf:profile_viewer|Profile Viewer]]: a viewer and editor to view existing flockr profiles and to update your profile. +  * [[uf:application|Applications]]: define the API of an "application object" to be plugged in the framework. What follows is the list of applications in Urbiflock. 
-  * [[uf:iflocku|IFlockU]]: a friend suggestor based on profile similarity and time spent in proximity. +    * [[uf:viewer|Flock Viewer]]: a viewer and editor to view existing flocks and to create new flocks. 
-  * [[uf:guanotes|Guanotes]]: a messenger application that sends post-its to flocks. +    * [[uf:app_viewer|Application Viewer]]: a viewer and editor to view existing applications and install/delete them. 
-  * [[uf:ir8u|IR8U]]: an application that allows you to rate your friends.+    * [[uf:profile_viewer|Profile Viewer]]: a viewer and editor to view existing flockr profiles and to update your profile. 
 +    * [[uf:iflocku|IFlockU]]: a friend suggestor based on profile similarity and time spent in proximity. 
 +    * [[uf:guanotes|Guanotes]]: a messenger application that sends post-its to flocks. 
 +    * [[uf:ir8u|IR8U]]: an application that allows users to ask proximate users to rate them on a certain subject.
  
 ==== Target Platforms ==== ==== Target Platforms ====
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag