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.
Difference between revisions of "NodeRelationDatatype"
(→Relationship to OpenID) |
(→Definition) |
||
| Line 5: | Line 5: | ||
* An [[I-NodeRelationDatatype]] is a kind of URI [[Attribute Value Datatype]] | * An [[I-NodeRelationDatatype]] is a kind of URI [[Attribute Value Datatype]] | ||
* A [[ContextIdDatatype]] MUST conform to the ABNF defined below | * 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 [[ | + | * 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 [[ContextIdDatatype]] contains exactly one [[I-Node]]. |
Two kinds of [[I-NodeIdDatatype]]s are defined: a URI-[[I-NodeIdDatatype]] (Hash URI) and XRI-[[I-NodeIdDatatype]]. The former is consistent with one of the two proposed W3C's [http://www.w3.org/TR/2007/WD-cooluris-20071217/ Cool URIs] approaches. The latter is an [http://en.wikipedia.org/wiki/XRI XRI] as defined by [http://wiki.oasis-open.org/xri/XriCd02/Xri2dot0Abnf XRI Syntax 2.0]. | Two kinds of [[I-NodeIdDatatype]]s are defined: a URI-[[I-NodeIdDatatype]] (Hash URI) and XRI-[[I-NodeIdDatatype]]. The former is consistent with one of the two proposed W3C's [http://www.w3.org/TR/2007/WD-cooluris-20071217/ Cool URIs] approaches. The latter is an [http://en.wikipedia.org/wiki/XRI XRI] as defined by [http://wiki.oasis-open.org/xri/XriCd02/Xri2dot0Abnf XRI Syntax 2.0]. | ||
Revision as of 10:52, 5 February 2008
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 ContextIdDatatype contains exactly one I-Node.
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 ContextIdDatatype MAY use OpenID (2.0 only) for its authority segment. See ContextIdDatatype 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