<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>KnowledgeSystems on emsenn.net</title>
    <link>https://emsenn.net/tags/knowledgesystems/</link>
    <description>Recent content in KnowledgeSystems on emsenn.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 09 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://emsenn.net/tags/knowledgesystems/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Directory organization for knowledge systems: a best-practices synthesis</title>
      <link>https://emsenn.net/library/domains/science/domains/information/domains/knowledge-systems/domains/research/directory-organization-for-knowledge-systems/</link>
      <pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/science/domains/information/domains/knowledge-systems/domains/research/directory-organization-for-knowledge-systems/</guid>
      <description>&lt;p&gt;A knowledge repository needs a directory structure that can hold the&#xA;full range of what knowledge work involves. The literature surveyed in&#xA;the supporting research texts [@asr-research-knowledge-organization-systems;&#xA;@asr-research-intellectual-differentiation;&#xA;@asr-research-epistemological-structure;&#xA;@asr-research-process-ontology; @asr-research-social-learning] does&#xA;not converge on a single canonical schema. It does converge on a&#xA;set of functional distinctions that any adequate schema must represent.&#xA;This text synthesizes those distinctions into four organizing groups&#xA;and their constituent directory types.&lt;/p&gt;&#xA;&lt;h2 id=&#34;1-grounding-principle-categories-as-activities&#34;&gt;1. Grounding principle: categories as activities&lt;/h2&gt;&#xA;&lt;p&gt;Process philosophy establishes that categories are better understood as&#xA;ways of tracking patterns of becoming than as bins for finished things&#xA;[@asr-research-process-ontology]. This permits — and the relational&#xA;commitment of this project requires — that directory names take gerund&#xA;form: they name activities, not substances. A &lt;code&gt;methods/&lt;/code&gt; directory&#xA;holds how-knowledge-is-produced, not an inert category called&#xA;&amp;ldquo;methods.&amp;rdquo; The form is functional.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Knowing Semioverse Specification</title>
      <link>https://emsenn.net/library/domains/science/domains/information/domains/knowledge-systems/domains/knowing-semioverse/texts/specification/</link>
      <pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/science/domains/information/domains/knowledge-systems/domains/knowing-semioverse/texts/specification/</guid>
      <description>&lt;p&gt;This specification defines conformance requirements for implementing a&#xA;knowing semioverse. A knowing semioverse is an agential semioverse&#xA;(already conforming to the base agential semioverse specifications)&#xA;that additionally implements the four-group directory organization&#xA;described in the knowing-semioverse index.&lt;/p&gt;&#xA;&lt;h2 id=&#34;1-normative-scope&#34;&gt;1. Normative scope&lt;/h2&gt;&#xA;&lt;p&gt;This specification IS normative about:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Which twelve directory types are standard cross-cutting subdirectories&lt;/li&gt;&#xA;&lt;li&gt;What content belongs in each type&lt;/li&gt;&#xA;&lt;li&gt;The grouping of those twelve into four functional groups&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;This specification IS NOT normative about:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
