Skip to main content

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.

Jump to: navigation, search

PDS Architecture

Revision as of 22:11, 31 October 2009 by Unnamed Poltroon (Talk)

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

Higgins.funnell.PNG


Personal Data Agent

Higgins 1.1 web services (planned):

Cloud Selector
The Cloud Selector 1.1 makes your cards available as OpenIDs. Reads card data from an I-Card Service, so no client software is required. (Higgins 1.1 only)
I-Card Service
Some selectors are designed as "thin clients" that only implement the user interface portion and rely on a hosted I-Card Service for core functionality. (Higgins 1.0 & 1.1).
CardSync Service
The CardSync Service makes sure that all of your cards are available across all of your computers and mobile devices. (Higgins 1.1)
Personal Data Store
The Attribute Service 1.1 stores self asserted identity data and makes it available for data sharing with others. It also provides data gateway services to connect the client selector with a variety of back end data stores. (Higgins 1.1 only)
Authentication Service
For 1.1 we are working to make the CardSync Service and the Attribute Service rely on an external Authentication Service 1.1. Eventually the I-Card Service will also rely on it.(Higgins 1.1 only)

Higgins 1.0 services:

I-Card Manager
Thin client selectors use the I-Card Manager Google GWT-based app to provide a web interface to view, update and manage your cards hosted on the I-Card Service. (Higgins 1.0 only)


Building Blocks

This section describes the attribute data related services, java frameworks and abstract data models that are used by the above services

Data Models

  • The 1.1 version solutions listed below are based on the Context Data Model 1.1, a very generic, abstract, low level RDF-based model. It is our metamodel.
  • For 1.1 we are now starting work on a higher level (more concrete model) that describes concrete attributes such as name, postal code, telephone number, etc. This model is called Personal Data Model 1.1 and is based on CDM 1.1.

IdAS Solution

The IdAS solution is a deployable "IdAS" Identity Attribute Service.

Attribute Service

New for Higgins 1.1, we're working on an network attribute web service called the Attribute Service. The initial protocol supported will be XDI with others to follow. See Higgins_1.1_Plan#Attribute_Service_1.1 for more info.

IdAS Proxy Service

XDI4J

XDI4J is a java support library for working with XDI.

Back to the top