Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Context UDI"
(→Definition) |
(→Version) |
||
Line 1: | Line 1: | ||
{{#eclipseproject:technology.higgins}} | {{#eclipseproject:technology.higgins}} | ||
== Version == | == Version == | ||
− | This page describes the Higgins [[ | + | This page describes the Higgins [[Context UDI]] used in the [[Context Data Model 1.1]]. |
== Definition == | == Definition == |
Revision as of 13:10, 13 June 2008
{{#eclipseproject:technology.higgins}}
Contents
Version
This page describes the Higgins Context UDI used in the Context Data Model 1.1.
Definition
- A Context UDI is a kind of URI Data Range
- The value of a Context UDI UDI identifies a Context
- The value of a Context UDI MUST conform to the ABNF defined below
Definition
- An Context UDI is defined in UDI Syntax
Relationship to OpenID
Any OpenID 2.0 identifier as defined by OpenID Authentication 2.0 may function as a Higgins ContextId. OpenID 2.0 supports both URLs and XRIs. All of the examples of contexthttpURI and contextXRI above are valid OpenID 2.0 identifiers.
The only caveat to keep in mind is that if an OpenID 2.0 URL is used as a Higgins ContextId, the XRDS or XDI document to which it resolves must EITHER contain:
- Only one XRDS service endpoint or XDI context reference describing the target Context, OR
- The consuming application must know how to select the XRDS service endpoint or XDI context descriptor it requires (i.e., it must know which Higgins Context Type it is seeking).