[[d:2025-10-12|previous]] ← [[t:Knowledge Serving Commons]] → [[d:2025-10-20|next]] // Reposted at [[https://open.substack.com/pub/growingcommons/p/structuring-knowledge-commons|Growing the Commons]] where anyone can comment.// ====== Structuring knowledge commons ====== [[2025-10]]-19 In [[d:2025-10-12|my previous piece]], I sketched out why commons initiatives need knowledge commons as an integral part. But just saying "knowledge" and "commons" doesn't dictate a specific approach to creating and maintaining this knowledge commons. There have been, and still are, several approaches. Right now, I'm working with [[https://growingthecommons.org/|Growing the Commons]] ("GtC") and [[https://www.r3-0.org/knowledge-commons/|Bioregional Knowledge Commons]] ("BKC"), and my intention for this series is to contribute to the structuring of at least both of these. Right up front, let's clarify that we are talking about the kinds of knowledge that are expressible and communicable, not private knowledge. We are very familiar with the kind of knowledge that can be expressed in words, and that is very easy to represent on web pages like this. But knowledge commons can also deal with the kind of knowledge – including what is known as "know-how" – that is expressed and communicated through action — and there are many kinds of action. Currently, videos can be a good start for communicating this kind of knowledge, but in-person experience, such as apprenticeship, is often more effective. Even if the knowledge itself cannot be fully expressed in words on a page, what can still be represented in a knowledge commons is information about who has that knowledge, how to connect with them, and how and when they are open to sharing their knowledge. ===== Historical reflection ===== There are of course many ways of acquiring knowledge, including most obviously just observing what happens, but communicating knowledge from person to person is a different matter. Before humans developed writing, knowledge was just transmitted by human words and actions, which relied on having personal contact with your collaborators. There's no reason why this form of knowledge commons shouldn't still work fine, for these traditional commons. If everyone around knows and understands how a commons works, there's no need to write down the rules: social pressure is enough, without institutions. Once cities and empires came along, people couldn't //all// talk to each other, so laws etc. needed to be written down (sometimes in multiple languages). However writing – along with publishing, sharing and spreading ideas – was not generally available to common people. As reading and writing became more common, communication at a distance was at first just one-to-one letter writing. Then came one-to-one speech by telephone, then only recently video conferencing. In the first incarnation of the Web, creating web sites was still limited to those with technical knowledge and resources. Now, particularly with social media, there is a deluge, a cacophony of information, where the valuable signals are drowned out in the noise.(([[https://www.oxfordreference.com/display/10.1093/acref/9780191843730.001.0001/q-oro-ed5-00019845|This quote from Herbert Simon]] points this out from 1971.)) ===== The reasons for wikis ===== To address our current, more complex, and more global challenges, how can we collaboratively put together the diverse experience and wisdom of the many people who wish to address them? Last time, I set out some questions that I saw were common to most if not all commons, so the question becomes, how can we bring together answers to those questions? Who knows what technologies may be able to help us in the future, but for now I see the most promising approach – for documenting verbal knowledge and pointing to non-verbal – as being with well-ordered wikis. Why wikis? First, we need a technology that is most easily available and usable for the range and diversity of people whose perspectives we want. That accessibility needs to extend right down to the simplicity of writing and editing the material on a computer, or other device. Well, you may ask, aren't services that the likes of Google provide good enough? Yes, they are well designed for collaborative composition and editing of single documents. I, too, often use them for that. But the knowledge we want to bring together is highly relational in nature, and most systems don't give you such an easy way to link documents together. This is the key advantage of wiki systems over Google Docs. A separate consideration is that we are building and supporting Commons, not the usual corporately-owned commercial systems. The big tech providers are diametrically opposed to the commons in their economic models and power structures. So we really don't want to rely on tech giants for our knowledge commons. Political powers that maintain themselves through dividing and ruling don't want their citizens to be doing too much linking up. I'm not suggesting a conscious conspiracy here, but it's easy to see that linking up the knowledge and experience of common people could be seen as a challenge to established power. The fact that it is so easy to link wiki pages together leads to three related benefits. - The pages can be shorter, and more concise: "small pieces loosely joined", as the internet commentator David Weinberger wrote in the early 2000s. - The relationships between smaller pieces are clearer, and easier to document, than between larger pages that each serve multiple functions and comprise different kinds of information. - Small, specific pieces allow people to refer to what they want to know, without being required to wade through information that is irrelevant to them. ===== Challenges for structuring wikis ===== Which brings us to the core of this work. How do we structure a knowledge commons wiki, to support commoning and bioregional initiatives? There is also the question of categorising the content, but that is **not** what I'm addressing here and now — I hinted at that in the previous piece, and I will follow up separately later. Rather, given that a wiki is composed of discrete pages, I'm looking at other questions, and I'll set them out here. First, there's what I could call the page [[t:ontology]]: the way that the wiki is structured in terms of the pages it contains, and the relationships between those pages. We can ask a few questions where the answers will help us make better decisions on structuring. * What can we learn from other ontologies related to the commons? * What do we see as good examples in other wikis, and even other non-wiki resources? * What kinds of thing are important enough to have their own page in this wiki? * What is important not just to the commons, but to the process of commoning? * What are the core, vital, common relationships between these things, at a page level? A knowledge commons wiki isn't the real world, it's just a representation: "the map is not the territory" as the saying goes. Our job is to choose a map or representation that is most useful for our purposes. Oh, and, what were our overall purposes in knowledge commoning? Here are the ones most obvious to me. - To compile and build the knowledge commons around commons and bioregional topics. - To maintain and grow those knowledge commons. - To learn about commons and bioregional topics from the knowledge commons. The first two of these we could call the commoning process. Related to these two, we might ask: * Where do we place new material? * How do we link it up? * How do we know what needs editing? * How do we support effective collaboration and teamwork amongst contributors? * How can we flag what is missing, or what needs to be added? The third point, about learning, brings up another range of challenges. The point of documenting knowledge is not only to remind oneself or other contributors, but also to help other people who want to learn and know about the documented topics. Learners need to be able to find **where** the knowledge they want to know is documented. Then it needs to be presented in a way in which they can assimilate. Given the large potential range of people who may want to learn about commons and commoning, this is a real challenge! Two points strike me as being helpful in any case. * On whatever page someone lands, there need to be links to more basic learning resources, if the material on a page is too advanced for that person; and links to more advanced material, if it all seems too obvious; and easy access to navigational tools and guidance. * The range of perspectives represented needs to include that of the reader, and be in their "language", so that a reader can feel comfortable, welcome, at home — to get them to feel "this is the kind of resource written for people like me." To succeed in this is a great challenge indeed! Beyond the structuring of whole pages and the links between them, there is also the question of the structure of each page. The more we can give pages a similar internal structure, the more easily readers will be able to take in what is presented. So I will continue on two separate pages: * the following one for [[d:2025-10-20|kinds of page]] in a knowledge commons wiki * the one after that for [[d:2025-10-21|the structure of single pages]] in such a wiki ---- By the way, have you (reading this!) seen anywhere else where these questions are addressed? I'd love to know! ---- === see also === * reposted at [[https://open.substack.com/pub/growingcommons/p/structuring-knowledge-commons|Growing the Commons]] where anyone can comment. === terms or themes === * [[t:knowledge serving commons]] * [[t:knowledge commons]] === backlinks === {{backlinks>.}}