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:33] elisagat:urbiflock [2010/08/04 17:21] – updating elisag
Line 22: Line 22:
 {{ :uf:urbiflock_architecture.png?375x400 |:uf:urbiflock_architecture.png}} {{ :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) 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 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 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. 
  
Line 28: Line 28:
  
   * [[uf:flockr|Flockr]]: A flockr represents a 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 loosely defined group of users.  + 
-  * [[uf:proximities|Characteristic Functions]]: "functions" that determine whether or not a user is proximate+  * [[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
-    isNearbyphysical proximity +  * [[uf:proximities|Characteristic Functions]]: "functions" that determine whether or not a user belongs to a Flock
-    * isFriendstatic encoding of friendship relationships +  [[uf:totam|TOTAM]]tuple-based middleware for flock communication
-    * doesProfileMatch: tests an attribute of a user's profile, form ATTR OP VAL, where ATTR is e.g. age, name, gender, hobbies, ... +  * [[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.
-    * combinators: and, or, not +
-  * [[uf:application|Application]]: define the API of an "application object". What follows is the list of applications in Urbiflock.+
     * [[uf:viewer|Flock Viewer]]: a viewer and editor to view existing flocks and to create new flocks.     * [[uf:viewer|Flock Viewer]]: a viewer and editor to view existing flocks and to create new flocks.
     * [[uf:app_viewer|Application Viewer]]: a viewer and editor to view existing applications and install/delete them.     * [[uf:app_viewer|Application Viewer]]: a viewer and editor to view existing applications and install/delete them.
Line 41: Line 39:
     * [[uf:iflocku|IFlockU]]: a friend suggestor based on profile similarity and time spent in proximity.     * [[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:guanotes|Guanotes]]: a messenger application that sends post-its to flocks.
-    * [[uf:ir8u|IR8U]]: an application that allows you to rate your friends. +    * [[uf:ir8u|IR8U]]: an application that allows users to ask proximate users to rate them on a certain subject.
- +
-==== Applications ==== +
-  * [[uf:viewer|Flock Viewer]]: a viewer and editor to view existing flocks and to create new flocks. +
-  * [[uf:app_viewer|Application Viewer]]: a viewer and editor to view existing applications and install/delete them+
-  * [[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]]: messenger application that sends post-its to flocks. +
-  * [[uf:ir8u|IR8U]]: an application that allows you to rate your friends.+
  
 ==== Target Platforms ==== ==== Target Platforms ====
-Rather than building a platform-independent framework, our aim is to assist in the rapid development of pervasive social networking applications. The Urbiflock framework has been entirely written in the AmbientTalk language. As such, no configuration is required to be able to quickly script new applications on it once AmbientTalk is running on the target platform. +The Urbiflock framework has been entirely written in the AmbientTalk language. As such, no configuration is required to be able to quickly script new applications on it once AmbientTalk is running on the target platform. 
  
-AmbientTalk requires a regular J2SE Java Virtual  +AmbientTalk runs on a regular J2SE Java Virtual  
-Machine supporting version 1.3 or higher. The implementation also runs on the Java 2 micro edition (J2ME) platform, under the connected device configuration (CDC).+Machine supporting version 1.3 or higherJava 2 micro edition (J2ME) platform, under the connected device configuration (CDC), and Android Platform version 1.6 or higher
  
-We have done some test to deploy our framework on HTC touch cruise pda's. In order to configure your HTC Touch device for our framework you can follow the instruction [[private:AmopHTC|here]].+We have implemented a AWT UI interface for Urbiflock's deployment on HTC touch cruise phones running J2ME. In order to configure your HTC Touch device for our framework you can follow the instruction [[private:AmopHTC|here]].
  
-We are currently working on deploying our framework on HTC Hero, a phone running on the Android platform.+We are currently working on an Android UI interface for Urbiflock' deployment on a number of Android phones ( HTC Hero, Legend and Desire, and Sony Xperia X10 series)
  
 ==== Development ==== ==== Development ====
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag