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.
Context Discovery
Revision as of 22:57, 28 February 2007 by Unnamed Poltroon (Talk)
Design Goals
- Higgins-ism free. Higgins is not in the service/protocol definition business. So the intuition here is that there shouldn’t be any higgins-isms in the XRDS documents. And there should be nothing special about how ContextIds are resolved to XRDS Service blocks
- Simple things are simple. We want an approach where a OpenID XRI (or URI) can be referred to by a Higgins i-card using a ContextId of the same value as this XRI (or XRI) and presented as an IContext without any modification of the XRDS to which the OpenID XRI resolves. In other words, armed only with an OpenID XRI/URI, the Higgins Identity Agent should be able to present its attributes to the user (read-only) in the i-card manager. OpenID servers don’t need any contextConfig or factoryConfig to use them.
- Complex things are possible. Beyond the simple OpenID case, we also want to support LDAP, SQL, etc. backed Context which do need contextConfig and probably factoryConfig metadata in order to be presented as an IContext.
Use Cases
| Use Case | ContextId | Resolves to | Finding the <Service> block by | |
|---|---|---|---|---|
| 1 | Higgins OpenID URI i-card | =drummond | xrds1 | matching <Type> value of "http://openid.net/server/2.0" |
| 2 | Higgins URI i-card | =drummond/vcard/+ldap | xrds2 | matching <Path> value of "+ldap" |
| 3 | Higgins URI i-card | =drummond/webSurfingPersona/+sql | xrds3 | matching <Path> value of "+sql" |
| 4 | Higgins URI i-card | @parityinc.net/AccountingDept/+ldap | xrds4 | matching <Path> value of "+sql" |
| 5 | Higgins URI i-card | localhost/icardstore/236-86/+ldap | xrds5 | matching <Path> value of "+sql" |
.