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"
m (I-NodeRelationDatatype moved to NodeRelationDatatype) |
|||
| Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
| − | This page describes the Higgins [[ | + | This page describes the Higgins [[NodeRelationDatatype]]. |
==Definition== | ==Definition== | ||
| − | * An [[ | + | * An [[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 [[ | + | * 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 [[ | + | Two kinds of [[NodeIdDatatype]]s are defined: a URI-[[NodeIdDatatype]] (Hash URI) and XRI-[[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]. |
=== ABNF === | === ABNF === | ||
| − | The following [http://en.wikipedia.org/wiki/Augmented_Backus-Naur_form ABNF] defines a Higgins [[ | + | The following [http://en.wikipedia.org/wiki/Augmented_Backus-Naur_form ABNF] defines a Higgins [[NodeIdDatatype]]. Rules not defined in this ABNF are defined in the [http://wiki.oasis-open.org/xri/XriCd02/Xri2dot0Abnf ABNF for XRI 2.0] (which includes the IRI ABNF from [http://www.ietf.org/rfc/rfc3987.txt RFC 3987]). |
| − | + | NodeIdDatatype = URI-NodeIdDatatype / XRI-NodeIdDatatype | |
| − | URI | + | URI-NodeIdDatatype = URI-ContextIdDatatype [ "#" NodeIdDatatype ] |
| − | XRI | + | XRI-NodeIdDatatype = XRI-ContextIdDatatype [ "//" NodeIdDatatype ] |
== Relationship to OpenID == | == Relationship to OpenID == | ||
| − | * An [[ | + | * An [[NodeRelationDatatype]]'s [[ContextIdDatatype]] MAY use OpenID (2.0 only) for its authority segment. See [[ContextIdDatatype]] for details. |
==Open Issues== | ==Open Issues== | ||
| − | * We SHOULD combine [[ | + | * We SHOULD combine [[NodeRelationDatatype]] and [[NodeIdDatatype]] |
| − | ** In other words should we allow the [[ContextIdDatatype]] to be omitted if a [[ | + | ** 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]] |
== See Also == | == See Also == | ||
Revision as of 20:59, 7 February 2008
Contents
Introduction
This page describes the Higgins NodeRelationDatatype.
Definition
- An 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 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