|
|
Line 4: |
Line 4: |
| | | |
| == Definition == | | == Definition == |
− | * A [[Context UDI]] is a kind of URI [[Data Range]]
| + | * The datatype of a [[ContextId]] |
− | * The value of a [[Context UDI]] UDI identifies a [[Context]] | + | * [[Context UDI]] is defined in [http://www.parity.com/spec/udi/udi-syntax.html UDI Syntax] |
− | * The value of a [[Context UDI]] MUST conform to the ABNF defined below | + | |
− | | + | |
− | == Definition ==
| + | |
− | * An [[Context UDI]] is defined in [http://www.parity.com/spec/udi/udi-syntax.html UDI Syntax]
| + | |
− | | + | |
− | == Relationship to OpenID ==
| + | |
− | Any OpenID 2.0 identifier as defined by [http://openid.net/specs/openid-authentication-2_0.html 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).
| + | |
− | | + | |
− | == Used as a Value Data Range By ==
| + | |
− | * [[ContextId]]
| + | |
| | | |
| == See Also == | | == See Also == |
| * [[ContextId]] | | * [[ContextId]] |
− | * [[Context Relation]]
| |
− | * [[Context Correlation]]
| |
− | * [[EntityId Data Range]]
| |
Revision as of 12:18, 3 September 2008
{{#eclipseproject:technology.higgins}}
Version
This page describes the Higgins Context UDI used in the Context Data Model 1.1.
Definition
See Also