intramesh identifier

An intramesh identifier is a esentially a relative IRI (i.e., without the scheme, e.g., https:// or file://) except that they should correspond to an existing mesh resources, i.e. Dereferencability for Humans

There are two types of intramesh identifiers: relative identifier and absolute

Syntax

Like IRIs:

Written without a scheme (e.g., no https:// or file://).
May use path segments (../, /foo/bar)
May use fragment identifiers (#)

Unlike IRIs:

Must not contain queries (?).

Semantics

Same as IRIs in RDF: they denote things (aka Referent) which may be mesh resources or “things in the world”.
- Fragments behave the same as in IRIs: they refine the primary denotation.

Purpose

locate mesh resourcess (when used in a filesystem or web site context)
denote a Referent, either internal or external

Identifier Name Limitations for Users

initial underscores prefix all system facet identifiers and should be avoided in general for user facet identifiers

Distribution Relativity

Examples

Node self-reference: "../../../my-dataset"
Other flows: "../../_cfg-op/_current/config.trig", "../../_cfg-inh/_current/config.trig", "../../_dataset-flow/_current/data.jsonld"
Components in other flows: Same pattern, just different flow names

Children

Backlinks