Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "UDI"

(Description)
(Description)
Line 4: Line 4:
  
 
== Description ==
 
== Description ==
* [[UDI]]s identifiy [[Context]]s, [[Entity | Entities]] and [[Attributes]]  
+
* [[UDI]]s identifiy [[Context]]s, [[Entity | Entities]] and [[Attribute]] s
* A [[UDI]] is a kind of [[URI]]
+
* A [[UDI]] is a kind of URI
 
* [[ContextId]] and [[EntityId]] [[Attribute]]s are [[UDI]]s.
 
* [[ContextId]] and [[EntityId]] [[Attribute]]s are [[UDI]]s.
 
* Two broad classes of [[UDI]]s will be supported in Higgins 1.1:
 
* Two broad classes of [[UDI]]s will be supported in Higgins 1.1:

Revision as of 20:51, 27 April 2008

{{#eclipseproject:technology.higgins}}

Version

This page describes the concept of UDI as used in the Context Data Model 1.1.

Description

  • UDIs identifiy Contexts, Entities and Attribute s
  • A UDI is a kind of URI
  • ContextId and EntityId Attributes are UDIs.
  • Two broad classes of UDIs will be supported in Higgins 1.1:
    1. OpenID URIs that resolve to an XRDS document (OpenID 2.0 only)
    2. HTTP URIs or XRIs that resolve to an XRDS document containing a Higgins Service Endpoint. This endpoint holds the necessary metadata to access Higgins Contexts and Entities using a variety of protocols.
    3. Semantic Web Linked Data HTTP Cool URIs (probably only the '303' redirect variant)
  • Some UDIs are global —they can be resolved to an object from anywhere on the internet
    • Objects identified with global UDIs can be interconnected together to form a global, distributed object graph called the HGG
  • Other UDIs are local — they can only be resolved within a LAN or perhaps on the local machine
    • Objects identified by local UDIs cannot be a part of the Global Graph

Back to the top