Component Deliverables

This page contains a list of components of the Higgins Architecture M4 that we'd like to see created for the Higgins project. Most of these, especially at first, will be made available under the Eclipse Public License (EPL), but over time we expect many others will be commercial offerings available elsewhere under other licenses.

A) Apps, developer tools, browser extensions, etc. that use Higgins

Note: lines that start with "HBX:" are contributions to the Higgins Browser Extension.

Wish-list:

1. HBX: Support for (SXIP/IETF) DIX-authentication protocol
2. HBX: Support for Yadis (esp. OpenID), iNames, Liberty, Shiboleth and other common SSO protocols
3. HBX: Extend HBX to be able to automatically fill in web forms using profile data from a Higgins-based Personal Information Provider (PIP) web service.
4. HBX: Extend HBX to be able to do screen scraping and use the scraped data to populate context data stored in a Higgins-based Personal Information Provider (PIP) web service.
5. HBX: Develop version of HBX for Internet Explorer 6.X+

In progress:

1. HBX: Ability to authenticate to an InfoCard-compliant website
2. HBX: Makes profiles available to RSS-P compatible websites
3. Integration of Higgins with the Eclipse Communication Framework's (ECF's) instant messaging and collaboration code.
4. Developer tool: Higgins Demo App based on Eclipse Rich Client Plaftform (RCP)

Planned:

1. To better support Java app developers: Higgins JAAS LoginModule
2. HBX: InfoCard-like "Identity Selector" user interface

B) Higgins Context Providers

The following is a list of context providers that we'd like to see built. "Client-side" providers (that is, providers that integration with things like desktop apps, etc.) are appended with "(client)".

Wish-list:

1. Support for LDAP-based directory services including OpenLDAP.
2. Support for Microsoft's Active Directory service.
3. Support for WS-Trust-based Security Token Services (STS).
4. Support for Liberty, SXIP, LID, Shibboleth and other Identity Provider services.
5. Ability to integrate personal data from Email and IM clients including: MS Outlook, Lotus Notes, Chandler, Gaim, Jabber/XMPP, as well as Telephony and Video services and RSS readers.
6. Ability to integrate personal data from collaboration clients such as Groove, IBM Workplace, WiredReach, and others. As well as from collaboration services such as Plone, CivicSpace, Drupal, Sharepoint.
7. Ability to integrate personal social network data from a variety of online social networking sites and contact sharing services.
8. Ability to integrate personal information from any OASIS XDI data source
9. Developer tools: ability to integrate social network and interaction data from developer source code repositories (e.g. Concurrent Version System (CVS), Subversion, and others)
10. Ability to virtually aggregate identity and profile data from online environments such as Second Life, World of Warcraft, etc.
11. Integration with Interra-project's market/transaction service used by the Interra Card
12. Ability to integration personal data in Electronic Health Records (EHR)
13. Integration with Friend Of A Friend (FOAF) data
14. Community-of-Interest (emergent networks based on topic maps, shared affinities, etc)

In Progress:

1. Profile Services: RSS-P provider
2. Instant Messaging integration: modifications to the Eclipse Communications Framework (ECF)'s "collab" example code (initially using XMPP ECF provider): (client)

Developer tools available now:

1. Rudimentary file-based root context
2. Simple ProfileSharing Network

Done, released:

1. None