#vocab/meta # PKM Vocabulary — README **I turned the concepts, terms, definitions, and relationships in my Obsidian Ideaverse vault into a PKM Vocabulary that my tools (apps, services, scripts, agents, and AI) can read. I would love your eyes on it during at this early stage, and any feedback or suggestions would be appreciated.** My Ideaverse has gotten big enough that I have a naming problem, and I know I'm not the only one. I use the ACE organization framework recommended by Nick Milo and Linking Your Thinking (LYT), so I have Atlas, Calendar, and Efforts. Underneath that I've built out a "Day Cluster" -- the plan, log, journal, review, and health notes that belong to a single day -- plus similar clusters for weeks, months, quarters, and years. That structure works well for me in Obsidian. The trouble started when the vault stopped being the only thing that touches it. I developed a Swift app for recipes and meal planning, Python scripts that build daily notes from templates, a synced Neo4j knowledge graph, Claude AI, and other tools using it too. Every one of those has its own quiet idea of what a "Day Plan" is, or whether an "Effort" is the same thing as a project. Nothing breaks loudly. Things just drift, and six months later a script writes a note the app can't find. So I did the boring thing: I wrote the terms down. 223 of them, each with a definition, a scope note describing context and where it actually lives, and its relationships to the terms above and below it. Then I published the whole thing at a permanent web address so my tools -- and anyone else -- can point at a term and get a real answer: **https://w3id.org/pkm/vocab** Under the hood it's SKOS (Simple Knowledge Organization System), which is the standard librarians and taxonomists use for exactly this. I used the Intentional Arrangement SKOS Editor by Jessica Talisman to develop my PKM vocabulary. Her book "The Ontology Pipeline" will be published in the middle of September 2026. You genuinely don't need to care about that part. What matters for anyone reading it is that every term has a stable address, so "Day Cluster" means one specific documented thing and can't quietly become two. Some of what's in there will look familiar: Ideaverse, Spark, Effort Cluster, ACE Organization, ARC Ideation, and Idea Emergence. Some of it is mine and probably idiosyncratic -- diabetes health notes, recipes and meal planning, Swift app intents (for Shortcut actions, Siri AI and voice interface, Spotlight Search). **This is version 0.1.3, which is my way of saying it's a first draft and I expect to be wrong about things.** Nothing is deleted when I change my mind -- a retired term stays resolvable and points at whatever replaced it -- so it's safe to link to even now. What I'd genuinely like feedback on: 1. **Should the time periods nest, or sit side by side?** Right now Day, Week, Month, Quarter, Year and Decade are all siblings under Calendar -- the only nesting is that a Day is also part of a Week. I keep going back and forth. A Day genuinely is part of a Week which is part of a Month, but when I nest them the tree gets deep and the notes at each level don't actually inherit anything from the level above. Curious how others see it. 2. **Are the names right?** I went back and forth on "Cluster" for a dozen notes that belong to one day. Is there better language for that? 3. **What's obviously missing?** There's a whole layer of LYT practice -- MOCs, home notes, maps, bases, workflows -- that I haven't modeled at all yet, mostly because I wasn't sure whether they're *terms* or *techniques*. Browse it here: https://w3id.org/pkm/vocab -- the hierarchy view is probably the fastest way in, and every term links to its own page. I'm also writing up the thinking behind it, and keeping working notes as I go: - [PKM Vocabulary - Notes](https://notes.warrenweb.net/pkm/vocab) - [PKM Vocabulary - Published](https://blog.warrenweb.net/pkm-vocab-published) Pick at it. Tell me what's wrong with it. That's what a 0.1 is for.