Topic map
knowledge organization system
A topic map is a standard for the representation and interchange of knowledge, with an emphasis on the findability of information. Topic maps were originally developed in the late 1990s as a way to represent back-of-the-book index structures so that multiple indexes from different sources could be merged. However, the developers quickly realized that with a little additional generalization, they could create a meta-model with potentially far wider application. The ISO/IEC standard is formally known as ISO/IEC 13250:2003.
A topic map represents information using
topics, representing any concept, from people, countries, and organizations to software modules, individual files, and events,
associations, representing hypergraph relationships between topics, and
occurrences, representing information resources relevant to a particular topic.
Topic maps are similar to concept maps and mind maps in many respects, though only topic maps are ISO standards. Topic maps are a form of semantic web technology similar to RDF.
Ontology and merging
Topics, associations, and occurrences can all be typed, where the types must be defined by the one or more creators of the topic map(s). The definitions of allowed types is known as the ontology of the topic map.
Topic maps explicitly support the concept of merging of identity between multiple topics or topic maps. Furthermore, because ontologies are topic maps themselves, they can also be merged thus allowing for the automated integration of information from diverse sources into a coherent new topic map.
“Topic map” enters the record as knowledge organization system. Crown Archives preserves that source wording while asking what Topic, knowledge and organization can confirm, complicate or overturn.
Why this record matters
“Topic map” is worth following because a concise public description often conceals a longer documentary argument. Here, Topic, knowledge and organization provides the most credible route into that argument.
The record creator and administrative purpose are central evidence, because official documentation reflects both action and institutional priorities. The source revision retrieved here is dated May 5, 2025. The linked authority identifier is Q1064031. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2003.
Institutional narratives can privilege the records that survived while minimizing voices that were never formally collected. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “Topic map”, its source revision and the description used here.
- Expand the search: follow Topic map primary sources, Topic map archive and Topic research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Topic map”?
- Who created the surviving record, and for what administrative purpose?
- What chronology connects this entry to wider political or social change?
Search terms from this dossier
This entry incorporates text from “Topic map” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.