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"
Line 7: | Line 7: | ||
===Higgins Selector 1.0 === | ===Higgins Selector 1.0 === | ||
− | + | ''Released as part of Higgins 1.0 on June 2008.'' | |
− | + | ||
You can get information cards from card issuing websites and store them in this selector in much the same way you put business, library, loyalty and payment cards in your wallet. | You can get information cards from card issuing websites and store them in this selector in much the same way you put business, library, loyalty and payment cards in your wallet. | ||
Line 23: | Line 22: | ||
===Higgins Selector 1.1 === | ===Higgins Selector 1.1 === | ||
− | + | ''Planned for release as part of Higgins 1.1 circa July 2010'' | |
− | + | ||
The following variants of the Higgins selector are being developed for Higgins 1.1. All of the following require a hosted [[I-Card Service 1.1]]: | The following variants of the Higgins selector are being developed for Higgins 1.1. All of the following require a hosted [[I-Card Service 1.1]]: | ||
Line 34: | Line 32: | ||
===Active Client 2.0 === | ===Active Client 2.0 === | ||
− | + | ''Planned for release as part of Higgins 2.0 mid 2011.'' | |
− | + | ||
In Higgins 2.0 we are moving beyond "selector" functionality to add support for managing passwords, Higgins relationship cards, as well other protocols such as OpenID. Even more exciting, it becomes a client for the [[Personal Data Store 2.0]]. It becomes a dashboard for your personal information and a place to manage "permissioning" | In Higgins 2.0 we are moving beyond "selector" functionality to add support for managing passwords, Higgins relationship cards, as well other protocols such as OpenID. Even more exciting, it becomes a client for the [[Personal Data Store 2.0]]. It becomes a dashboard for your personal information and a place to manage "permissioning" |
Revision as of 10:22, 23 May 2010
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
An active client is integrated with your browser and runs on a computer or mobile device. It is a personal identity manager. In Higgins 1.0 and 1.1 this client only supported the OASIS IMI protocol and acted as an Information Card "selector".
Higgins Selector 1.0
Released as part of Higgins 1.0 on June 2008.
You can get information cards from card issuing websites and store them in this selector in much the same way you put business, library, loyalty and payment cards in your 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.
Variants:
- 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 for release as part of Higgins 1.1 circa July 2010
The following variants of the Higgins selector are being developed for Higgins 1.1. All of the following require a hosted I-Card Service 1.1:
- AIR Selector 1.1 - Mac and Windows selector
- iPhone Selector 1.1 - for iPhone
- Android Selector 1.1 - for Google Android
- See the Higgins 1.1 Selector section of the Higgins 1.1 Plan for more details.
Active Client 2.0
Planned for release as part of Higgins 2.0 mid 2011.
In Higgins 2.0 we are moving beyond "selector" functionality to add support for managing passwords, Higgins relationship cards, as well other protocols such as OpenID. Even more exciting, it becomes a client for the Personal Data Store 2.0. It becomes a dashboard for your personal information and a place to manage "permissioning" --deciding who gets access to what slice of your data.