Structure Sharing is different than Structural Abstraction. Structure Sharing Is Not Available in Textual Dialects.
In structure sharing, nodes in a network that share the same Linking Structure can be joined into a single node with multiple links. Entire subnetworks are replaced by links to shared Structure (Struktur).
Sharing joins together multiple references to the same form, while abstraction ignores selected features. [The occurrence of identical subpatterns within a Form. ⇒ Dnet Dialect]
Sharing is a property of Representation rather than reality. Human prejudice probably does not apply to structure sharing.
> The fluidity of object and reference in networks can be expressed as a transformation rule that is unique to this (and similar) dialects, structure sharing. In structure sharing, nodes in a network that share the same linking structure can be joined into a single node with multiple links. Entire subnetworks are replaced by links to shared structure. **Structure sharing is not available in textual dialects.** […] Multiple occurrence of the same variable in a textual dialect emulates shared structure in a network dialect. The absence of structure sharing in symbolic mathematics has lead to rampant replication of symbols and a presumption that replication is free. […], replication is the source of complexity.
We do have patent laws that adjudicate cases of structure sharing in creative works. [⇒ Establish Rules]
~
BRICKEN, William, 2019. Iconic Arithmetic Volume I: The Design of Mathematics for Human Understanding. Unary press. ISBN 978-1-73248-513-6, p. 320 and p. 340N8.
See also Side Road
pages/structure-sharing
Structure sharing, synchronization, replication, and reenactment describe four distinct modes of multi-user systems that are often conflated.
*Structure sharing* means one representational structure with multiple references (one structure, many references); identity is enforced at the representation level, so mutations propagate because there is only one thing to change (e.g., shared blocks referenced by multiple pages on a FedWiki server). *Synchronization* means multiple independent copies kept identical by propagating updates (many copies, kept in sync); identity is replaced by consistency guarantees, and divergence is managed by protocols (e.g., Google Docs). *Replication* means multiple independent copies that are allowed to diverge (many copies, no automatic sync); identity is fork-based and plurality is preserved at the cost of drift (e.g., classic FedWiki page forking). *Reenactment* means multiple independent executions kept identical by replaying the same event stream (many executions, same causality); identity is causal rather than representational, and consistency is guaranteed by deterministic execution rather than shared objects. **Croquet** is the canonical reenactment model: it shares the event stream and relies on deterministic virtual machines to produce identical states, without sharing representation. Reenactment is therefore orthogonal to structure sharing—neither stronger nor weaker—but incompatible with side roads by default, since it eliminates divergence rather than supporting rejoin over shared structure.