Pete likes to call this "Chunking, naming, linking", in that order. (Why, Pete?)
This page contains some preliminary thinking by Bill Anderson.
The ideas of "chunking, naming, and linking" are related to managing wiki contents, as well as information system architecture, design, and deployment. I have questions about each of these notions. These questions are also about.
First,"chunking": this is a term used into name the human mental work of putting ideas or text entities together under one category or in one place. Sometimes chunking requires breaking large items into smaller pieces; e.g., a large text document into separated sections, such as paragraphs, or even sentences or phrases.
Second, "naming": in computer-based information systems every item needs a name. The computer system needs ways of representing the digital items so that they can be accessed and maintained over time. And in our lived experience we use names to enable sharing our experiences of the world with each other. - all names are arbitrary and socially determined - naming schemes? whatever they are they need to be agreed upon to support long-lived linking.
Third, "linking": in my mind this notion refers to practices of connecting separate information items by explicit relations (and relationships?).
Zettelkasten: this introduction provides a generative description of the method.
Unix OS file system: how files are managed in the directory system; how hierarchy of the file system is related to maintenance of file system integrity. (cf., Bell System Technical Journal: The UNIX Operating System, July 1978)
linking on wikis and elsewhere: in order to link an item it needs a name, hence item 3, above. In the world-wide-web lands, links are represented by URIs URLs and URNs.
Following up on some thoughts from Peter Kaminski.
Information organization on a wiki is focused on linking and chunking rather than classification. Change that.
Put ideas into a wiki page and create links for the associations the arise during the writing.