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.
Node Relation
Definition
- A Relation is a type Attribute
- The value of a Relation is a URI that identifies an Entity in a Context
- If Entity A has a relation that points to Entity B this implies that both Entities are representations of the same real world natural person, thing or concept
Details
Note: If the two Digital Subjects being linked are digital representations of the same real-world Entity then a specialization of Relation called a Correlation should be used.
Format
A Subject Relation is a URI. It is comprised of a ContextId URI combined with an optional identifier string called a SubjectId. The SubjectId, if present, uniquely identifies a Digital Subject within the Context identified by the ContextId. The SubjectId may only be omitted when the Context identified by the ContextId contains exactly one Digital Subject.
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
- A Relation's ContextId MAY use OpenID (2.0 only) for its authority segment. See ContextId for details.