Skip to content

Concept Map

A concept map represents knowledge through labeled concepts and links that form readable propositions.

Version
v2 · 2026-10-03 · History
Domain-specific #
13076
Domain group
Professional & Organizational Practice
Origin domain
Education & Pedagogy
Subdomain
Concept Mapping → Education & Pedagogy
Aliases
Conceptual Map

Core Idea

A concept map is a diagram for organizing and representing knowledge by connecting labeled concepts with linking phrases. Each linked group can be read as a proposition: “plants — require — light” says more than an unlabeled line between two words. The relational phrase makes the map's asserted knowledge visible, so a learner or expert can inspect, challenge, and revise it.[1]

Novak and Cañas recommend a focus question, a general-to-specific organization, and cross-links between branches. These improve construction and interpretation, but a map need not be a perfect top-down tree to express propositions. Its identity rests on concepts and readable relations, not one layout style or one software product.[1]

Structural Signature

Sig role-phrases:

  • Focus topic: guides the selection of concepts; normally useful, though not a minimal syntactic requirement.
  • Concept nodes: stand for the ideas, events, or regularities under discussion.
  • Linking phrases: specify a relation rather than mere association.
  • Propositions: connected concepts and link words form interpretable statements.
  • Organizing layout: hierarchy and cross-links can reveal levels and integration, but are not compulsory for every map.

What It Is Not

A concept map is not any diagram with bubbles and arrows. Unlabeled associations do not say what relation is being claimed. It is not automatically a formally executable ontology, and a visual link is not proof that its proposition is true. A Sowa conceptual graph is a different, logic-oriented formalism with typed relations, quantification, and inference semantics; a classroom concept map need not meet those requirements.[1][2]

Scope of Application

Concept maps began as tools for learning and evaluation and can show how a student relates ideas in science or another subject. In knowledge acquisition, experts can externalize the concepts and propositions they use, making them discussable before a more formal system is built. The same schema travels between those settings, although the evidential standard changes: a student's map is evidence of expressed understanding, while an expert's map is a candidate knowledge model requiring domain validation.[1][3]

The frozen “Concept mapping” candidate redirects to “Concept map.” Here the map is the representation; mapping is the activity of producing and revising it. Both provenance IDs belong to this one entry, not two duplicate identities.

Clarity

Inspect a link as a sentence. If “light” and “photosynthesis” are connected, does the intended claim mean “photosynthesis requires light,” “light causes photosynthesis,” or something else? A linking phrase resolves that ambiguity. A focus question further reveals why those concepts, rather than every related concept, appear on the page.[1]

Manages Complexity

A domain may contain many terms and relationships. A map compresses them into nodes, proposition-forming links, and possibly hierarchy and cross-links. This makes omissions and disputed relations easier to see. The compression has a limit: a short arrow label can hide conditions, uncertainty, or causal direction, so important claims may need supporting text or a formal model.[1]

Abstract Reasoning

Read each concept–link–concept unit as a testable claim. Compare maps or successive revisions to see whether relations are added, removed, or corrected. When branches are connected by a cross-link, ask whether it reveals a justified synthesis or an unsupported leap. The map supports diagnosis of expressed understanding; it does not automatically establish what a person privately knows or whether an asserted proposition is true.[1]

Knowledge Transfer

The proposition-forming schema transfers literally from classrooms to expert elicitation because both settings need visible assertions between concepts. A map for a science lesson and one for maintenance knowledge may use entirely different vocabulary while retaining the same node/link/proposition relation. Converting a map into a formal ontology or conceptual graph requires extra typing, logical semantics, and validation rather than a change of title alone.[3][2]

Examples

Student photosynthesis map

An illustrative student map might connect “photosynthesis — requires — light” and “plants — use — carbon dioxide.” An instructor can ask whether each proposition is correct and whether a missing link explains a misconception. These particular sentences are constructed examples of the schema, not reported findings about an actual student.[1]

