at:urbiflock
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
at:urbiflock [2008/09/05 11:21] – tvcutsem | at:urbiflock [2010/10/19 19:28] – * elisag | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Urbiflock ====== | ====== Urbiflock ====== | ||
- | ==== What is Urbiflock? ==== | + | ===== What is Urbiflock? |
- | Urbiflock | + | UrbiFlock |
- | ==== Terminology ==== | + | Urbiflock is a Facebook-like application framework for mobile devices. As in Facebook, users that join Urbiflock can meet other users and interact with them. For example users may broadcast announcements to each other, they can browse one another’s profile, launch interactive polls, etc. The framework takes care of managing a user’s social networks, called “flocks”. A flock represents a loosely-defined group of users. A flock can be compared to a Facebook group (for example, a group of your old classmates), |
- | * Flock: a group of proximate users | + | Users can also build applications and plug them into the Urbiflock framework. Several core applications are currently available in the Urbiflock framework, such as flock creators and profile viewers. The framework also counts with two user applications //I rate you (IR8U)// that allows users to ask proximate users to rate them on a certain subject, and // |
- | * Flockr: a user of the urbiflock | + | |
+ | ===== Terminology ===== | ||
+ | |||
+ | * Flockr: a user of the Urbiflock | ||
+ | * Flock: a group of users | ||
* To flock: to become part of a group | * To flock: to become part of a group | ||
- | ==== Modules | + | ===== Demo ===== |
- | * [[uf: | + | |
- | * [[uf: | + | < |
- | * [[uf: | + | <object width=" |
- | * isNearby: physical proximity | + | </ |
- | * isFriend: static encoding of friendship relationships | + | |
- | * doesProfileMatch: | + | ===== Target Platforms ===== |
- | * combinators: | + | The Urbiflock framework has been written in the AmbientTalk language. As such, no configuration |
- | | + | |
- | * [[uf: | + | AmbientTalk runs on a regular J2SE Java Virtual |
- | | + | Machine supporting version 1.3 or higher, Java 2 micro edition (J2ME) platform, under the connected device configuration (CDC), and Android Platform version 1.6 or higher. |
+ | |||
+ | We have implemented a AWT UI interface for Urbiflock' | ||
+ | |||
+ | We are currently working on an Android UI interface for Urbiflock' | ||
+ | |||
+ | The Urbiflock framework is available in the AmbientTalk distribution library under the frameworks/ folder. Visit [[http:// | ||
+ | |||
+ | ===== The Urbiflock framework architecture ===== | ||
- | A flock is defined as a list of references to ' | + | The architecture |
+ | {{ : | ||
- | Predefined Flocks: | + | The application layer includes the API of an " |
- | * friend flockrs: isFriend | + | * [[uf:viewer|Flock Viewer]]: a viewer and editor to view existing flocks and to create new flocks. |
- | * nearby flockrs: isNearby | + | * [[uf:profile_viewer|Profile Viewer]]: a viewer and editor to view existing flockr profiles and to update your profile. |
- | * nearby friend flockrs: isFriend & isNearby | + | * [[uf: |
- | ==== Architecture ==== | + | There are also several user applications in the framework: |
- | An ad hoc RETE-network. Events | + | * [[uf:guanotes|Guanotes]]: |
- | * discovery: '' | + | * [[uf:ir8u|IR8U]]: |
- | * profile changes: '' | + | * [[uf:iflocku|IFlockU]] |
- | * friend changes: '' | + | |
- | These events are received by the local flockr user object | + | The Urbiflock' |
- | As a first implementation of the RETE-network, | + | * [[uf: |
+ | * [[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. It is an alternative representation of user groups that allows the semantic specification of user groups in a modular manner and manages the constant changes of the group' |
- | def flockrTemplate | + | * [[uf: |
- | def name := *; // wildcard, | + | |
- | def age := constraint: { _ < 25 }; // must be younger than 25 | + | |
- | | + | |
- | def street := *; //any street,but street name must be filled | + | |
- | def city := "Brussel"; // city must equal this string | + | |
- | }; | + | |
- | def greet(); // person must have a greet method | + | |
- | } taggedAs: | + | |
- | </ | + | |
- | ==== Applications ==== | + | The infrastructure layer consists of three low-level abstractions on which the framework core is based: a RETE engine which orchestrates the flock composition, |
- | * [[uf:appmgr|Application Manager]]: allows | + | |
- | er to view installed applications, | + | ===== Further Reading ===== |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | ==== To think about ==== | + | **Flocks: Enabling Dynamic Group Interactions in Mobile Social Networking Applications**. E. Gonzalez Boix, A. Lombide Carreton, C. Scholliers, T. Van Cutsem, W. De Meuter, T. D' |
- | | + | |
- | | ||
- | * [[uf: |
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag