Difference between revisions of "NodeRelationDatatype"
(→Definition) |
|||
| Line 3: | Line 3: | ||
==Definition== | ==Definition== | ||
| − | * | + | * A [[NodeRelationDatatype]] is a kind of URI [[Data Range]] |
* 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 [[NodeIdDatatype]]. The [[NodeIdDatatype]] may only be omitted when the [[Context]] identified by the [[ContextIdDatatype]] contains exactly one [[Node]]. | * It is comprised of a [[ContextIdDatatype]] URI combined with an optional identifier string called a [[NodeIdDatatype]]. The [[NodeIdDatatype]] may only be omitted when the [[Context]] identified by the [[ContextIdDatatype]] contains exactly one [[Node]]. | ||
Revision as of 17:31, 12 February 2008
Contents
Introduction
This page describes the Higgins NodeRelationDatatype.
Definition
- A NodeRelationDatatype is a kind of URI Data Range
- A ContextIdDatatype MUST conform to the ABNF defined below
- It is comprised of a ContextIdDatatype URI combined with an optional identifier string called a NodeIdDatatype. The NodeIdDatatype may only be omitted when the Context identified by the ContextIdDatatype contains exactly one Node.
Two kinds of NodeIdDatatypes are defined: a URI-NodeIdDatatype (Hash URI) and XRI-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 NodeIdDatatype. Rules not defined in this ABNF are defined in the ABNF for XRI 2.0 (which includes the IRI ABNF from RFC 3987).
NodeIdDatatype = URI-NodeIdDatatype / XRI-NodeIdDatatype URI-NodeIdDatatype = URI-ContextIdDatatype [ "#" NodeIdDatatype ] XRI-NodeIdDatatype = XRI-ContextIdDatatype [ "//" NodeIdDatatype ]
Relationship to OpenID
- An NodeRelationDatatype's ContextIdDatatype MAY use OpenID (2.0 only) for its authority segment. See ContextIdDatatype for details.
Open Issues
- We SHOULD combine NodeRelationDatatype and NodeIdDatatype
- In other words should we allow the ContextIdDatatype to be omitted if a NodeIdDatatype is present? (saves repeating the ContextIdDatatype value when referring to another Node in the same Context