Mapped back: science focus → concept nodes → labeled relations → inspectable propositions; hierarchy and cross-links may organize the map.

Expert maintenance-knowledge map

In an illustrative elicitation session, an engineer might connect “fault — causes — symptom” and “inspection — checks — component.” The map exposes a proposed causal or diagnostic relationship for discussion before formalization. Original IHMC work describes concept maps as a framework for capturing and sharing expert knowledge; the sample wording here is illustrative.[3]

Mapped back: maintenance focus → expert concepts → relation phrases → propositions to validate before formal use.

Structural Tensions

  • Readable simplicity versus faithful detail. A small map aids inspection, but compressed labels can hide conditions and exceptions. Diagnostic: Which proposition needs a qualifier or supporting explanation?
  • Hierarchy versus cross-branch integration. General-to-specific placement clarifies category structure, while cross-links reveal relations a pure tree misses. Diagnostic: Which cross-link changes the understanding of the topic?[1]
  • Elicited claim versus established fact. A map makes someone's assertion visible, but visibility is not verification. Diagnostic: What independent source or test warrants this link?

Structural–Framed Character

This entry is mixed, leaning structural. Node, link, and proposition form a repeatable relation; evaluative weight enters when judging whether a proposition is useful or true. Human practice determines what question is asked and which labels communicate well. The format arose through an educational method rather than a formal institution's mandate. Its vocabulary travels literally between teaching and knowledge elicitation, while importing “concept map” to any loose visual association would drop the proposition test. The portable skeleton is a representation of assertions, covered more broadly by the live prime Representation. Its character: a reusable visual proposition schema whose practical value depends on interpretation and validation.

Structural Core vs. Domain Accent

The skeletal relation is an external representation that joins named entities by named relations. The domain-specific mechanism is that two or more concepts and a linking phrase form a readable proposition for learning or knowledge elicitation. A mere network drawing lacks that check, while a formal conceptual graph adds logic that is not constitutive here. The broader Representation prime supplies portability; this named educational schema remains a domain-specific entry because its own diagnostics are proposition reading, focus, and map revision rather than every kind of representation.

This entry is a kind of Representation.

The strict subsumption parent is the live prime Representation: the map stands for a person's or group's knowledge claims, with a specific node–link–proposition schema as its differentia. The live Conceptual Graph entry is a neighbor with formal logical interpretation, not a synonym or parent. Network Mapping is broader in target and purpose and does not automatically require proposition-forming labels.

Relationships to Other Abstractions

Local relationship map for Concept MapParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Concept MapDOMAINPrime abstraction: Representation — is a kind ofRepresentationPRIME

Current abstraction Concept Map Domain-specific

Parents (1) — more general patterns this builds on

  • Concept Map is a kind of Representation Prime

    A concept map is a representation that maps knowledge claims to labeled concept nodes and proposition-forming links.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

Concept Map sits in a moderately populated region (58th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Controlled Vocabularies & Term Mapping (18 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08

Not to Be Confused With

  • Mind map or unlabeled brainstorm: proximity and branches can associate ideas without stating a proposition.
  • Conceptual graph: Sowa's logic-based formalism adds typed and quantified semantics.
  • Ontology: a concept map may help elicit one but is not automatically a machine-interpretable ontology.
  • Concept mapping activity: the practice of constructing the diagram, not a second diagram identity here.

References

[1] Joseph D. Novak and Alberto J. Cañas, The Theory Underlying Concept Maps and How to Construct and Use Them, IHMC Technical Report 2006-01, revised 2008. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i

[2] John F. Sowa, Conceptual Graphs, original description of the distinct logic-oriented formalism. Frozen Wikipedia revisions provide redirect/discovery provenance only. registry ↩a ↩b

[3] Alberto J. Cañas and colleagues, Managing, Mapping, and Manipulating Conceptual Knowledge, original IHMC knowledge-acquisition work. registry ↩a ↩b ↩c