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 "Higgins Selector"
(→Introduction) |
(→Services) |
||
Line 32: | Line 32: | ||
;Cloud Selector: Makes your cards available as OpenIDs. Reads card data from an I-Card Service, so no client software is required. ''(Higgins 1.1 only)'' See [[Cloud Selector 1.1]]. | ;Cloud Selector: Makes your cards available as OpenIDs. Reads card data from an I-Card Service, so no client software is required. ''(Higgins 1.1 only)'' See [[Cloud Selector 1.1]]. | ||
;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)''. See [[I-Card Service]]. | ;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)''. See [[I-Card Service]]. | ||
+ | ;I-Card Manager: Thin client selectors use this 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)'' | ||
;CardSync Service: Makes sure that all of your cards are available across all of your computers and mobile devices. ''(Higgins 1.1)'' See [[CardSync Service]] | ;CardSync Service: Makes sure that all of your cards are available across all of your computers and mobile devices. ''(Higgins 1.1)'' See [[CardSync Service]] | ||
;Attribute Service: 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)'' | ;Attribute Service: 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)'' |
Revision as of 22:26, 12 July 2009
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
This page describes the Higgins Card Selectors. For an introduction, see the the Information Card Foundation's quick overview of cards and selectors.
A card selector is a piece of software that runs on a computer or mobile device. The user can get cards from card issuing websites and can store them in this selector in much the same way a person puts business, library, loyalty and payment cards in their wallet.
- By clicking on a card you can log into sites. No more passwords.
- By clicking on a card you express yourself. No more filling in forms.
- You can share cards with friends and businesses you trust.
- Some cards create permanent connections to your friends, communities and businesses.
Selector
Higgins Selector 1.0:
- GTK and Cocoa Selector 1.0 - for Firefox (or other applications) on Linux, FreeBSD and OSX (runs standalone)
- RCP Selector 1.0 - an Eclipse RCP Application (Java app; requires JRE 1.4 or higher, runs standalone)
- Firefox-Embedded Selector 1.0 - for Firefox on Windows, Linux, and OSX (Requires a hosted I-Card Service)
Higgins Selector 1.1 planned:http://wiki.eclipse.org/Special:Upload
- GTK Selector 1.1-Win - for Firefox and IE on Windows (runs standalone or uses CardSync Service)
- AIR Selector 1.1-Win - for Firefox and IE on Windows (requires a hosted I-Card Service)
- AIR Selector 1.1-Mac - for Firefox and IE on Mac OSX (requires a hosted I-Card Service)
- iPhone Selector 1.1 - for iPhone, requires hosted I-Card Service
- See the Higgins 1.1 Selector section of the Higgins 1.1 Plan for more details.
Services
Some selector clients take advantage of cloud-based services. These services include:
- Cloud Selector
- Makes your cards available as OpenIDs. Reads card data from an I-Card Service, so no client software is required. (Higgins 1.1 only) See Cloud Selector 1.1.
- 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). See I-Card Service.
- I-Card Manager
- Thin client selectors use this 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)
- CardSync Service
- Makes sure that all of your cards are available across all of your computers and mobile devices. (Higgins 1.1) See CardSync Service
- Attribute Service
- 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)