Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PDS Architecture"
(→A Common Vocabulary) |
(→Naming: Entity and Context Ids) |
||
Line 51: | Line 51: | ||
Data that is either created by the user and stored on the PDS or passes through the PDS intermediary on its way from the data source to the data consuming service can in many cases be mapped into a rich, common data model. This allows it to be consistently displayed to, and in some cases edited by, the user irrespective of its original source. The common data model being developed for the purpose of representing people and their social networks is called the [[Persona Data Model 2.0]]. The [[Persona Data Model 2.0]] builds on the [[Higgins Data Model 2.0]] which defines a small set of fairly abstract attributes. | Data that is either created by the user and stored on the PDS or passes through the PDS intermediary on its way from the data source to the data consuming service can in many cases be mapped into a rich, common data model. This allows it to be consistently displayed to, and in some cases edited by, the user irrespective of its original source. The common data model being developed for the purpose of representing people and their social networks is called the [[Persona Data Model 2.0]]. The [[Persona Data Model 2.0]] builds on the [[Higgins Data Model 2.0]] which defines a small set of fairly abstract attributes. | ||
− | + | ||
− | + | ||
[[Category:Higgins 2]] | [[Category:Higgins 2]] |
Revision as of 10:06, 26 August 2011
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}This document describes the top level Higgins 2.0 PDS components under active development. Here are the bugzilla component names:
- H2-Client
- H2-HBX
- H2-PDS
- H2-PDS Support
- H2-ADS
- H2-Data Model
Contents
Front End Components
There are two front end components: a web client, and a browser extension.
Client
The client is written in HTML and JavaScript and runs in any desktop browser (e.g. IE, FF, Safari, Chrome). In the future we also plan to make it display well on the limited screen size of smartphone mobile browser (e.g. iPhone, Android, etc.).
HBX
The Higgins browser extension makes possible functionality that isn't possible in a pure web app architecture. One kind of functionality is browser-side integration with other web APIs and sites. Shown above is a connector that imports the user's advertising preferences from Google's Ad Preference page (http://www.google.com/ads/preferences).
Back End Components
There are three back end components mostly written in Java and running in the cloud (e.g. Amazon AWS):
- PDS
- PDS Support
- ADS
PDS
PDS Subcomponents:
- .pds.usermanager.ws - simple web service to manage user accounts, change password, etc.
PDS Support
PDS Support Subcomponents:
- .pds.client - wrapper around Open Anzo java client
ADS
ADS Subcomponents:
- PLANNED: .ads.ld - Linked Data endpoint
Data Model
Data Model
Data that is either created by the user and stored on the PDS or passes through the PDS intermediary on its way from the data source to the data consuming service can in many cases be mapped into a rich, common data model. This allows it to be consistently displayed to, and in some cases edited by, the user irrespective of its original source. The common data model being developed for the purpose of representing people and their social networks is called the Persona Data Model 2.0. The Persona Data Model 2.0 builds on the Higgins Data Model 2.0 which defines a small set of fairly abstract attributes.