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 "Node Relation"

(Details)
(Details)
Line 5: Line 5:
 
== Details ==
 
== Details ==
  
Note: If the two [[Digital Subject]]s being linked are digital representations of the same person, thing or concept then a specialization of [[Relation]] called a [[Correlation]] should be used.
+
Note: If the two [[Entity | Entities]] being linked are digital representations of the same person, thing or concept then a specialization of [[Relation]] called a [[Correlation]] should be used.
  
 
==Format==
 
==Format==

Revision as of 18:53, 31 January 2008

Definition

Details

Note: If the two Entities being linked are digital representations of the same person, thing or concept then a specialization of Relation called a Correlation should be used.

Format

A Relation is a URI. It is comprised of a ContextId URI combined with an optional identifier string called a LocalId. The LocalId, if present, uniquely identifies a Entity within the Context identified by the ContextId. The LocalId may only be omitted when the Context identified by the ContextId contains exactly one Entity.

Two kinds of Relations are defined: a URIrelation (Hash URI) and XRIrelation. The former is consistent with one of the two proposed W3C's Cool URIs approaches. The latter is an XRI as defined by XRI Syntax 2.0.

ABNF

The following ABNF defines a Higgins Relation. Rules not defined in this ABNF are defined in the ABNF for XRI 2.0 (which includes the IRI ABNF from RFC 3987).

relation           = URIrelation / XRIrelation
URIrelation        = contextURI [ "#" subjectId ]
XRIrelation        = contextXRI [ "//" subjectId ]

Relationship to OpenID

See Also

Links

Back to the top