Secondary Notation¶
An informal cue channel beside an official notation that helps readers recognize structure or add context without changing formal interpretation.
Core Idea¶
Secondary notation is information carried beside an official notation, by a channel that its formal interpretation does not use. A writer, designer, or user can arrange symbols, group controls, add visual marks, or annotate a diagram so that another person can read its structure or context more readily. The adjective secondary describes the cue's standing relative to an official syntax; it does not mean the information is unimportant to the person using it. Green and Blackwell explicitly distinguish two modes: redundant recoding makes information already present in the official notation easier to perceive, while escape from formalism adds information the official notation has no place to express.[1]
In the first mode, indentation can display a program's syntactic nesting, and spaces can display how a telephone number is grouped. In the second, a diary's hand-drawn marks can signal priority or a program comment can record why a choice was made, even though the calendar fields or executable program do not formally encode that rationale. Removing either kind of cue may leave the official interpretation unchanged; removing the second can nonetheless erase real reader-facing information. The abstraction is the two-channel relation between official rules and informal communicative affordance, not the claim that every such cue duplicates information.[1][2]
Structural Signature¶
Sig role-phrases: official notational channel — supplemental cue channel — human reading task — redundant recoding or escape from formalism — change-sensitive maintenance.
- Official channel. A notation supplies the symbols, fields, or operations with a rule-governed interpretation. The relevant distinction can only be drawn after asking what that interpreter actually takes as authoritative; there is no secondary notation in isolation from something primary.[1]
- Supplemental channel. Layout, spacing, grouping, annotation, size, or color can carry cues outside those official rules. Its physical medium varies; its structural job is to alter what a human can notice or infer without changing the notation's formal result.[1][2]
- Human reading task. Readers use the cues to parse, navigate, compare, or recall context while creating or revising an information structure. A variation that merely decorates a surface but communicates nothing for the task is not a useful instance.[1]
- Contribution mode. Redundant recoding repeats an official fact in a more perceptible form. Escape from formalism adds a purpose, warning, intention, or other informal fact not provided by the formal channel. The modes can coexist, but one cannot define the whole category by redundancy alone.[1]
- Maintenance relation. Since formal changes need not update informal cues, the latter can become stale or misleading. Editors may maintain predictable indentation automatically, whereas arbitrary free-form rationale is harder to synchronize. This is a frequent design constraint, not a requirement that every instance actually be in error.[1][3]
What It Is Not¶
It is not every mark next to a symbol. If a mark is required to determine the official interpretation, it is part of the primary notation for that system. Python's block indentation, for example, generates INDENT and DEDENT tokens that determine statement grouping; it is not secondary in the way optional C/C++ visual indentation can be. The same visual device can change classification when the language's rules change.[4][3]
Nor does secondary mean merely redundant or dispensable for all purposes. A diary mark may carry priority that the official date and event fields do not. A comment may tell future maintainers the reason for a code decision even if it does not change executable behavior. Removing such a cue preserves the narrow formal result but loses informal knowledge. Conversely, a color that is the sole specified carrier of a category cannot be treated as a secondary recoding of that category.[1]
Scope of Application¶
The original cognitive-dimensions account covers both textual and graphical information artifacts. In program text, optional indentation or vertical alignment lets readers detect groupings and differences that formal syntax already determines. In circuit schematics, placing related components together can make a functional relation visible without adding an electrical connection. In control panels, related controls can be grouped spatially while each control's official action remains separately specified.[1][2]
The account also covers deliberately informal additions to diaries, diagrams, and software artifacts: handwritten emphasis, diagram annotations, and comments can express priorities or rationale not admitted by the main form. Which layer counts as official must be established case by case. A notation can deliberately promote a formerly informal cue into syntax, as Python does with indentation; then this entry no longer describes that cue as secondary.[1][4]
Clarity¶
The distinction resolves a common ambiguity in the sentence “the layout means something.” It can mean either that the official parser changes its output, that layout merely recodes a relation the parser already knows, or that readers receive extra context outside the parser. Secondary notation covers the latter two, with different consequences when the cue is removed. This prevents a designer from treating optional spacing as a formal guarantee, and prevents an analyst from dismissing useful informal information as noise just because a machine ignores it.[1][4]
Manages Complexity¶
Instead of separately cataloging every indentation style, color, margin mark, spatial cluster, and comment, the abstraction asks three compact questions: what is official, what is supplemental, and whether the supplement repeats an official fact or adds an informal one. Those questions travel across code, diagrams, controls, and diaries while preserving the crucial difference between formal result and human understanding. Maintenance then becomes a fourth question: will a revision update the supplemental cue or leave an old inference behind?[1]
Abstract Reasoning¶
If two artifacts have the same official content but one is easier to inspect, compare their informal cue channels before concluding that the formal language itself is superior. If a cue disagrees with formal structure, the formal interpreter still governs the official result; the discrepancy is evidence of a possible human-reading error, not a new formal rule. GCC's misleading-indentation warning is a concrete boundary: indentation can suggest that an unbraced statement is guarded by if, while C/C++ syntax says it is not.[3]
For a proposed redesign, the concept also predicts a different kind of loss. An editor that faithfully preserves executable code but discards rationale comments or handwritten diagram annotations may preserve official semantics yet impoverish later modification. The prediction is not that every extra mark helps; it is that the Channel can serve a function that a purely formal equivalence test will miss.[1]
Knowledge Transfer¶
Within notational design, the same tests apply literally to programs, circuit diagrams, calendar interfaces, and control layouts: identify the official interpretation, locate the cue outside it, and ask whether it repeats structure or carries additional context. Green and Blackwell use these unlike artifacts precisely to show that the cognitive dimension is about the notation–reader relation, not one particular typography.[1]
Outside information-artifact design, one may notice a looser pattern of informal signals accompanying an authoritative rule. That broader analogy is not automatically this named HCI dimension. Live prime Representation carries general mapping between target and medium; live prime Redundancy explains some recoding but not escape from formalism. A general “non-authoritative adjunct cue” spanning non-notational systems is a future-prime question, not an admitted parent of this staged entry.[1]
Examples¶
1. Program indentation as redundant recoding. In a language where block syntax is fixed by tokens and braces, optional indentation places nested material at increasing horizontal depth. Green and Blackwell describe this as a second, faster-to-read channel for structure already in the formal code. Mapped back: the official channel is executable syntax; the supplemental channel is whitespace layout; the human task is to inspect nesting; the mode is redundant recoding; and the maintenance relation is exposed when code changes without updating its indentation. GCC's warning illustrates a failure case in which the human cue and the actual C/C++ block relation diverge.[1][3]
2. Paper-diary marks as escape from formalism. Green and Blackwell describe calendar users enlarging letters or drawing lines to convey importance or relationships not captured in a uniform electronic form. Mapped back: the official channel is the dated entry structure; the supplemental channel is handwritten size and marks; the human task is to read priority and planning context; the mode is added informal information rather than duplicate coding; and the maintenance relation is that altered plans can leave marks outdated. Erasing the marks need not change the recorded date or event, but may erase a meaningful planning signal.[1]
These are unlike realizations—program code and a diary—of the same relation between official form and non-authoritative communicative cue. Green and Blackwell also give grouped controls, telephone numbers, and annotated diagrams; none requires redefining “secondary” as a particular color or spacing convention.[1]
Structural Tensions¶
Expressive annotation versus maintenance burden. A generous secondary channel lets a user record priority, provenance, or intended future action beyond the formal fields. But as the primary structure is revised, those free-form marks may become stale; restricting or automatically regenerating them improves consistency but loses some expressive freedom. Neither maximum freedom nor maximum automatic synchronization gives both benefits for arbitrary informal rationale. Diagnostic: What information does the cue contribute, and who or what will update it when the official structure changes?[1]
Fast perceptual guidance versus authoritative correctness. Visual grouping makes an existing relation easier to perceive, but it can also suggest a relation the official notation denies; ignoring layout avoids that false inference but forces readers to reconstruct every relation from raw formal marks. GCC's unbraced conditional example shows why a visual cue must not silently overrule syntax. Diagnostic: When the cue and official rules conflict, can the reader detect the disagreement before making a decision from the cue?[3]
Structural–Framed Character¶
Secondary notation is structural-leaning within a bounded information-design frame. Its portable relation—an official channel plus a supplementary human-facing cue—recurs across programs, diaries, controls and diagrams. Yet the particular cue has no identity apart from a designated official notation and a reader's task. Its evaluative weight is conditional: it may aid comprehension, but a stale or misleading cue can make a design worse. Its human-practice dependence is substantial because cue interpretation relies on habits of reading, grouping, and annotating, not a machine-only invariant.[1][2]
Its institutional origin lies in Green and colleagues' cognitive-dimensions evaluation vocabulary, not in one mandatory style standard. Its vocabulary travel is strongest among notations and information artifacts; calling any redundant physical backup “secondary notation” would merely borrow the word. For import versus recognition, moving from code to a diagram recognizes the same official-versus-informal cue relation, while moving to a non-notational system would require an independently defended analogy or new parent abstraction. The possible generic adjunct-cue skeleton is a future-prime question, not a presently admitted prime. Its character: a repeatable structural affordance whose named meaning remains anchored to notational design and human interpretation.[1]
Structural Core vs. Domain Accent¶
Skeletal relation: one rule-governed representational channel establishes the official reading, while another channel supplies reader-facing structure or extra context without authority over that reading. Redundant recoding and escape from formalism are alternatives within that structure. The latter is why live prime Redundancy cannot be assigned as a strict parent of the whole entry.[1]
Domain accent: official syntax, editors, diagrams, control layouts, comments, and the cognitive task of revising an information artifact determine what counts as secondary and when a cue helps. Without a distinction between an official notation and a human reading practice, the named cognitive dimension loses its original test. Live prime Representation is a more general target-to-medium mapping, not this two-channel design affordance. Whether the bare “non-authoritative adjunct cue” relation deserves a separate cross-domain prime remains an unadmitted future-prime question; no strict DAG parent is asserted on that speculation.[1][2]
Instantiates / Related Primes¶
The existing Cognitive Dimensions of Notations entry describes the larger evaluation framework and is related, not a strict parent by mere membership in a checklist. - Representation (related prime, not asserted parent). The official notation represents information under a convention, but the prime's general mapping does not itself require a separate non-authoritative cue channel. Test: is the claim about mapping target to medium, or about informal information beside an official representation? - Redundancy (related prime, not asserted parent). It explains the recoding mode only; annotation may add information absent from formal syntax. Test: does the cue duplicate an official fact, or convey an additional intention or rationale?[1]
Neighborhood in Abstraction Space¶
Secondary Notation sits in a sparse region of the domain-specific corpus (84th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Language, Mind & Meaning-Making (57 abstractions)
Nearest neighbors
- Musical Notation — 0.82
- Writing system — 0.82
- Dichotic Listening — 0.82
- Generic You — 0.81
- Cognitive dimensions of notations — 0.81
Computed from structural-signature embeddings · 2026-10-08
Not to Be Confused With¶
- Cognitive dimensions of notations as a whole. That is the framework of multiple evaluative dimensions. Secondary notation is one question inside it: can information travel by means other than official syntax?[1]
- Primary or syntax-bearing notation. Python block indentation determines grouping in the language reference. A cue needed to parse the official result is not secondary for that system, however visually similar to optional indentation elsewhere.[4]
- Merely decorative formatting. A style variation that conveys no relation, grouping, priority, or context in the reader's task does not perform this abstraction's function.
- Musical notation or colored music notation. Those are named systems for representing music, not the cross-artifact distinction between formal semantics and informal cueing. If a color is itself an official code in such a system, it is primary for that use.
References¶
[1] Thomas R. G. Green and Alan F. Blackwell, Cognitive Dimensions of Information Artefacts: a tutorial, 1998, “Secondary Notation,” PDF pp.29–33, especially definition, redundant recoding, escape from formalism, examples, and maintenance trade-off. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n ↩o ↩p ↩q ↩r ↩s ↩t ↩u ↩v ↩w ↩x ↩y
[2] Marian Petre, “Relating cognitive dimensions to expert software development”, 2005, p.1, lines on secondary notation and LabVIEW studies. registry ↩a ↩b ↩c ↩d ↩e
[3] GNU Project, GCC 13.1 Warning Options, -Wmisleading-indentation subsection and example. registry ↩a ↩b ↩c ↩d ↩e
[4] Python Software Foundation, Python Language Reference, “Lexical analysis”, §2.1.8 “Indentation.” registry ↩a ↩b ↩c ↩d