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.
NodeRelationDatatype
Revision as of 23:43, 31 January 2008 by Paul.socialphysics.org (Talk | contribs) (EntityIdDatatype moved to EntityRelationDatatype)
Introduction
Definition
- An EntityRelationDatatype is a URI.
- It is comprised of a ContextIdDatatype URI combined with an optional identifier string called a EntityIdDatatype. The EntityIdDatatype may only be omitted when the Context identified by the ContextId contains exactly one Entity.
Two kinds of [[EntityIdDatatype]s 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 [[EntityId]. Rules not defined in this ABNF are defined in the ABNF for XRI 2.0 (which includes the IRI ABNF from RFC 3987).
EntityIdDatatype = URI-EntityIdDatatype / XRI-EntityIdDatatype URI-EntityIdDatatype = URI-ContextIdDatatype [ "#" EntityIdDatatype ] XRI-EntityIdDatatype = XRI-ContextIdDatatype [ "//" EntityIdDatatype ]
Relationship to OpenID
- An EntityId's ContextId MAY use OpenID (2.0 only) for its authority segment. See ContextId for details.
Open Issues
- Should we allow the ContextIdDatatype to be omitted if a EntityIdDatatype is present? (saves repeating the ContextIdDatatype when referring to another Entity in the same Context