Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
NodeRelationDatatype
Revision as of 15:44, 3 February 2008 by Unnamed Poltroon (Talk)
Contents
Introduction
This page describes the Higgins I-NodeRelationDatatype.
Definition
- An I-NodeRelationDatatype is a kind of URI Attribute Value Datatype
- A ContextIdDatatype MUST conform to the ABNF defined below
- It is comprised of a ContextIdDatatype URI combined with an optional identifier string called a I-NodeIdDatatype. The I-NodeIdDatatype may only be omitted when the Context identified by the ContextId contains exactly one Entity.
Two kinds of I-NodeIdDatatypes are defined: a URI-I-NodeIdDatatype (Hash URI) and XRI-I-NodeIdDatatype. 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 I-NodeIdDatatype. Rules not defined in this ABNF are defined in the ABNF for XRI 2.0 (which includes the IRI ABNF from RFC 3987).
I-NodeIdDatatype = URI-I-NodeIdDatatype / XRI-I-NodeIdDatatype URI-I-NodeIdDatatype = URI-ContextIdDatatype [ "#" I-NodeIdDatatype ] XRI-I-NodeIdDatatype = XRI-ContextIdDatatype [ "//" I-NodeIdDatatype ]
Relationship to OpenID
- An I-NodeRelationDatatype's ContextId MAY use OpenID (2.0 only) for its authority segment. See ContextId for details.
Open Issues
- We SHOULD combine I-NodeRelationDatatype and I-NodeIdDatatype
- In other words should we allow the ContextIdDatatype to be omitted if a I-NodeIdDatatype is present? (saves repeating the ContextIdDatatype value when referring to another I-Node in the same Context