Herbrich Ontology – visual representation of a semantic knowledge graph with interconnected nodes, digital identity and structured ontology in the Herbrich system

Class: GridNodeConnection

A GridNodeConnection represents a logical, organizational, or physical connection registered on a Grid Node. Each connection is an entry consisting of a technical Type and a reference Param, as returned by the Grid API endpoint /v1/grid/nodes/{HallAddress}/connections. A connection describes how its subject (Name) is referenced, classified, or linked within the Herbrich network – from technical identifiers (DNS, EAN, PGP-KEY, ONION) to organizational associations (SYNONYME, ASSOCIATION) and semantic definitions (SNAKE, ROOT-ERROR).

Properties of GridNodeConnection

The properties correspond one-to-one to the fields of a connection entry as returned by the Grid API:

Property	Expected Type	Description
Id	xsd:string	The GUID of the connection entry (UUID). Identifies the connection uniquely within the Grid.
Name	xsd:string	The identifier or display name of the Grid connection: the subject of the connection entry.
Type	xsd:string	The technical type of the connection (e.g. FACEBOOK, DNS, HSSID, SHC, SYNONYME, EAN, JENNIFRAME, SNAKE, ROOT-ERROR, …). The `Type` constraint defines the specialized subclasses.
Param	xsd:string	The specific identification parameter or technical reference value of the connection (e.g. a route segment, an EAN, an IMDB ID, an entity name).
Description	schema:Text	An optional free-text explanation of the nature, function, or status of the Grid connection.

JSON-LD Example

{
  "@context": "https://www.herbrich.org/ontology/",
  "@type": "GridNodeConnection",
  "@id": "urn:uuid:0e31271d-fc5e-4891-bbd8-2d4a4136c886",
  "Id": "0e31271d-fc5e-4891-bbd8-2d4a4136c886",
  "Name": "Adolf Hitler",
  "Type": "SHC",
  "Param": "SH-AdolfHitler",
  "Description": "SHC reference entry registered on the node."
}

The example maps a real connection entry from the Grid API. Specialized subclasses use a JSON-LD @type array so both the specific and the base type remain machine-readable, e.g.:

"@type": ["JenniFrameLink", "GridNodeConnection"]
"@type": ["Snake", "GridNodeConnection"]
"@type": ["Root-Error", "GridNodeConnection"]

More specific types

Analogous to schema:Thing and its more specific types (e.g. schema:Organization, schema:Place), GridNodeConnection can be refined through derived classes. More specific types inherit all properties of the base class and are defined by the constraint on the technical Type of the entry; they add their own properties only where the semantics require it.

Type	Description
HSSID	A specialized `GridNodeConnection` that addresses a node within a Subspace (Hyperspace) using a Hall Service Set Identifier. The connection type is fixed to `HSSID`. Adds `hssid`, `spaceType` and `targetNode`.
JenniFrameLink	A specialized `GridNodeConnection` that exposes a callable JenniFrame route (`jennifer.herbrich.org/{Param}`). Typically used when `Type = "JENNIFRAME"`. Adds `targetUrl` and `sourceNode`.
Snake	A specialized `GridNodeConnection` with `Type = "SNAKE"` that represents the definition of the serpent of the Garden of Eden (Genesis 3). Introduces no additional properties; the semantics lie in the `Type` constraint. Adds `sourceNode`.
Root-Error	A specialized `GridNodeConnection` with `Type = "ROOT-ERROR"` that represents an error signature: an error explicitly declared as an error at the root level. Declaration only – not necessarily an active fault. Introduces no additional properties; the semantics lie in the `Type` constraint. Adds `sourceNode`.

Further subtypes can be introduced the same way: declare an rdfs:subClassOf relation to GridNodeConnection, document the Type constraint that defines the class, and note any additional properties. Instances should use a JSON-LD @type array so both the specific and the base type remain machine-readable.

Distinction

GridNodeConnection describes a connection registered on a Node (Id, Name, Type, Param). It is not the same as:

Class	Difference from GridNodeConnection
GridEdge	Directed or undirected edge between two Nodes (`SourceNodeId`, `TargetNodeId`, optional `Weight`). An edge connects Nodes in the graph; a connection is a Type/Param entry attached to a Node.
NodeApplication	Technical application or service running on a Node (Path, AccessLevel, Critical). Neither a connection nor a graph edge.
Node	Physical or logical node (location/object) with a HallAddress and geo-coordinates. Connections and Applications are attached to Nodes; the Node itself is not a connection.
JenniFrameLink, Snake, Root-Error	Not a distinction, but specializations (`rdfs:subClassOf GridNodeConnection`). Every JenniFrameLink, Snake, and Root-Error is a GridNodeConnection.